Annamalai (@asvny_) header
Annamalai (@asvny_) profile picture
Melbourne, Victoria
Joined July 2015
Photo by Annamalai (@asvny_)Photo by Annamalai (@asvny_)Photo by Annamalai (@asvny_)Photo by Annamalai (@asvny_)Photo by Annamalai (@asvny_)Photo by Annamalai (@asvny_)Photo by Annamalai (@asvny_)Photo by Annamalai (@asvny_)
Annamalai retweeted
Sridhar has shared the difficult decision we have taken to skip appraisals this year, given the rising costs and uncertain outlook for the software industry. Every software business will be having this discussion and making difficult choices. These are real-world situations where there is no single right answer. The decision depends on what we choose to prioritise. These are also decisions AI cannot make for us. During COVID, we made a similar decision. We offered free licences to customers, even though it meant losing revenue. This time, we had to deal with the sharp increase in server costs. We discussed these options internally. Lay off employees. While layoffs are common across businesses, we felt it wasn't the right choice when our business is still growing. We have over a million customers to support and products to keep improving. Cutting jobs could affect both employees & customers. Instead, we want to reduce costs by focusing on R&D to make our products and infrastructure more efficient. Reduce other expenses. We have decided to cut our marketing spend and are looking at ways to improve efficiency across the business. Increase prices. Customers are already dealing with rising costs and geopolitical uncertainty. So we don't want to add to their burden. We want to first do what is in our control before doing this. Skip appraisal. This was a difficult decision, but we wanted to avoid layoffs and price increases. So we made this tough decision. As a private company, we have to take care of our customers and employees. Publicly listed companies also have shareholder expectations to consider. There is no one right decision in these situations. Ultimately, it comes down to what we choose to prioritise and how we balance the needs of our customers, employees and business for the long term.
The business outlook for software is uncertain and AI has raised costs dramatically with a) massive 4-fold increase in server prices which we need for data centers b) AI usage increasing rapidly, leading to much higher expenses, which we are trying to control. On top of that is the challenging geopolitical backdrop. We have cut down on our marketing budget. We have also told our employees that we cannot have our usual pay increase this year. I have apolgized for not being able to avoid this. We will work hard to avoid mass layoffs but the outlook for software jobs in general is grim. We have not been growing our employee count for 18 months now. Most of our employees understand the situation. I am thankful to them. We are in the middle of reinventing ourselves. The next 3-5 years will decide how our reinvention has worked. Please pray for us 🙏
47
54
12
561
74,351
Lol... since when @LinkedIn started using React? A bit surprised since they were one of the major adopters of @emberjs
19
I am surprised to see the preact 10 results in octanejs.dev/benchmarks ... I wasn't expecting it to beat every metric in that benchmark, but at the same time didn't expect these numbers. @preactjs folks thoughts on this?
1
218
🚨🗣 Egypt's Coach Hossam Hassan couldn't control himself after full-time: "I will say what's on my mind regardless of the consequence, this was clearly a rigged match and the whole world saw it" "And I want to say one more thing, if they want them [Argentina] to win so bad, why call everyone to come and participate?"
1,848
58,195
3,930
333,342
10,935,847
I think @cursor_ai frontend sourcemaps were public for short period, did anyone manage to extract source code? It had some interesting code. Lazy me didn't do it. I saw stylex, protobuf dot generation, code to sync ui spinners animation timeline etc..,
59
I think now more about fb way of having node_modules pushed in their monorepo.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.
50
Annamalai retweeted
This is literally insane guy had 5 BTC locked in a wallet for 9 years dumped his old college computer into Claude as a hail mary Claude found the wallet file, debugged btcrecover's password logic, decrypted the keys, converted to WIF, recovered the funds We are so unbelievably early
HOLY FUCKING SHIT OMG CLAUDE JUST CRACKED THIS SHIT, THANK YOU @AnthropicAI THANK YOU @DarioAmodei NAMING MY KID AFTER YOU 😍 blockchain.com/explorer/addr…
186
544
41
10,444
2,189,169
Annamalai retweeted
USERS care if code is messy. They care if the app is buggy. Or slow. Or if the UX is frustrating. Or if important features are missing or broken. These are downstream effects of messy, unmaintainable code.
Senior developers are currently having a massive existential crisis because Claude writes "messy code" A junior just used Claude to ship an entire feature in 2 hours. Meanwhile, the Senior is still spending 3 days reviewing code. When will y'all realize that literally nobody cares if the code is "messy"?
87
143
9
2,095
115,188
Annamalai retweeted
when software had a soul there was a moment around 2005 when using a Mac felt like touching something alive. the dock bounced. the genie effect swooped. exposé scattered your windows like cards on a table. none of it was strictly necessary. all of it felt like someone cared – not about metrics, but about the feeling of using a machine. software back then had texture. it had a philosophy. you could feel the person behind it. someone made a decision to make that icon beautiful, to animate that transition just so, to write that error message with a little warmth. apps had personalities. some were weird. some were over-designed in ways that would make a modern PM flinch. but they were alive. the web was the same. personal sites were genuinely personal. blogs felt like letters. forums had regulars. you knew who made what. the internet had neighborhoods, and each one felt different. nothing was optimized for scale. things were made by people who loved what they were making. somewhere along the way, we traded all of that for growth. A/B tests flattened the edges. design systems standardized the personality out. everything got faster, smoother, more consistent – and somehow less interesting. the quirks were removed because they didn't test well. the warmth got cut because it wasn't measurable. we optimized our way into a world of things that work perfectly and feel like nothing. now every app looks the same. every interface follows the same patterns. every product speaks in the same calm, frictionless voice, siloed in their own little islands. the humanity got rounded off. and then came AI agents. and the speed got inhuman. now you can generate an entire product in an afternoon. ship a feature before lunch. spin up ten variations before anyone's had their coffee. the gap from idea to code is basically zero. which sounds incredible. and it is. but there's a catch. when making things are too easy, the slop comes for free too. mediocre things don't look obviously bad – they look fine. they work. they ship. they pass review. and now there are infinite of them. the internet is filling up with software that functions but means nothing. interfaces that are correct but feel dead. products made by agents, reviewed by no one, shipped into the void. this is the thing that keeps me up at night. not that AI will replace people who care. but that it will drown them out. here's what I still believe: the best things are made by people who couldn't help themselves. someone who lost sleep over an icon. who rewrote the same line of copy twelve times. who added an animation nobody asked for because it made the thing feel right. that obsession – that's not inefficiency. that's the whole point. AI doesn't make that irrelevant. it actually makes it rarer and more valuable. taste is not a markdown skill. caring is not a parameter. the weird, specific, "soul" thing you put into something – that can't be programmed into existence. the path forward isn't to make more slop faster. it's to finally give people with real vision the tools to make the thing they always imagined but couldn't build alone. the designer who had the idea but couldn't code. the kid who saw something nobody else saw. the person who cared too much about something most people wouldn't notice. if we get this right, we don't get a faster factory. we get a renaissance. more strange, personal, opinionated software made by teams of people who care and mean it. that's still possible. but only if the people who care get the space and tools to actually express themselves – and don't just hand the wheel to the agent and walk away.
142
342
114
2,475
428,415
Annamalai retweeted
Dear recruiters, If you are looking for someone with : Java, Python, PHP; React, Angular, Next.js; PostgreSQL, Redis, MongoDB; AWS (S3, EC2, ECS, EKS); Unix system administration; Git & CI with TDD; Docker & Kubernetes you’re not hiring a Full Stack Developer. You’re hiring an entire IT department.
181
774
53
8,851
438,340
Annamalai retweeted
If our business would be the first to be competed away by vibe coded apps, why are we seeing such rapid customer growth (exceeding 50%) right now? And why don't we see vibe coded email or spreadsheet or accounting app or messaging apps yet? My own personal R&D project is to enable huge gains in programmer productivity by _combining_ compiler technology with AI. Our goal is to enable a quantum leap in programmer productivity while being able to provide security, privacy and compliance guarantees. Without those guarantees, vibe coding just piles up tech debt faster and faster until the whole thing collapses. ‌ Of course, for people like Garry Tan, tech debt is to be pawned off on unsuspecting acquirers. Let me make a bet with Garry Tan: we will outshine and outlast his vibe coding companies!
Zoho’s business would be first to be competed away by people building their own custom software built by people using @Replit @emergentlabs and @Taskade Why pay $30/seat/month for over bundled SaaS when soon even nontech ops ppl can vibe-code a custom solution in a weekend?
350
572
155
6,748
900,383
And, is there anything that you don't like or miss in inertia.js ?
29
Hey @derrickreimer , I have been poking around Savvycal on how you use Elixir/Inertiajs and noticed you have prefix for ids along ulids. Wondering if you store prefix also in the db or is it handled by app (Ecto to output with prefix)?
1
28
200 Matches 2354 Runs 152 wickets 94 catches When history speaks of courage in Yellove, it will echo your name. 💛⚔️ Thank You, Ravindra Jadeja! 🫡 #WhistlePodu #ThalapathyForever
980
8,142
648
56,137
1,024,703
Annamalai retweeted
Animating layout isn't always bad. Global CSS variables are a performance killer. Hardware accelerated blurs can crash sites. Surprised? We go into all this and more, in the first Web Animation Performance Tier List: motion.dev/blog/web-animatio…
9
110
23
1,162
305,510
I don't know how Remix 3 will work out for large scale apps only time will tell. But, it is a great fit for embeddable/widget apps!!! #remixjs Aside from that, the best part is I can test my logic without renderer 😘
53
Annamalai retweeted
Something I just told a founder: Stay as small as you can for as long as you can. People who come to visit your office should always be surprised that such an important company has so few employees.
266
847
141
11,156
729,278
A very little-known SEO wins:
27
218
11
7,172
785,169
Is anyone interested in a slim version of @inertiajs ? with backward compatiability, plugin based extension for certain things. This might help to reduce the bundle size to a major extend. Swap libs like axios, qs, progress etc., #inertiajs
53