@GergelyOrosz is right. From my pov there are two reasons to write your own stuff, even if it's a struggle. First, it's fitness training for your brain. If you struggle to write, your brain is flabby. Having a fit brain will be a key differentiator in the new era. And second, we would all rather read your "bad" writing than polished AI writing. Trust me on this one. We can spot even one sentence of AI writing and it stinks. Your bad writing is fine. Just do more of it, every day, to get in shape and stay in shape.
Almost 6 million people have watched the interview with @ZelenskyyUa in just 3 days!
A conversation I will never forget.
He spoke in Ukrainian, we both had ear pieces in with human translators in a room next door, and we translated what he said into English afterwards.
The single most important career advice i could give someone would probably be: dont be convenient to your boss, solve his problems.
Most of the time doing this requires being inconvenient in the short term. Asking a lot questions, making him prioritize, setting boundaries on your time, making him focus, holding him accountable, etc. are necessary to genuinely understanding what his problems are and deliver the most value to him without overworking yourself.
Get good enough at this and you become indispensable such that he will throw money and freedom at you to keep you around.
If, in contrast, you never tell him no, never be inconvenient, never ask for clarity beyond “how high” anytime he says jump, and just take on every task he gives you, you will almost certainly burn out doing a fuck ton of menial work that doesn’t actually matter to him for low pay. And when you try to leave he’ll just say “kind of annoying i have to find another but they were a dime a dozen so no biggie”
Дивлячись на Париж я все більше пишаюся Україною та Києвом.
Під час революції Гідності не було розграбовано жодного магазину, не було знищенно жодної церкви чи каплички. І при цьому бій був не на життя, а на смерть.
Черговий раз стає зрозуміло, чому Путін вважає, що Європа не готова до війни.
Why are you still using pull requests?
Is it for code review?
If so, do you really think your or your colleagues catch bugs and mistakes that an Opus 5.5 or Fable or Astra won't find? You can literally spawn all three of them and have them check four times each.
(Also, don't tell me you don't have a "stamp plz" Slack channel or group chat somewhere.)
Is it for knowledge sharing?
Surely there's better ways for that now than the PR, no? We have models that can generate explainer videos, presentations, podcasts, games, quizzes, walkthroughs, ... for any piece of code it can reach.
Is CI the reason?
Well ackshually, CI means continuous integration and its original meaning is the *opposite* of having long-lived branches and PRs.
But, leaving that aside, your agents are hopefully already running the tests before they push something, and hopefully they can run as long as they want and don't block you so they can run the whole test suite and generate "irrefutable proof" and end-to-end demo videos and so on... And so they run the tests and confirm and then you push to a branch and everything runs again and then you merge and then it runs again? That doesn't make sense, does it?
Maybe you work in open source and you accept contributions, in which case I can't speak to the value of pull requests. It's been 2 years since my last OSS contribution. But from what I heard, the time of the PR is coming to an end in OSS too?
I honestly don't get why people still stick to PRs.
With agents you can now move 10x faster, you can finally do real continuous integration, and get more confidence in the changes the agent made.
Don't slow yourself down by having all the changes pile up in a PR.
Launching Keepsake in Early Access today!
Save little things you care about.
Then search them with 1 shortcut.
People need no "second-brain" bs. What they need is ability to capture and find again small joys that excite them.
Local & offline.
Get it:
https://t.co/H0bhLvOQCe
There's some senior engineers on here who, in the face of AI changing the very structures this industry is built on, present themselves as Stewards of the Craft of Programming.
Bugs the hell out for me.
They keep alluding to the virtue of doing things by hand, the value of Good Code and of craftsmanship, saying that yes, AI might change some things, but hey it won't ever change the value of something done with proper care, by hand, just like in the olden days of 2024. Most everything that was Good back then is still Good now: deep knowledge of languages and systems, good code, great architecture. You know the sermon.
And, yes, some of that *is* true. At least I think so. But we don't know, because no one truly knows what will be important in the future.
We're going through times of great change and I think the best advice to give to young people and others who want to have a job and provide value is: keep your eyes open, rethink from first principles, derive from what businesses value what you can provide; the digital world is more malleable than ever, you should rethink how you can help shape it.
All this pounding on the Bible of Good Code seems to me to be doing the opposite: it lets people feel comfortable -- what I've valued all my life is still valuable, I can rest easy -- in times when one shouldn't feel comfortable. This is a bumpy, exciting, strange ride. If you lean back you might fall off the waggon.
Let's not delude ourselves and others that we can keep doing what we've been doing. Rethink it all.
And, like I said, it bugs the hell out of me seeing senior engineers (that are secure in their career) talking as if there's nothing *really* to change, because the Fundamentals will still be valued. They might!
But it's the wrong advice to not rethink everything right now.
the right way to use model capabilities is not to ship 10x more features to prod
it's to spend more time understanding your users, trying experiments, building prototypes, learning about things you don't understand so that you can ship things that actually work
My small programming tricks:
- ci and cicd commands that automate running CI and CI/CD
- make ci - same, but local in Docker. This is my pre-commit hook.
Inspired by https://t.co/AvLv7gI0Dl
Favorite use of Claude this week - https://t.co/CbttwBAzzg with access to CI/CD and asking it to analyze where time goes and optimize. 50% speed up on one pipeline and 35% on another. Took 2 minutes total to write a prompt and review a PR, and the whole team will benefit.
Threads blocked my account for absolutely no reason and there is no way to contact customer support. What an app, magnificent! But one less social media to doom scroll with :)
Though now I'm wondering if Google or Apple can randomly disable my accounts...