Back when I saw doing freelance work, the worst type of client was the one who was semi-technical, meaning they were technical enough to write code that they wanted to contribute to the project or to have strong architectural opinions, but not technical enough to understand the nuances and the implications of their suggestions.
I guess that, with vibe coding, it is very easy for every client to become like this.
> [...] they wanted to contribute to the project or to have strong architectural opinions
Also the worst kind of tech line-manager - typically promoted from individual contributors , but still want to argue about architecture, having arrived at their strong opinion within the 7 minutes they perused the design document between meetings.
If you're such a manager, you need to stop, if you're working with one, change teams or change jobs - you cannot win.
What are your thoughts on the idea from the book High Output Management where everyone's outputs under the manager is considered the managers output. Aka if they're choosing incorrectly it's trivial to explain the facts for them to choose right. If they don't you get them to agree to the wrong choice in writing and move on
> if they're choosing incorrectly it's trivial to explain the facts for them to choose right
It's far from trivial when there are multiple, clearly-communicated trade-offs (documented in the design doc!) that, but you happen to land on opposite ends of value-judgements (e.g. pattern A is easier to maintain based on my experience with the codebase & bugs that have popped up, but manager thinks pattern B is simpler to implement, but brittle). The debate wastes time, and signals mistrust when you're the staff engineer, or the design was OK'd by staff/rest of team
While I think the link between birth rates declining and automation does make sense, it will take quite sometime for this to verifiable as this is a somewhat recent anxiety. The reason for the trend that we have seem over the last decades seem to mostly stem from lower childhood mortality rates, women having access to the job market, and perhaps to a lesser extent climate anxiety.
Out of curiosity, I live in Europe where it is quite common to work remotely across countries within the EU or the UK. I have always wondered why so many US companies limit remote roles to people based in the US, and then mention a shortage of qualified talent. It feels like there is a large pool of people being overlooked.
In our position we're only hiring for in person roles, so location/authorization is a must have.
But in regards to US/EU remote, I imagine the EU candidates come with slightly higher overhead (different payroll processing, employment regulations, time zones, etc). Which makes it easier to adopt a US only approach.
In Europe, what we do is usually: if the person lives in the same country as one of our business entities, they get hired directly as an employee. If they live in a country where the company does not have a business presence, they get hired through an EOR or as a contractor.
Do you have any data to back up the claim that it's "quite common" to work remotely across countries within the EU/UK. Almost nothing in the "common/single market" works uniformly across the "common/single market". For instance this guy (OP) doesn't have a hope in hell of landing a job anywhere in the EU even though he's in the UK.
I know it’s anecdotal data, but every company that I’ve work for in the past 11 years? I’ve worked for companies in the UK, France, Portugal. If you check the job listings for remote jobs in Europe, you will find that there is rarely a constraint to where in Europe the candidate is located in.
If you had actually read the post you would have understood there are ways to ditch GCP, but they are perceived as cumbersome.
The exaple is OpenID Connect. It works well with Azure (according to the post).
I'm sorry to say this, but the author is choosing something easy but unrealiable over something a bit more complicated but reliable.
It's really the author's fault. They are choosing their comfort over the service reliability (and keeping promises made to customers).
Heck they might even go with api keys. They could give explicit direction on the minimal amount of permissions the api key would need and they could ping the users each 3-4 months to rotate them.
But no, I guess we'll have another post at some point about the fourth (definitive?) account suspension.
> I think the OO hatred comes from how academia and certain enterprise organisations for our industry picked it up and taught it like a religion.
This, this, this. So much this.
Back when I was in uni, Sun had donated basically an entire lab of those computers terminals that you used to sign in to with a smart card (I forgot the name). In exchange, the uni agreed to teach all classes related to programming in Java, and to have the professors certify in Java (never mind the fact that nobody ever used that laboratory because the lab techs had no idea how to work with those terminals).
As a result of this, every class from algorithms, to software architecture felt like like a Java cult indoctrination. One of the professors actually said C was dead because Java was clearly superior.
Java was probably close to 50% of the job market at some point in the 2000s and C significantly dried up with C++ taking its place. So I'm afraid everyone was right actually.
To be honest, I'm convinced the reason so many people dislike Java is because they have had to use it in a professional context only. It's not really a hobbyist language.
Just for the record, I don't think C ever dried up in the embedded space. And the embedded space is waaaay bigger than most people realise, because almost all of it is proprietary, so very little "leaks" onto the public interwebs.
Nuclear plants follow a strict “as low as reasonably achievable” (ALARA) principle. Any intake of reactor water or radiation exposure must be reported and evaluated no matter how small.
The water is borated and heavily purified. You don’t want stuff growing inside, but at the same time you don’t want to have chlorinated water slowly corroding the metal components.
On the picture, the fuel rods are indeed protected by a huge quantity of water above them. But what happens below them ? They seem to be in direct contact with the ground...
I guess that, with vibe coding, it is very easy for every client to become like this.
reply