People took it seriously because that's exactly how a lot of LLM users think and exactly what they want 'coding' to be. Honestly I'm not even certain it is satire.
I don't think it's tongue-in-cheek at all. It refers to a specific type of LLM coding, where you literally don't care about how bad the code is and just code stuff and hope it works. That's how I use the term, and that's why I use it rarely.
I'm a software engineer and you don't speak for me.
There are plenty of software engineers who would unionize, given the chance. It's not easy to do. And sure, with enough effort we could, but that's a pretty big difference from "refusing to".
Software engineers and other white collar professionals want to believe we have more in common with our CEO than we do with a plumber because we work in offices, but I'd bet most of the executive class, ownership class, boards of directors and such see us the same as plumbers: we're a necessary expense
Yep. I first read that when I was twelve. I wouldnt say I understood much back then, or even now after a number of re-readings. But its an amazing book. "Sprawling" is one word that I would use to describe it.
> Many of the benefits and concerns are tackled in their respective chapters. Even so, I want to emphasize that Server-side tagging has the potential to overturn the current dynamic of data collection and governance for an organization. You own and have full control over the server-side environment. You have access to tools and methods to thoroughly vet and validate the traffic between network sources and your advertising and analytics endpoints.
Not quite sure what's so revolutionary about this -- isn't this what Segment and other similar products have been offering for the better part of a decade?
Not exactly. Although Segment has some backend integrations, most tags still need to be on the client side. Each tag typically tracks its own cookies and uses third-party cookies to learn more about each user. However, as those cookies are starting to go away and privacy is starting to increase, we may see a big shift.
I'm hopeful something like this will take off. I'm tired of adding so many slow third-party tags.
Secondly, unless you're selling compiled software for others to configure, there really is no difference between config in config files and config in code, except that the former does not let you build such meaningful and useful abstractions. You're presumably delivering it all into production via CI/CD anyway, so what difference editing a config file vs. some actual source code, besides the lack of real type safety and IDE assistance?
Pulumi have figured this out.
(And I suspect that if your end users need to configure your software's use of Spring's Dependency Injection in XML config then you are probably doing it wrong.)
If people were to actually read beyond the first sentence, it would become clear very quickly that this was meant to be tongue in cheek.