281–290 of 401 posts
Earlier quoted context omitted.
This isn't about distinction between literal titles. But continue missing the point.
You make up an false dichotomy. The differentiation between the title and the supposed skill level based on title, is neither true nor helpful to make your point.
> Craftsmanship will always be in our hands, it's one thing we can never outsource to a machine. I'm right there with you, but this last sentence concerned me a bit. In my most other "industries", craftsmanship is not _dead_, but it's been pushed to the wayside for (significantly) cheaper and more available alternatives. You can still get hand-made leather shoes, but very few want to pay $1000+ for them. You can stil…
Earlier quoted context omitted.
At first I thought "medior" was a strange typo for "senior", but on seeing it twice I had to check - apparently it's used in some parts of Europe to mean "mid-level"
It's a Spanish/Portuguese thing, so south America also. I kind like it even though I was originally nonplussed by the term.
This cascades of short sentences are a giveaway.
Earlier quoted context omitted.
There's like three groups of developers you need: The prototypers, who move fast and break things, who throw together shiny first versions that look great and work some of the time; The architects, who take the prototypes and take the time to build it correctly; And the gardeners, who maintain the built system for the next 10-30 years, fixing bugs, making incremental improvements to speed or resource usage, and updat…
Ha, I'm a gardener then, on my 15th year of maintenance. So halfway there according to you. Slowly, very slowly, fixing the thousands of bugs the rockstar left behind 15 years ago.
Earlier quoted context omitted.
It’s not about pristine software. Customers expect something that works. But changes will then be requested and the expectation is that the software will continue working. It’s hard to do that with janky code. If you have a good architecture and keep good code hygiene, then velocity is easy. Without that, everything will slow to a crawl.
I agree, but I think you've not understood what the reply above is saying. You will never get the chance of "customers requesting changes" if you never ship. The company with the janky code that shipped will. And they will iterate and get better - as described by your process.
Why does good code imply never shipping?
Managers and Developers have different thresholds for “good enough to release”. The former are not the one on call for bugs or the one that get blamed for outage, but they are the ones that get praised when projects are completed quickly. Anything that’s past demo level is good for them.
I like fixing code made by AIs and others (outsourcing code is similar as someone else said already). Last week we found out some client tried to vibe some departmental tool; the result is some massive crap in nextjs that needs 10GB mem to compile, has 1000s of lint errors, dev logs in git (very noisy ones) and so on. Now we have to fix it: its basically free 10k-50k euros over and over again for this type of work. V…
This X a 1000. I work in IR for small to medium sized business. The past few years have seen my business increase well beyond what I can reasonably handle and my bank account feels like a dragons pile of gold. I will always always be on the side of security should be integrated and planned for and by no means do I want to see breaches. That being said giving people of dubious expertise the ability to blast out an app…
Earlier quoted context omitted.
You make up an false dichotomy. The differentiation between the title and the supposed skill level based on title, is neither true nor helpful to make your point.
There's no false dichotomy. You're just choosing to miss the point to argue semantics.
Earlier quoted context omitted.
It’s not about pristine software. Customers expect something that works. But changes will then be requested and the expectation is that the software will continue working. It’s hard to do that with janky code. If you have a good architecture and keep good code hygiene, then velocity is easy. Without that, everything will slow to a crawl.
> If you have a good architecture and keep good code hygiene That's a big "if" however - customers have a tendency to come up with requirements that aren't covered (or only covered in awkward ways) by the architecture you envisioned initially, while many of the well-architected parts will remain unused.
Earlier quoted context omitted.
This X a 1000. I work in IR for small to medium sized business. The past few years have seen my business increase well beyond what I can reasonably handle and my bank account feels like a dragons pile of gold. I will always always be on the side of security should be integrated and planned for and by no means do I want to see breaches. That being said giving people of dubious expertise the ability to blast out an app…
What is "IR"?