- Some of us intentionally avoid FAANG for that reason.
- So, I think there are two models.
One is a "one junior per team" model. I endorse this for exactly the reasons you speak.
Another, as I recently saw, was a 70/30 model of juniors to seniors. You make your seniors as task delegators and put all implementation on the junior developers. This puts an "up or out" pressure and gives very little mentorship opportunities. if 70% of your engineers are under 4 years of experience, it can be a rough go.
- This was at the beginning of game design. Everyone was still learning what good game design was and it kept changing as the technical constraints changed.
- Just remember that the market can stay irrational longer than you can stay solvent.
Consider diversification in your portfolio. Maybe you divert a little more away from the US market, for example, which is heavily dependent on 7 stocks largely tied to AI.
- There are a wide number of small problems for which we do not need bridges.
As a stupid example, I hate the functionality that YouTube has to maintain playlists. However, I don't have the time to build something by hand. It turns out that the general case is hard, but the "for me" case is vibe codable. (Yes, I could code it myself. No, I'm not going to spend the time to do so.)
Or, using the Jira API to extract the statistics I need instead of spending a Thursday night away from the family or pushing out other work.
Or, any number of tools that are within my capabilities but not within my time budget. And there's more potential software that fits this bill than software that needs to be bridge-stable.
- Why? It turns out that I try to read people who have a different perspective than I do. Why am I trying to read everything that just confirms my current biases?
(Unless those writings are looking to dehumanize or strip people of rights or inflame hate - I'm not talking about propaganda or hate speech here.)
- I really enjoyed the garden there - we spent hours happily. And we don't have a lot of palaces where I'm from.
And I didn't really enjoy the Louvre, especially compared to Musée d'Orsay and Centre Pompidou.
- CTOs are the original vibe coders.
- > Can "AI" in its current form deliver value? Sure, and it absolutely does but it's more in the form of "several hours saved per FTE per week" than "several FTEs saved per week".
Yes but...
First, what we're seeing with coding is that it is just exposing the next bottleneck quickly. The bottlenecks are always things that don't lend themselves to LLMs yet.
Second, that still can mean 4 hours a week for 20-50 bucks. At US white collar wages, that might mean 8 people are needed rather than 9. In profit centers that's more budget for advancing goals. At cost centers, though, that's a reduction in headcount.
- It's more nuanced. If I even have a few lines I can prove are mine, those parts are copywritable in the same way Pride and Prejudice is public domain but pride and prejudice and zombies is copyrighted.
- It's much harder on many surgeries. They come in with "it depends" and completely avoid discussing it. The doctors often do not even know, and those who know will refuse to discuss. On top of that, consultations are not free and often expensive.
And something like cancer treatment is nigh impossible to get a quote on. They obfuscate the costs even when required to post them - see https://www.healthcaredive.com/news/hospital-price-transpare... as but one example.
There is an entire industry built around reading hospital bills and watching for double charges. https://www.tomshardware.com/tech-industry/artificial-intell... was discussed earlier on HN.
- We have a price for the total infrastructure spend per dev, and that includes things like AWS prices and all of the tooling like jira and github.
But you absolutely shouldn't have to pay for your own tools. (That said, blue collar people often have to, unlike us, and that's also awful.) But also, it's their productivity. If you are all laboring under the same constraints, it's their choice to make if they care about your productivity.
- We are getting to storage solutions already. But I think many of us think nuclear for base load and massively overbuilt solar and wind so that we can handle the full electrification of our system would be a net economic win as well as an environmental one.
Also, consider that we have a connected grid outside of Texas and that the weather is not usually bad everywhere.
- That was my first thought as well, but interfaces that take care of pluralization with an i18n framework can handle all of these.
It just takes longer and is at the expense of another feature. In truth, it mostly takes more skill - once you have that skill, it's another 5 minutes. There are a few edge cases, but you largely have the necessary context to translate a string. You have to translate the string in its entirety instead of relying on composition of translated chunks. (This is already best practice.)
- Since when did Google pay attention to implementation bugs?
- If you are large enough, you will need an ops team to manage allowing your developers to write terraform and manage AWS costs already.
If you are small enough, you are not going to be truly affected by downtime. If you are just a little bigger, a single hot spare is going to be sufficient.
The place where you get dinged is heavy growth in personnel and bandwidth. You end up needing to solve CPU bound activities quicker because it hurts the whole system. You need to start thinking about sticky round robin load balancing and other fun pieces.
This is where the cloud can allow you to trade money for velocity. Eventually, though, you will need to pay up.
That said, the average SaaS can go a long way with a single server per product.
- They're put in git. You treat it like any other source. You might even have them as a set of shell scripts.
- I know Workday is working overtime on this. I’m sure Oracle and others are too.
SAP is giving companies a reason to switch and that’s always a scary moment.
- It helps that you can have the "free" labor document the processes and build the plan.
Otherwise, it's going to be a very frustrating experience to move a number of things.