> Look at his CV. Tiny (but impactful) features ///building on existing infrastructure which has already provably scaled to millions and likely has never seen beneath what is a rest api and a react front end///
Off the top of my head he wrote the socket monitoring infrastructure for Zendesk’s unicorn workers, for example.
I DON'T know the guy, but Zendesk isn't a flex IMO
I certainly don’t agree with everything Sean says and admit that “picking the most important work” is a naive thing to say in most scenarios.
But writing Python in production is trivial. Why would anyone lie about that? C is different OTOH. But just because you do a single config change and get paid for that doesn’t mean it’s true for everyone.
Also, staff at GitHub requires a certain bar of excellence. So I wouldn’t blindly dismiss everything just out of spite.
The guy is full of shit.
Look at his other blog spam
The formula for prioritizing is literally this simple: Am I working on the most important thing right now? If not, drop what I’m doing and go do that
Utter trash.
Look at his CV. Tiny (but impactful) features ///building on existing infrastructure which has already provably scaled to millions and likely has never seen beneath what is a rest api and a react front end///
I know this type. I AM him. Exaggerating my way through roles saying the right things through self promotion at the right times.
> I’ve also written Python and C in production
Absolute miss truth. A single line edit to existing applications/a pet project CGI server.
This is EXACTLY what I do.
Appreciate the hustle, but don’t assume “because github + writes blog = knows things”