Wild thing to say. There's not enough information provided in these dockets for me to form an opinion whether or not any of these dismissals are warranted or unwarranted.
Take a breath. Balance compassion for self and others.
I'm old enough to remember being fatigued with so many people talking about making "apps". Programs that run on a phone. Before that everyone was excited about blogging. Web 2.0 ugh.
Before that we were excited about the wheel and the creation of fire. All capital drained into those ephemeral fancies.
Yep, the hype will die, and some of the substance will remain. I mean, we're currently commenting on Web2.0 about a blog post. Both stopped being the next big thing, and are now just some things we use. Relevant anecdote: I most recently worked on the apps (ding) for a car company (double-ding, fire and wheels).
Yeah. I don't mind AI, but I'm waiting for it to stabilize and a good work flow being replicable for non-toy problems that should survive and evolve for a long time. I don't think I lose out much by not having 10 agents doing my work for me right now. In 6 months or some years or whatever I can just learn the new way of doing it. It's just exhausting with how much it changes month to month. Do I use it? Yes. Probably suboptimally. I'll learn later, though.
Like the new frontend frameworks coming every week after 2010 sometime. Not jumping on every single one, and waiting until react was declared the winner and learn that worked well. Sure, someone that used it from day 1 had more experience, but one quickly catch up.
It only is nonsensical if you create your own comparison dimension ("adoption") to construct your argument, to call what I said, nonsensical!
All those listed and more, are part of the cycles that the parent comment mentioned and which I've continued.
Same thing with Agile. Mostly sprint-based waterfall, iterative development is not something I've ever seen in practice. Or people over processes, remember those ideas?
BigData, was another hype cycle where even smaller companies wanted a "piece of the action". I've worked at the time in a sub 50 developers company, and the higher ups where all about big data. When in fact our system was struggling with GBs of data due to frugality in hardware.
For a moment in time you couldn't spit in any direction without hiting a Domain Driven Design talk. And now we disable safeguards and LLMs write a mix of garbled ideas from across all the laundered open source training data.
Too early to tell where AI will land, and if it will bring down the economy with it, but spending rate doesn't deliver equal results for all, and we will have to see after the dust settles.
This is so whiggish that it made my whig fly off my head when I read it. I spend a lot of time on HN, so I'm gonna need to secure my whig somehow, because this happens a lot.
I appreciate your perspective on this. We're living in an era of sensationalism and noise. It wont get better until a lot of people from every political disposition becomes tired of hollow words designed only to create BIG FEELINGS.
Imagine an era where the majority leans in on a balance of compassion for self and others.
Proprietary food.. that you can only buy from a single company are all doomed? Might I offer an example that, under some definitions, has not failed despite that strategy. The McRib.
I was going to offer the twinkie but I guess hostess declared bankruptcy, so maybe you're right.
It's not an unreasonable statement though that for the concept to work it has to "jellybean" though: many manufacturers, many variations, same basic product, ubiquitous availability.
Where it sits as a "premium" good doesn't really work as a value proposition.
You could express the offset with scientific notation, tetration, and other big math number things. You probably don't need the whole offset number all at once!
You can use all the math stuff like scientific notation, tetration, etc... but it won't help you make things smaller.
Math notation is a form of compression. 10^9 is 1000000000, compressed. But the offset into pi is effectively a random number, and you can't compress random numbers no matter what technique you use, including math notation.
This can be formalized and mathematically proven. The only thing wrong here is that pi is not a random number, but unless you are dealing with circles, it looks a lot like it, so while unproven, I think it is a reasonable shortcut.
It uh.. was kind of weird that a junior dev wrote.. an.. rfc? I sense that this is a company that has somewhat adapted that concept for some kind of internal communication, or it's AI slop. All the jobs I'd ever had would probably call something like that a "design proposal" or similar.
Maybe this is a folksy anecdote about a junior developer working for John Email designing the protocol for trinary morse code over a token ring of twisted pair barbed wire. An RFC for that kind of project would be natural.
In the spirit of this, I propose we start calling things like flowcharts, SVG images of digraphs, UML diagrams etc "articles of war" just to spice things up.
Take a breath. Balance compassion for self and others.