For quick and dirty app deployments, though, other vendors like Heroku probably do a better job.
206 karma · joined December 13, 2023
For quick and dirty app deployments, though, other vendors like Heroku probably do a better job.
Luckily, we moved off Azure Front Door about a year ago. We’d had three major incidents tied to Front Door and stopped treating it as a reliable CDN.
They weren’t global outages, more like issues triggered by new deployments. In one case, our homepage suddenly showed a huge Microsoft banner about a “post-quantum encryption algorithm” or something along those lines.
Kinda wild that a company that big can be so shaky on a CDN, which should be rock solid.
I had what felt like withdrawal symptoms: a strong headache, muscle aches, and I was really cold. It lasted for two days, until I took a minuscule sip and everything went away within five minutes.
That made me realize the extent to which I was actually addicted, and how dependent my body was on it.
I managed to quit and stayed caffeine-free for about a year.
But one day I said, “Just one cup won’t hurt,” and oh boy... it was like having superpowers. I was so focused, so wide awake. Of course, I’m an addict again. :(
Today we can access, easily and cheaply (often free), almost every song ever recorded, every book ever written, every movie ever filmed, every video game ever made. You can write and reach thousands. You can film and reach millions. Twenty years ago, that was a millionaire’s life.
It’s the need for more and more and more that alienates us. Do you really need that shiny new car? Do you really need to take a vacation? Do you really need that promotion?
For some, work (and the status that comes with it) became their identity. Take it away and there’s nothing left. Others keep constant noise and stress around just to avoid hearing themselves think.
What if you chose a peaceful life?
He was always on the cutting edge of boobs physic engines.
We humans are predisposed to see anthropomorphic shapes in things. I understand why that could be interpreted as a face, but at the same time, it could just be a random shape. It’s just a “T” shape. Sure, it could look like a nose and a pair of eyes, but it could also just be... something.
From there, as I was learning Linux (I was 16 years old), I used KDE a lot. It was such a cool experience. I especially loved how easy it was to create custom themes, the desktop widgets, and Amarok! the big “killer app” back then. A music player that could show you song lyrics, album art, and even the band’s history by pulling data from Wikipedia and other APIs. It felt futuristic.
Later on, I switched to GNOME as it became more popular in the mid 2000s, but I’ve always had a soft spot for KDE. It’s been part of my Linux journey for nearly three decades.
Happy birthday, KDE!
Something similar might be happening in software. LLMs allow us to produce more software, faster and cheaper, than companies can realistically absorb. In the short term this looks amazing: there’s always some backlog of features and technical debt to address, so everyone’s happy.
But a year or two from now, we may reach saturation. Businesses won’t be able to use or even need all the software we’re capable of producing. At that point, wages may fall, unemployment among engineers may grow, and some companies could collapse.
In other words, the bottleneck in software production is shifting from labor capacity to market absorption. And that could trigger something very much like an overproduction crisis. Only this time, not for physical goods, but for code.
The real problem arises when non-technical people use an LLM to generate a full project from scratch. The code may work, but it’s often unmaintainable. These people sometimes believe they’re geniuses and view software engineers as blockers, dismissing their concerns as mere technical “mumbo jumbo.”
It’s like in literature if someone could patent the idea of a detective investigating a murder.
How could the "pokemon-like" genre even exist if you couldn’t create a game that uses “summoning and battling characters”?
Even worse, that description alone applies to multiple genres... JRPGs, or even fighting games with multiple characters (something like Marvel vs. Capcom) could fit that description.
I can understand intellectual property rights for very specific technical implementations (for example, the raycasting technique used in Wolfenstein 3D) but you shouldn’t be able to patent the concept of the first person shooter itself. That feels more like restricting freedom of expression.
It's hard to explain how advanced was Solaris at the time, specially Solaris 10 which had something named "Zones" which were actually some initial form of containers. With Zones you could run another instance of the OS completely isolated from the main Solaris (the kernel was shared, but for your apps would look like a native OS). You could even run another Solaris version! that was a cool approach to migrate a really old solaris 8 app to solaris 10 without having to change the app code.
Zones, combined with Sun Cluster or Veritas cluster would give you the ability to migrate those zones from one node of the cluster to the other (with it's own lun -external scsi disk/volume attached-) giving you some reaaaaaly interesting and new approaches to system design.
You can think about it as your dad's kubernetes.
Nothing like that could be done in linux at the time, and no one would use linux for any critical task, only for lamp servers.
Time has passed.
This new approach, however, often means you need to pay to use something that has already been produced, with its functionality fully available, but locked unless you subscribe. In that case, they are not really providing a service, they’re just holding a feature hostage until you pay. That isn’t a service; it’s basically extortion. If the car were free, I could understand having to pay to unlock it. But needing a subscription just to use my own car at full capacity? That’s dystopian.
I can totally see a TV that refuses to turn on until you’ve paid Samsung, a fridge that stays locked until you cough up more money, or a toilet that only lets you flush twice a day.Unless, of course, you upgrade to premium.
I keep seeing more and more vibe coded AI implementations that do whatever... by anyone. And managers celebrate that the new junior engineer created something that "saves a lot of time!" (two full time positions in their heads)
I agree it can be useful for some tasks, but the non deterministic nature of AI will inevitably impact production once someone plugs an AI tool into a critical part of the system, thinking they’re a genius.
> // TODO: If the user triple-clicks this button, the click handler errors because [xyz]
looks more like a comment than a real TODO to me. I agree that comments like those are useful, but shouldn't be a TODO.
A TODO implies a specific type of comment. One that implies a task, points to something that should actually be done (like TODO: This function should return another value with XYZ). And I agree that the proper place for that is a tracker, not buried in the code.
In the example just documents a bug. , there is no actual action.
In my experience, TODOs are often a way to get quick and dirty code approved in a PR. They usually never get done, they're just a way to push the responsibility onto some future developer who "will have more time" (which means it will likely never happen).
But besides that, if they consider that aliexpress is selling illegal stuff, they can easily block access to ali express in the country, decline all credit card transactions to ali express, block in customs any package coming from ali express... since is basically a criminal organization. I mean, they are selling the product in amazon.it and you put in jail a reviewer?
https://www.amazon.it/portatile-illuminazione-Joystick-integ...
I don't think putting in jail a customer that is just reviewing what he bought is the way to go.
So, Mark Cerny is contributing on the next Xbox? At the end, today all consoles are basically PCs with different frontends and storefronts (and that is also opening up, starting with xbox but probably PS will follow eventually)
As AlbertaTech says, “we make sparkling water.” I mean, what’s the mission? A can of sparkling water on every table? Spreading the joy of carbonated water to the world? No. You sell sparkling water because you want to make a profit. That kind of speech is just a way to hide the fact that you're trying to cut three full-time positions and make your employees work off-hours to increase margins. Or, like in this case, pay them less than the competition with the same objective.
Sam Altman might actually have a mission, turning us all into robot slaves, but that’s a whole different conversation.
First, HP bought Compaq to gain full ownership of the home computer market. That merger didn’t work out very well. Later, HP acquired Ross Perot’s EDS, attempting to enter the services business. The integration was, at best, chaotic and took several years.
It was a time of turmoil—every other morning you’d receive an email from Mark Hurd announcing layoffs affecting a percentage of employees.
Hurd’s focus was on increasing the company’s share value. He aggressively cut staff and reduced R&D investment (one of HP’s strongest traditions), essentially putting HP on life support. For example, HP-UX, which was relevant in the server market at the time, was completely abandoned.
When Mark Hurd was fired—accused of using company funds to give gifts to occasional partners (you know what I mean)—he immediately joined Oracle as an advisor, one of HP’s strongest competitors in the enterprise market at the time. Employees saw him as a traitor to the HP brand. Internally, many people hoped things would finally change.
What came next was completely unexpected. Leo Apotheker, from SAP, took over. He had this idea of transforming HP into a software and services company, essentially abandoning decades of tradition and letting one of the strongest brands in the industry fade away. He lasted only a few months—it clearly wasn’t working.
Then Meg Whitman came in. There was some initial hype around a hardware project called “The Machine,” which was supposed to revolutionize the data center by relying on memory instead of CPU power. That was never released. AWS had already emerged, and HP had no way to compete.
Whitman decided to split the company in two: HP (consumer hardware) and HP Enterprise Services (enterprise hardware and services). HP-ES eventually migrated most of its operations to India. Around that time, I accepted a WFR (Workforce Reduction) plan—since it was clear I’d be laid off sooner or later. Later, HP-ES was split again and became DXC Technology for services.
It’s incredible how a company that was once one of the strongest brands in the world—a tech giant and market leader for decades—went to hell in just three or four years. Bad management, a focus on short-term share price, and a complete lack of vision can bring even the most powerful company to its knees.
At the time, many said HP was simply too big for its own good, that it was impossible to succeed in so many markets. I don’t think that’s true. Amazon, Microsoft, Google—they all do what HP did in the 90s and 2000s, and more. It was just bad management. As always.
I agree that Military Companies are nasty thingys, but there is nothing INFAMOUS about SEGA model 2.
0 on that Project, but those 2 engineers will still be used on a different Project that needs just 2 Engineers.
BUT a company that sees that project as a critical part of the bussines and MUST tackle that project, will only need the 2 engineers in the payroll. Or hire just 2 instead of 10.
Engineers not hired = 8
Or.. maybe they don't really need that project that needs 10 engineers. They are ok as they are today, but they realize that with AI, they don't need those 2 engineers anymore to produce the same output, probably can be handled by just one with AI assistance.
Engineers fired = 1