Tejas retweeted
i’m hiring a forward-deployed product engineer at Elm AI!
elm-ai.com/careers/forward-d…
someone who wants to talk to customers, figure out what actually needs building, and then build it.
new york / london
a bit about the work:
The cost of not being curious is the highest right now.
We no longer need devs who just tick off tickets from their boards. Agents have gotten pretty good at it. What we need are curious people. Who are willing to go into a rabbit hole on weekends, learn something new, experiment, break things and come back knowing something. The good thing about LLMs are they have made this entire process a lot simpler and faster. There's literally no more friction in learning something new.
Funny part is curiosity is also something that makes u good with agents. Your output only depends on how well u explain the thing and you cant explain something clearly you were never curious about.
we used to do a weekly bug bash. find bugs, file tickets, wait for someone to pick them up
this week we skipped the tickets and created devin sessions instead. same effort as writing tickets but wayy different outcomes
one hour. PRs merged the same night
2
218
using @t3dotcodes for 2 weeks now. initially was reluctant to move away from my cli based workflows but glad I did! added significant productive gains.
the inline html rendering and opus spawning codex agents frictionlessly are probably the two best features for me so far!
Great job @theo and team!
2
178
ai is great at finding the 20 year old bugs and equally great at writing the next 20 years of them. we're speedrunning both ends
Everyone: "Vibe coding is causing all these security bugs"
Reality: PHP, Node, Linux kernel, GitLab. All hand-written code by humans, some of it 20 years old.
AI isn't creating the slop. It's finding it 🫠
70
My college email got deactivated. I wonder how many other accounts I'm about to lose access to 🫠
So over the weekend @theMehtaParth and I built Lapse. It uses @falkordb to map which of your accounts depend on each other, so you can trace a lockout before it happens.
Then AI agents walk that graph to plan the fix and actually carry it out, all from a Telegram chat.
Our submission for GraphHacks by @WeMakeDevs 🤞
@kunalstwt
It’s been ages since my last hackathon, but man, I've missed it sooo much. The satisfaction of seeing everything running perfectly is unmatched atleast until something breaks and you spend hours figuring out what went wrong
2
109
Tejas retweeted
im hiring our founding gtm lead!
probably one of the highest impact roles in the company right now
supply chain ai today, is what coding ai was in 2023 -- super early, barely any adoption, healthy skepticism.
we know how ai coding turned out, and it's obv supply chains are an *even better* application.
we are already working with some of the worlds most complex supply chains proving that this works incredibly well, and we want to scale fast!
work at the most impactful vector for ai diffusion.
(apply and dm me if interested)
You can’t outwork the whole world. There’s always going to be someone somewhere willing to work as hard as you. Someone just as hungry. Or hungrier.
Assuming you can work harder and longer than someone else is giving yourself too much credit for your effort and not enough for theirs. Putting in 1,001 hours to someone else’s 1,000 isn’t going to tip the scale in your favor.
What’s worse is when management holds up certain people as having a great “work ethic” because they’re always around, always available, always working. That’s a terrible example of a work ethic and a great example of someone who’s overworked.
A great work ethic isn’t about working whenever you’re called upon. It’s about doing what you say you’re going to do, putting in a fair day’s work, respecting the work, respecting the customer, respecting coworkers, not wasting time, not creating unnecessary work for other people, and not being a bottleneck. Work ethic is about being a fundamentally good person that others can count on and enjoy working with.
So how do people get ahead if it’s not about outworking everyone else?
People make it because they’re talented, they’re lucky, they’re in the right place at the right time, they know how to work with other people, they know how to sell an idea, they know what moves people, they can tell a story, they know which details matter and which don’t, they can see the big and small pictures in every situation, and they know how to do something with an opportunity. And for so many other reasons.
So get the outwork myth out of your head. Stop equating work ethic with excessive work hours. Neither is going to get you ahead or help you find calm.
[The Outwork Myth — It Doesn't Have To Be Crazy At Work, 2018]
Frontier LLMs are doing too much when it comes to editing code.
I'm excited to share this work on the Over-Editing problem which refers to models modifying code beyond what is asked of them.
The main findings are:
- Many frontier models Over-Edit with GPT 5.4 being the biggest culprit
- Reasoning models have a higher natural tendency to Over-Edit compared to their non-reasoning counterparts
- RL is the best approach to train models to perform minimal code editing while preventing catastrophic forgetting compared to SFT, DPO and Rejection Sampling.
Blog and details below!
can't believe we still do not have linux support for codex app!?! @thsottiaux
1
69
Tejas retweeted
With agentic slop, we are trading software reliability for shipping velocity and calling it progress. It isn't. Systems are more fragile than ever, and engineers building them no longer trust their code to hold up in real-world edge cases.
I am pro-AI, but this will backfire - big time.
















