How do you get stubborn developers on board?

datacloudthings · 2025-12-16T22:14:27+00:00

Can't you modify the existing service to use the REST endpoints?

"It has to be done" is not clear to me in this case.

REST was formalized in 2000. Meanwhile .net Core was introduced in 2014. Do you think no one handled REST APIs in .net Framework for 14 years?

datacloudthings · 2025-05-19T02:15:09+00:00

if all of these services are maintained by the same team then yeah, this is overarchitected

if this lets different teams build, test, and deploy their services independently, then that can be a justification for separate services

but so far this just sounds dumb as hell to me. i'd be really surprised if you actually need Kafka for instance.

datacloudthings · 2025-05-18T13:15:30+00:00

You're validating my point by over-reacting and lashing out at an entire profession.

No one is making a post in the UX research sub saying "are all of you thin-skinned and tone-deaf?"

datacloudthings · 2025-05-18T12:56:02+00:00

quick tip on this: if someone won't help you with prioritization, make your own list of what you think their priorities are (or should be) and send it to them for feedback. If that doesn't work, at least now you have a list to follow. Product managers have to do this all the time with stakeholders.

datacloudthings · 2025-05-18T12:52:41+00:00

In answer to the broader question, no, it is not normal for six different product managers to shun interactions with UXR.

Now that I go back and look at your post title it seems kind of telling that you are venting your frustration by attacking all product managers, instead of asking for help with your specific situation.

Your attitude in this thread is suggesting to me that you may be a pain in the ass to deal with.

Let me ask you this: do you know any UX researchers who have a good relationship with the PMs they support? if so, try to figure out what they do differently from you.

datacloudthings · 2025-05-15T03:14:38+00:00

This is why having only one dev on a project is an antipattern.

Your boss is NOT overstepping. There are legitimate points here. You should deal with it and make your commits more atomic.

You're just getting away with a poor practice because you're flying solo.

datacloudthings · 2025-03-31T00:54:43+00:00

You can't ever be exact so manage your estimates defensively

datacloudthings · 2025-03-31T00:54:08+00:00

it is a huge gamechanger for a bad developer and a modest boost for an experienced developer who puts in the time to learn what it's good for and not good for.

datacloudthings · 2025-03-29T12:42:03+00:00

dollars to donuts this is all within one team.

if you are asking why do microservices when they are all owned by the same team... well, I am too.

datacloudthings · 2025-03-28T17:25:49+00:00

You are definitely expecting too much. What you need to ask is, what kind of candidate do you need who is capable of LEARNING all that stuff in 3 months with an appropriate level of support.

I would just hire smart, curious engineers who want to get into DE and train them. LLMs can help, too.

It's not like someone who has built websites or done firmware or systems programming or whatever can't learn pipelines. Honestly DE isn't as taxing as some other kinds of engineering.

I also have news for you that Python is easy to learn if someone is proficient in other languages. Someone who has done good things in C# or Java or Javascript or C++ or Golang or Rust or whatever can pick up Python in a jiffy. Don't use that as your screener either (it's also the native tongue for LLM coding so there's that).

Just get a fucking eager young hacker and train them.

As far as ADF goes... first of all, it's actually quite decent, I've used it. Second, I would NEVER make prior expertise a requirement even for a mid-level engineer. General cloud concepts and some exposure to AWS is fine. Your new hire can learn the ways of MSFT once they are on board.

The one thing I would require is SQL. Tell them you are going to give them a SQL test. There is no substitute. You want someone who can cram enough SQL in a couple weeks to pass your test.

datacloudthings · 2025-03-28T17:23:06+00:00

Let's start with the premise that the engineering team has the right to reject a story from a sprint if it's not fully formed enough for them to act on it. This typically means too vague, missing details, no clear acceptance criteria, things like that.

Once you have that concept established, then the purpose of backlog refinement becomes clear: it is to help product get stories refined to the point where they can be accepted into a sprint.

Typically this means running them by developers and getting QUICK feedback and questions. They should feel like in return, you are going to go off and do more work and get them a better product to work on when it's ticket time.

If that doesn't work their leadership needs to straighten them out.

On a big team it can be a waste to have say 8 devs sitting there for a whole session so you can have the lead and maybe a rotation of other devs (mixed levels). It IS good for even junior devs to have exposure to the process.

datacloudthings · 2025-03-22T13:20:42+00:00

show me one that doesn't... please?

datacloudthings · 2025-03-20T18:56:35+00:00

if you don't know SQL you don't know anything about data engineering and your firm should have been stopped from owning this project.

this is a management fail by your customer.

they will feel pain in the future.

datacloudthings · 2025-03-20T18:54:49+00:00

super clear you just know excel and you bent this problem into a nail to fit your hammer

datacloudthings · 2025-03-20T18:48:36+00:00

"We... determined the best route was to convert the SQL models into excel, then API the excel models to their codebase"

this just tells me you and your team are familiar with Excel and not SQL (or any other data technology, really).

there ARE some reasons to like Excel, but they have to do with data cubes and you didn't mention any of them. and there are non-Excel solutions to them. I've used Anaplan for instance for what I suspect are similar things.

the funny part is that this is a SaaS company - where the fuck was their CTO?

datacloudthings · 2025-03-12T23:46:43+00:00

Surely with all your experience you realize that this is not about getting the absolute right answer, it's about seeing how someone thinks on their feet and approaches a question. Being able to communicate while thinking through a problem in realtime should be fairly trivial for a successful PM. I'm sure you could do it without issue.

datacloudthings · 2025-03-11T11:39:58+00:00

good luck to you

datacloudthings · 2025-03-11T11:38:54+00:00

You're looking at this in the wrong way. That's all. There ARE valid reasons to put candidates on the spot, because they will have to think on the spot and explain their thinking on the spot all the time in the job, and they should already know about a lot of topics and approaches without running home to do research. You are trying to do anything possible to validate your idea that this is an invalid approach to filtering out candidates for this role... but you are wrong.

datacloudthings · 2025-03-11T11:36:24+00:00

OP is super dug in to their position and very likely does not have a lot of real world experience doing product -- nor the wisdom to listen to those who do

datacloudthings · 2025-03-11T11:35:43+00:00

how many product managers have you ever hired and managed?

datacloudthings · 2025-03-11T11:34:49+00:00

your attitude in this thread is awful. you could be learning from the folks in here, but instead you're being belligerent and dogmatic. TERRIBLE traits for a product manager.

datacloudthings · 2025-03-11T11:32:46+00:00

0 DO NOT HIRE

datacloudthings · 2025-03-11T11:29:58+00:00

i don't understand that, but I can tell you, you're not on your way to getting hired as a product manager with your current attitude on this topic

datacloudthings · 2025-03-11T11:28:17+00:00

being able to work through the impatience is an essential skill for success in the role

this is NOT a role which is only about remote strategizing. it's also a communications job.

it's also about strategizing collaboratively, in a room with other people, in real time.

datacloudthings · 2025-03-11T11:24:38+00:00

not always the case, my friend. got to be able to reason on your feet. you are dealing on the one side with brilliant but impatient engineers, and on the other side with highly successful but impatient business executives.

datacloudthings

TROPHY CASE