![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
The approach I’ve seen most is using semantic versioning for releases, and having a continuously upward counting (not bothering to reset) build number for everything in between.
The approach I’ve seen most is using semantic versioning for releases, and having a continuously upward counting (not bothering to reset) build number for everything in between.
Sweet. Welcome to the cult of Debian.
We (Debian users and contributors) are inevitable. Our quiet satisfied computing cannot be stopped, only delayed.
We should consider getting some fancy robes and a few club houses, though. The only thing that can make Debian better is cookies and tea.
Lunchtime, doubly so!
I’ve not worked with a marketing team where that would work, but maybe it will for some.
I’ve never been anywhere that I thought it would work, but it ultimately did, almost everywhere.
I’ve found it takes a few iterations, but the marketing folks in on it love being the ones who actually can reliably deliver on their promises.
It doesn’t work for the marketers that promise whatever they please without talking to dev, but I don’t find them to be worthwhile professional allies, so I don’t sweat it.
It doesn’t change the “massive customer will only renew if” scenario, though.
Very true. It doesn’t help with that case, and that one does happen. I’ve had the best luck saying “we don’t do that, but we’re scrambling to add it” in that situation.
The stupidly easy solution is to just give them stuff that has already been successfully delivered to production to market, 9 months from now. There’s invariably a huge backlog of years worth of successes that marketing wasn’t even aware of.
“No deviations will be approved from this year’s Agile product roadmap!”
We’re in a “fuck around” cycle where they pretend that the problem was we didn’t have “copilot”, and not that all of our development managers are wildly unqualified.
The “find out” part comes next.
Which is fucking impossible to fathom, because my fucking grocery store’s app can’t even implement search reliably, today.
I’m not sure how they’re going to manage to make things worse.
Actually, I’ll make a guess. My guess is we will go under the critical skill level needed for building safe hospital equipment, and we will get a rash of that stuff killing people due to lack of programmer skills.
I hope the asshole CEOs are the ones that die, but there’s not enough karma in the world for that.
Yep. This is the way.
Blind faith in organizations claiming to protect our long held traditions makes us vulnerable to fascism?
I don’t like to jump to conclusions. I’m going to give it a few more films to see if the pattern holds. Lol.
It works fine for anyone with the foresight to be born into an ultra wealthy family.
Yeah. But it’s still rare to see “no unicycling” signs so the unicyclers need to get on that.
The mantra that got me through JavaScript was “almost nothing we do here is able to be synchronous”.
Everything about the language makes more sense, with that context.
An LLM pointed at various (local) public sources of data, that can answer (local) voter questions, could be pretty cool.
I.e: "Summarize X candidate’s voting record on tax increases/education/walkable cities/unionization/etc…
Don’t be like me.
Too late!
At what point does one stop being a noob?
I recognize that trick question. For C++, the answer is always “soon”.
That’s a solid description. I’m stealing that. “Cozy” is an excellent word for that sets C# apart from other languages.
Yeah. My journey of love, loathing, hatred, adoration, and mild appreciation for C++, ended with the realization that 90% of the time I can get the job done in C with little hassle, and a consistent, predictable, trustworthy set of unholy abominations.
Perfect description.
It also describes why I now love GoLang so much.
“How has GoLang improved on this unholy tome or horrors?”
“Well, it fits in my pocket now.”
This is quite accurate.
Source: I’ve been in this journey.
I find this outcome delightful for all the compliance mandated organizations that are leaching with no intention to contribute back.
It could be really helpful for developers at pure leech organizations to make a case for being ready to contribute in an agile manner.
Now they’re all stuck waiting on either a good Samaritan, or their lawyers to get out of the way of progress.
I have little doubt that the fix has been committed to private forks dozens of times already, of course.