spsaaibi 
kellanWhere is the content talking about contemporary software development issues? Like "How to migrate away from GraphQL?", "Maintaining software that was written by a team twice this size", "HTML and CSS for React Engineers", etc?
"Hiring Practices for for Teams where People Don't Quit Every 18 Months"
“How small a Kubernetes cluster is too small?” (Via https://mastodon.social/@xahteiwi/111555598574504813)
"Your aren't running MySQL/Postgres, thats Aurora in a trenchcoat"
Kristin Davidson {kxd}@kellan I’d say probably a raspberry pi pico. You might lose it!
Jan Lehnardt 
@kellan oh I can write that one! The others, I wanna read, badly.
Thomas Vander Wal@kellan Does this have a follow-up article for how to spend less than 1/4th of your time convincing people today is not a good day to rage quit, and it will get better.
kira :3@kellan "hiring practices for teams where the ceo might fire 10% of the company to make himself richer"
dave@kellan "Maintaining software that was written by a team twice this size" is one hell of a kick in the nethers.
xmlns="Dan"@kellan Are people migrating away from GQL? We're still in the middle of a migration to it. :(
@divclassbutton it's a fundamentally terrible idea, and yes, it's falling from favor.
@kellan Oh its 100% a bad idea, but plenty of bad ideas manage to carry on for years.
Drew Blake@divclassbutton @kellan and why is it a fundamentally bad idea? We’ve had succes with it at <90ms even at P90. Prevents overfetching, and allows the front end to define new views without requisite backend changes.
Brody Berg@drewble @divclassbutton @kellan it’s not a fundamentally bad idea it’s just like everything else: not the solution to all problems
Jeremy List@Brodyberg @drewble @divclassbutton @kellan yeah it's an adequate solution to the problem it solves, which is not the problem I would expect something called GraphQL to solve.
Stephan@kellan @divclassbutton can you please shortly outline the major problems of GraphQL and what would be your recommendation for a replacement?
Jamie McCarthy@durchaus @kellan @divclassbutton I think whole books could be written on this subject, but my personal take is that it encourages sweeping issues of scale, performance, and even correctness under the rug. It facilitates splitting teams in a way that can leave important questions no one’s responsibility to answer. By the time teams realize their software has a problem, I imagine, it may already be too late.
Alper Çuğun-Gscheidel@kellan @divclassbutton What do they go to? Plain REST?
Aleš Roubíček@alper @kellan @divclassbutton Frontend team must own their APIs on the backend. If it doesn't, it will always underdeliver. We use CQRS style APIs, I won't call them GraphQL nor REST.
@alesroubicek @kellan @divclassbutton That sounds like a frontend team in a very large organisation.
Su-Shee@kellan "my journey to the cloud and back again" by billable hours baggins - "platforming and de-platforming" "shuffling platforms around for the fifth time" "building platforms on hardware, building platforms without hardware, building platforms back into hardware"
@kellan uh another good one: getting out of the data swamp and a classic: you don't have big data
Jan Katins
@kellan May need one for how to staff your product development team during a hiring freeze and you were still two roles and skill sets short of a complete team. In addition we like the initial progress on the new product development, to reward you we are cutting 60% of your team. But since you are also doing so well we are adding 3 other products that can't get started to you to lead, but they don't really have any staffing either.
Evan Prodromou@kellan "Having a team of Xooglers isn't as prestigious as it was a few years ago"
@kellan I’m sure there is a great article in this unfound location for the, “How to handle the emotion and cognitive stress reading a leadership email finally embracing automation of most everything (after years of pushing that idea and just doing it without approvals) and the next email is from HR giving you a heads up the contract for the automation team has been terminated”
Michal Migurski 🍉@kellan Head First YAML
Sophie@kellan oh wow, this would be my specialist subject. I should write some stuff
Alexander Thurow„How to create a team that writes code so dead boring, that you actually ‚feel kind of ok‘ to be woken up at 3 a.m. to investigate a pressing cloud issue?“
… which of course leads to the natural follow-up question of:
„How to create a blameless engineering culture with a just incentive system that creates creative, energized and resilient teams?“
Matthew Skelton@alexthurow 👏 yes, please !@kellan
@kellan I'm pretty sure this resource also has an article on "How to discuss with the Sr. Director of IT (who isn't technical) that the data aggregation and synchronization team should not be called the Web Hookers and the t-shirts made for them should not be deliverd”.
Josh Grant@kellan somewhat side note but I did not even think about the maintenance impact of the ridiculous amounts of layoffs over the past year or so
Florian Haas@kellan "Post-Kubernetes Stress Disorder: diagnosis and therapy"
Aidan Harding@kellan I searched for Choose Boring Technology and found that the author was managed by you. Huh. Seems to be at the root of a lot of this and I guess you're well aware. It's one I refer to a lot so thanks for inspiring him
https://mcfunley.com/choose-boring-technology
https://mcfunley.com/choose-boring-technology
Latte macchiato 
@kellan "How to adapt to a new framework bought by C-level suite without previously asking"
Bill, organizer of stuff@kellan Just completed a self-paced course on "Writing a Webserver Using Serial Output on An Underpowered Microprocessor Using Copy, Paste, Trial, Error, and A Mess of Jumper Wires," myself...
a*lfonso adriasol&@kellan maintaining software built by a team 10x this size!
Scale up with microservices, scale down and learn about Conway's corollary
NoSQL but want reports that are consistent and fast
How to delete terabytes of data you are not supposed to be holding on to
What happens when pagerduty is shut off and slack is replaced with Teams
Build with the best, fire em all, maintain with the cheapest, fire em all again, go cheaper, after all nerds are nerds, replace em with chatGPT
Scale up with microservices, scale down and learn about Conway's corollary
NoSQL but want reports that are consistent and fast
How to delete terabytes of data you are not supposed to be holding on to
What happens when pagerduty is shut off and slack is replaced with Teams
Build with the best, fire em all, maintain with the cheapest, fire em all again, go cheaper, after all nerds are nerds, replace em with chatGPT
Max Lee 
@aadriasola @kellan
"How to delete terabytes of data you are not supposed to be holding on to"
And how to find all the places they were automatically backed up and manually copied to
"How to delete terabytes of data you are not supposed to be holding on to"
And how to find all the places they were automatically backed up and manually copied to
Richard Crowley@kellan “Sometimes putting it on one server is fine, actually”
Roma Komarov@kellan Re: “HTML and CSS for React Engineers” I think the https://css-for-js.dev/ by Josh is one that comes to mind right away.
Though, I agree, this is a topic that is worth talking about more widely and not only as a part of the paywalled (good) content.
@kizu nice!
Matt May@kellan @slightlyoff "Reconsidering Life Goals for Career Tech Folks"
Kevin Boyd (he/him) 🇨🇦
Oliver Maksimović@kellan how would you call this thing: Promote all good devs to management positions, then hire whoever you can to make up for those devs, but after years of such practice still not be able to figure out what the f is going on
twifkak@kellan "How to pretend you're interested in building a product that is both boring and useless using tactics that will obviously fail and a strategy that means none of the effort will matter in 5 years."
Jocelynephiliac 
nobletrout@kellan "Reinventing the wheel to keep rockstar developers happy isn't as amazing as you might think."