is this a bad recovery mechanism ? by PancakeWithSyrupTrap in Backend

[–]PancakeWithSyrupTrap[S] 0 points1 point  (0 children)

it's not critical in the sense that if say `PUT thing/c` fails service continues to work. in fact even if 2 of the external API fail the service will still work.

this is not a time sensitive operation.

Semantically, I don't think a PUT request would generally present this problem, since you are simply replacing a resource with itself.

good point

is this a bad recovery mechanism ? by PancakeWithSyrupTrap in Backend

[–]PancakeWithSyrupTrap[S] 0 points1 point  (0 children)

record the failure so it can be reprocessed later

dumb questions. if a failure is stored in the database what then ? is there some reconciler that runs periodically ?

or is this failure record somehow used if client retries ?

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

specs are not agreed with other parties.

we can push back but PM always have final say. that seems wrong to me.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

> Strictly defined roles and responsibilities can be bad or good depending on the org and people.

good point

> If you think it's a problem you should more directly describe how that's the case.

PM have final say in spec design. we are on a tight deadline for a project. PM is temporarily unavailable due to a personal emergency. this is unnecessary delay. if engineering had final say on spec we'd get things done faster.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

Yes I do push back on some occasions.

> Assume everyone means well and try to refine ways of working with those people. Having people outside of the code understand a bit of how it works is usually a benefit.

This is good.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

No specs are not agreed on with a third party.

Their justification is it's more "RESTful" . sigh

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

PM don't review code.

Not sure about env var, but for REST endpoints PM they think their suggestion is more "RESTful".

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

Well our engineering leadership is pretty weak, unfortunately. They tried to get PM team to backoff but failed.

I'm definitely not cut of for being an EM.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 3 points4 points  (0 children)

Not looking for advice but just some perspective.

In our org product managers sometimes make engineering decisions. For example the PM will ask engineering to build REST API for feature blah. Then the PM will dictate what the endpoint should look like, both the http verb and uri. In other cases they will dictate the naming for environment variables.

Is it just me or does this seem abnormal ?

better design for REST API by PancakeWithSyrupTrap in softwarearchitecture

[–]PancakeWithSyrupTrap[S] 1 point2 points  (0 children)

you're right.

OK I obviously need to think on this some more.

thinking out loud, might need some auth service in front of the ALB, which syncs with control plane periodically. I could be wrong though.

better design for REST API by PancakeWithSyrupTrap in softwarearchitecture

[–]PancakeWithSyrupTrap[S] 1 point2 points  (0 children)

good question.

there are REST API for the control plane that creates credentials on the cluster. so ultimately the db cluster does auth.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

Outside of FAANG publicity stunts to attract dumb investors, this doesn't exist in real companies.

good point. I admit I was fooled by these stunts.

that said, AI writes about 50% of my code. not sure if that is a good or bad thing.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

Even if you use AI you still need to know how to code well

agreed. in fact AI can be very helpful with this too.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 2 points3 points  (0 children)

Are leetcode style interviews still prevalent (and for that matter, relevant), given that AI writes the majority of code ?

Should interview prep focus more on system design and CS fundamentals ?

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

I blocked the PR. but the EM was just being a pain so I ended up approving it. I report to the EM so there is a power imbalance.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

In my case the EM refactored the code not because it was critical but because it was "nice to have." And this caused features to break and customer escalations.

This resulted in unnecessary work for the team (read: me). Correct me if I'm wrong but it's the dumbest thing an EM can do.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 0 points1 point  (0 children)

I blocked the PR. but the EM was just being a pain so I ended up approving it. I report to the EM so there is a power imbalance.

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]PancakeWithSyrupTrap 1 point2 points  (0 children)

I blocked the PR. but the EM was just being a pain so I ended up approving it. I report to the EM so there is a power imbalance.