-
damn Johnathan Blow is not afraid to give you the cold hard opinions. If you want to be good you need to spend your early most formative years doing hard things, because you will not do it later, then goes on to say you should not do anything related to web development during that time as it will rot your brain.
Note
This post is a thought [1]. It’s a short note that I make
about someone else’s content online #thoughts
References:
[1]: /thoughts/
Publishing rhythm
-
Thorsten is always a great listen with well thought out answers. I thought the advice “all you have to be is good” from his is so great, so many people focus too hard on credentials and certificates, they miss the time in the saddle and raw, just being good at what you do. They talk a lot about industry trends and that ai/llms have been here long enough to see that they are the new iphone. In some way you need to learn to work with them. Much of the minutia is churn, it will change and we will forget about it in six months. Working at amp right now is really trying to focus on releasing exactly the right thing and not everything. We’ve been given these great models that can churn out poc very quickly, it is our job to focus on what the right thing to adopt is.
Note
This post is a thought [1]. It’s a short note that I make
about someone else’s content online #thoughts
References:
[1]: /thoughts/
-
Thorsten is always a great listen with well thought out answers. I thought the advice “all you have to be is good” from his is so great, so many people focus too hard on credentials and certificates, they miss the time in the saddle and raw, just being good at what you do. They talk a lot about industry trends and that ai/llms have been here long enough to see that they are the new iphone. In some way you need to learn to work with them. Much of the minutia is churn, it will change and we will forget about it in six months. Working at amp right now is really trying to focus on releasing exactly the right thing and not everything. We’ve been given these great models that can churn out poc very quickly, it is our job to focus on what the right thing to adopt is.
Note
This post is a thought [1]. It’s a short note that I make
about someone else’s content online #thoughts
References:
[1]: /thoughts/
Ping 59
"All you have to be is good"
[source](https://www.youtube.com/watch?v=thMFsqe8kbQ)
Not sure if this is a quote from somewhere but thought it was some interesting
advice that @thorstenball received when he was starting into web development.
He asked a friend already in the industry if he thought he had a shot. He had
no degree, no credentials, no experience at the time.
remember rule 4
I almost for got Rules [1] 4 today, rollout when smooth late in the day right
before a vacation day (terrible time to deploy I admit not my clearest plan).
Race conditions are a b****, all around on this one. The app I was concerned
about won the race to deploy first and was fine by itself, then another app had
a race condition inside itself that killed it
References:
[1]: /rules/
-
Hilarious ai episode of the office. all sort of flaws. nailed the personalities.
Note
This post is a thought [1]. It’s a short note that I make
about someone else’s content online #thoughts
References:
[1]: /thoughts/
-
one minute in, I cannot believe Prime has never used a password manager. For all the shit they give Trash for his one password, He does not use a password manager!
Note
This post is a thought [1]. It’s a short note that I make
about someone else’s content online #thoughts
References:
[1]: /thoughts/
-
Prime on Big A they make a really great mix. I really like primes perspective on the layoffs here. Adding in an ops perspecive a bit here. Maybe inspiring a full level post. infra, ops, sre roles are incentivised to keep uptime, that is your goal in these roles. Idk how it works on big products, its probably more greased, higher stakes, more well thoguht out, more well discussed. In my role for many small internal applications developers constantly use my platform different and find new edge cases that we never expected to hit. Depending on my week I’m either the team blocker and I’m fighting fires all week making sure new releases are getting out and stay running while everything is breaking, or I’m tending to the fire lanes, predicting the new edges, looking at previous outages and asking myself how do we never see this category of failure again. I think AI is really good a enabling both of these. I think you can probably run a leaner team with AI on the latter half. AI is really good at implementing things consitent (if you are careful) and fast. But when shit hits the fan, you still need the people who know the systems to get things back up quickly and prevent a cascade o...
-
What a great way to start a Wednesday morning with a fresh brand new tiny desk concert with the Foo Fighters. The killed it, love the classics.
Note
This post is a thought [1]. It’s a short note that I make
about someone else’s content online #thoughts
References:
[1]: /thoughts/
agents are never done
Agentic coding has this nice trick of letting you bang out a project in an
afternoon, something complex that would have take some real time to implement,
not just some rounding error that can slip right in between the jira board.
Then it will be perpetually never done. There will always be bugs and thorns
rear their head up, new features no one ever thought of, and now no one really
has to think much about beyond having the idea.
This part of software engineering has always been here, its the root of the
never complete 200 side projects. But now it feels like fuel has been poured
on the fire, like we can get more done than ever. But we are tricking
ourselves, these projects will never be “done”. There’s always more to add.
Without feeling any of the pain of implementing it yourself, why not just keep
adding new features forever. This is the mentality that is crushing me right now.
It pulls at your token anxiety like crazy. You look at the usage board and you
are almost cooked so y...