danielPort9

Don’t know why python gets so much love. It’s a painful language as soon as more than one person is involved. What the author describes is just the tip of the iceberg

I see it as “everyone deserves respect”. No need to overanalyse it. It’s one of those few things in life that are simply true, no proof needed.

That’s dumb. Your bosses will decide to pay copilot instead of paying you. We should use llms in a way that empowers us, not in a way that replaces us.

Just like any other Apple Watch. Don’t see the difference between them and CCP (probably because I’m not American)

I think the tricky part lies on knowing which things can be done without consulting any product owner. I agree that created_at and updated_at don’t cause any harm. deleted_at on the other hand cannot be decided by engineers only (mainly because of GDPR reasons: if something is expected to be totally deleted, then that must be it). As usual, these kind of things are obvious to engineers with years of experience , not so much to newcomers.

You don’t know their performance at their jobs. You don’t know either if they fulfill family obligations decently. You don’t know how their lifestyle is affecting their health long term.

But then you don’t need product managers at all, or at least not full time.

But that changes from team to team, and sometimes even from individuals to individuals. It’s rare the company (not faang level) that invests that much in engineering culture.

Fresh bread delivery. There’s nothing worse than waking up and find out that you dont have bread. Would be great to have fresh bread at my door every morning.

Who said anything about open source not having issues? I talked about trust. Open source can be trusted simply because the code is scrutinised by many if the software is that important. CS cannot be trusted by anyone, because you simply don’t know how they develop their software. Yes, I do work for a private company because otherwise I cannot pay the bills. Companies on the other hand do have the privilege to choose what kind of software they can use (unless the regulation says otherwise, which is in itself something to fix too, but I do lack knowledge in that field to suggest anything)

> The glaring question is how and why it was rolled out everywhere all at once?

Because it worked good for them so far? There are plenty of companies that do the same and we don’t hear about them until something goes wrong.

> Either of these failures is inexcusable in a professional product

Don’t we have those kind of failures in almost every professional product? I’ve been working in the industry for over a decade and in every single company we had those bugs. The only difference was that none of those companies were developing kernel modules or whatever. Simple saas. And no, none of the bugs were outsourced (the companies I worked for hired only locals and people in the range of +- 2h time zone)

I value collaboration as in: high level discussions about how to solve a problem or what’s next in the quarter. When it comes to implementation, please let me do it alone. There’s nothing worse than sitting next to someone to write code (because we all write code differently: I for instance don’t like to stare at the screen for more than 20min. I love to think about the code in my head while taking a walk… now all of that goes to hell if I have to do pair programming)

It’s easier than that: do not trust non open source software no matter how many “seals of approval” it has. Now let’s spread the voice so that in 10 years companies start to think the same way.

Don’t sell yourself as junior. Companies blindly hire anyone who knows how to sell themselves.