linton

A mental model for working with coding agents is that they're blind squirrels running into a maze and bumping into walls. You must place the walls (verifiable constraints) strategically so that they end up in the general region you want them in.

@NotionHQ d o i t

🤔💭🪩

@hagaetc 100% Trying to be happy and relaxed all the time is an easy way to guarantee a bad life

+1 your feelings and emotions are experienced on a limited scale so you might as well throw yourself into something hard, the downside is not that big. In fact our natural state as evolutionary creatures is to deal with stress and discomfort all the time.

Being sociable is a skill Self-isolation is addictive so much more harmful than you realise The world expands and opens up for those who are people-centric, just as it shrinks for the introverted and nervous Don’t fall into the trap of being a lone wolf

@fedesimio @paulg And not even the whole social media app. It’s just the infinite scroll feed that’s responsible for 90% of unhealthy tech habits

@paulg But phones are just a platform through which you can use multiple apps. I bet social networks are >80% of the cause.

If Steve Jobs were still alive, he would have the moral authority to face and maybe even to solve this problem. But I doubt anyone in the phone business now does.

@Jeyffre Yep, you gotta get the edge from somewhere

Your ability to grind is not what separates you from your peers. In India, Singapore, and China, grinding is part of the culture. Grinding is necessary but not sufficient. Your ability to grind with uncertain and delayed payoffs is what separates you from your peers. If you only chase things that appear to be certain, you enter the same crowded trade as everyone else. That only works if you have some other ace up your sleeve besides your ability to grind.

Can we bring back the Windows phone? I think the world lost something valuable when Microsoft abandoned it.

@SrinivasanSS52 Rust is on the upswing with surging demand?

Rust Developers get "paid" more than C++ or Go or Python what could be the reasons?

@ayushagarwal @dodopayments Love this!

we are built so much infra in-house that we can abstract and create ton of saas and open source projects. i just created one open-source project today, excited to ship it soon.

@bhalligan What about Kind Truths? 🧐

I don't remember where I found this, but its spot on.

@ConnerBean Yep, I think every org should calculate the dollar cost of all their meetings every quarter and track that as a KPI. Hopefully then they’ll realise how expensive these meetings are and drive those costs down

If you're still having engineers spend the majority of their time trapped in meetings, you've already lost

@DhravyaShah Never meet your heroes :((

todays learning: many people you respect and look up to, and have known for years are completely hostile and rude for no apparent reason. it's actually kinda sad. anyways. back to building

@e2e_developer @icanvardar Spot on! Don’t attack the man, attack the argument. People who give personal criticism are not being constructive. And inversely, people who perceive criticism of their argument/behaviour/decision as a personal attack are also not being constructive.

@icanvardar The difference lies in whether the criticism is directed at the person or at the behaviour. Most people are not good at providing feedback without making it personal. And most are not good at receiving criticism without feeling personally attacked.

when people dismiss your work, that's not constructive criticism. don't normalize it, it erodes confidence and distorts decisions until you doubt yourself. not all criticism is harmful. sometimes it's blunt honesty and the issue is your filter

@tylerangert Is there really much of a stigma around frontend work? I assumed people respected frontend devs more because it’s harder in a lot of ways than backend work

What’s funny about the industry stigma against frontend work is that before the internet, basically all programming was “frontend” in a way. Eg it was all about graphics, local performance, proper memory management, etc. sort of “back of the frontend” work all baked together. The service-ification of algorithms + compute has created an artificial divide between where “real work” lives software

@Glenn6 @aashatwt Exactly. Either companies will realise they still need good devs like they did when they experimented with no code tools, offshoring, etc…, or this is something entirely new

@aashatwt that's either the best or worst career choice right now and i can't work out which

literally crazy that my irl friends still learning coding to become a software engineer

A leading indicator for PMF is customer complaints. If someone complains about something broken in your product then you know that they care enough about the solution to have unmet expectations. If all you get are compliments then odds are that your users are trying to spare your feelings and your lagging indicators - your churn and retention metrics, will give you a rude shock one day. That’s another reason why it’s important to ship before you’re ready, besides the benefits of rapid iteration and more customer insight from running more experiments. This piece of advice is so hard to follow, speaking from personal experience. Every engineering & perfectionist instinct in your body needs to be resisted. It feels obvious as a builder that a potential user might reject your product if it’s not polished enough. But think about how many times you’ve tolerated a broken button or a clunky UI because you needed to get something done as a consumer.

@won__sikkk @housecor As they should. I can’t imagine a small team setting up a CI server and a Terraform repo to manage their infra. That would be overkill

@housecor Two-person team advantage: no change approval boards, no long-lived branches, no politics. We just push, test, and ship. Small teams skip half this list by default.

In 2026, many dev teams still fail to get the basics right. Click ops No CI server No feature flags No automated tests Long-lived branches Big, ambiguous tickets Change approval boards Infrequent, manual deploys Many long-lived environments I still often see all this.

@poteto Everyone in the world, including all the cooks?

everyone is cooking but who is eating

@luluneverstops @incentivising It’s absolutely tragic when someone’s doing everything right but fails because they’re in the wrong place :(

@incentivising yup competence is only useful when it sits where opportunity can see it. you can be excellent in the wrong room, under the wrong label, solving the wrong visible problem, and stay invisible for years. positioning creates the frame before merit gets judged

I've watched highly intelligent people with every possible structural advantage lose to someone intellectually inferior. While the genius optimized for merit, the latter optimized for positioning. Not skill or resources, nor intelligence, but pure positioning. This made him visible. And most modern environments favor leverage over merit. It's the arrogance of competence, and you must realize that pure merit without an overarching strategy won't get far.

@arturchyk9 @thdxr If you’ve got something that helps you see things differently and step outside that box, you probably have a massive advantage

@thdxr I agree. It is likely because programming is a selective factor for a specific type of mind, with outliers ofc. However, the mind can be changed; it is a flexible construct.

programmers are so good at rationalizing themselves out of building things that work for a lot of people it's why programmer takes on business are usually exactly backwards