Boy that "st" ligature in the subheading font is eye-catching, to the point of distraction.
I didn't read any more of the article after that, and the primary reason was just this weird font choice.
691–700 of 752 posts
Boy that "st" ligature in the subheading font is eye-catching, to the point of distraction.
I didn't read any more of the article after that, and the primary reason was just this weird font choice.
1. This isn't rooted in data but anecdotes "One Series E CEO told me that they’re re-evaluating the quarterly renewal of their engineering productivity software because they along with an engineer reimplemented something using Github and Notion APIs. They were paying $30,000 to a popular tool3 and they were not going to renew anymore." 2. These anecdotes are about tech startups spend, not your . Nor or they grounded…
Earlier quoted context omitted.
B2B is a large corp is like you describe, but it's very different in SMBs, and there are many, many more SMBs.
My experience is that SMBs are generally not run by people who feel confident doing any kind of self managed IT. No amount of LLM usage is going to change them into full stack vibe coders who moonlight as sysadmins. I just don't see it happening. Not until, that is, a new generation, that has grown accustomed to the tech, takes over. Until then the current SMBs will for the most part fulfill their IT needs from SaaS…
It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible…
OTOH, I was hired by an enterprise that was many months into a giant backend rewrite. After wrapping my head around the many plans, I realized they were rewriting Django, badly. One weekend I prototyped the whole thing… in Django. It worked. It met the specs. It was a CRUD app with a REST API. I came in to work Monday morning, showed it off, and inadvertently triggered a firestorm. Later my boss told me not to do tha…
Earlier quoted context omitted.
This is the prime example of Law 1 of Robert Greene's "The 48 Laws of Power": "Never Outshine the Master." The core principle is to always make those above you - your bosses, mentors, or superiors feel comfortably superior. If you display your talents too aggressively, you risk triggering their deep-seated insecurities, which can lead them to sabotage your career or remove you from your position. Galileo Galilei hand…
Sure it has been codified into a "law" but really this is just basic social skills / emotional intelligence which engineers on the spectrum struggle with. If you've spent any time in a large enough organization you realize quickly that hierarchies form based on status, power and influence & not necessarily technical merit. No it's not "the best person for the job" that rises up and tells you what to do. Casually solv…
Earlier quoted context omitted.
Software got easier to develop, but we just came up with more problems to solve with software. The new tools didn't shrink demand for COTS enterprise software - it grew massively since the 90s!
This is what I want to be true, but as someone’s at the middle of their career I’m terrified.
Earlier quoted context omitted.
It that works, nobody would be using Jira anymore, because people would just use a competitor that's cheaper or vibe code their internal Jira tool. Somehow that has not happened yet in 2026.
The market seems convinced it will happen, considering its stock price is in the gutter
It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible…
Moving SaaS apps in house is a great way for a VP to get a fat bonus or a director to get a promotion but I have to imagine it keeps the CIO/CTO up at night unless they're fully asleep at the switch.
It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible…
A huuuuuge part of why companies, especially public companies, especially those in regulated industries like healthcare and finance are willing to pay eye-watering sums of money for a SaaS app that you could get an MVP up in a few weeks time from a competent team with no AI is that they need a phone number to call when something shits the bed at 2 AM on a Wednesday. They need support SLAs without the payroll and head…
Earlier quoted context omitted.
This is the prime example of Law 1 of Robert Greene's "The 48 Laws of Power": "Never Outshine the Master." The core principle is to always make those above you - your bosses, mentors, or superiors feel comfortably superior. If you display your talents too aggressively, you risk triggering their deep-seated insecurities, which can lead them to sabotage your career or remove you from your position. Galileo Galilei hand…
Sure it has been codified into a "law" but really this is just basic social skills / emotional intelligence which engineers on the spectrum struggle with. If you've spent any time in a large enough organization you realize quickly that hierarchies form based on status, power and influence & not necessarily technical merit. No it's not "the best person for the job" that rises up and tells you what to do. Casually solv…