adithyassekhar

This might be controversial. Please disagree with me.

When these were social networks, I remember my friends and later myself too, changed our profiles to public, send requests to random strangers, messaged them to like our pictures. We were teenagers and we were competing on who's more famous by having a bigger number next to our friends list or likes. There was no influencer culture back then yet everyone was trying to be this new thing. There were rarely any influencer type features on these platforms.

So I won't blame facebook or Instagram for being what it is today, moving away from friends to social media stars. They saw what people were doing and only supported them. People did what people did.

What I've read is that even with all the meticulous planning, the author still needed to intervene. Not at the end but at the middle, unless it will continue building out something wrong and its even harder to fix once it's done. It'll cost even more tokens. It's a net negative.

You might say a junior might do the same thing, but I'm not worried about it, at least the junior learned something while doing that. They could do it better next time. They know the code and change it from the middle where it broke. It's a net positive.

Is this that dropbox moment again? Anyway on Windows I keep a separate work and personal profile and GitHub auth doesn't go between them.

That was it, ok now I feel stupid.

I wish I could read this but got this[0] guy on mobile with no close button, won't close when you click outside the modal.

0: https://i.postimg.cc/14h3Q9mD/Screenshot-20260219-001356-Chr...

Edit: Nvm, found it. Weird place to put it.

This is seriously impressive! Never knew after market os's were even a thing for watches with their proprietary drivers.

I like that peeking watch face switcher, companies like samsung even after all these years still takes way too long to apply a watch face.

This article makes me want to move to Europe. :)

This I do agree with. All I've seen is reducing headcounts and forcing people to take up other roles as well.

> The cost of building something just for yourself used to be weeks of learning a new stack. Now it's a conversation and some token spend.

I remember this being the opposite. Some used to do side projects to play with and learn a new stack. That's how we all ended up here don't you think?

It's not about adapting. I use AI a bit in my work, not fully agentic. I've seen what it does, I've seen what it's good at.

The problem begins people see this as a know everything magic orb and trust it blindly for everything. It's still a pattern matching model, it's not sentient. It should remain a tool rather than one you should be asking for decisions.

Also I've seen people waste massive amount of tokens to add two tabs to a line of code to fix indents. Said they don't want to click the damn line. Bro you just typed a larger prompt, sent the complete file, instead of two keystrokes. And guess what it took multiple attempts. It's like watching someone type google into google 3 times before typing what they want.

Not all software are simple crud from your standard consulting business which makes more money the quicker something is finished. Some software runs critical life threatening infra everywhere. We need people who have the skills to build these, and they're discouraged from the school level not to thanks to AI bros.

Thanks

Hi I am a non native english speaker as well. Please don't be discouraged. But you're not speaking with your own voice if I make sense.

Honestly I prefer to talk to humans who have flaws. Even if your english is bad try typing it yourself. Everyone here will support you. That's how I learned.

Even my team mates use chatgpt to rewrite their messages in teams, it feels so dishonest.

Not really no. It's pretty much the same pace as before. I wanted to point out Android is not playing catch up to iOS in anyway in features or quality, it's the opposite. Your comment asked why Google isn't catching up to Apple with AI's help. iOS meanwhile has been regressing since 18 and is a mess now on 26.

Not really when there's economic incentive and when you need to eat.

Android is a poor example here especially with how more and more features are moved from the OS to Play services. Google is shipping so many features without even an OS update that's how Android has always been. Even for their OS, Pixel feature drops happen every quarter. AOSP is only a base for others to build anyway, have you seen how fast samsung and others are pushing updates and uncountable number of features. It's not comparable to iOS at all.

Your reply has a 0% ai score yet the presence of that "reply to" text is concerning.

Intersting concept. I just can't get my mind off one of the blurbs from the page

>Code Storage is designed for modern workloads: Vibe Coding platforms generating 1m+ new repos a day, AI copilots writing thousands of commits per session, teams branching and merging in real time, and apps syncing code across devices.

This is sort of a rant, skip if you must

Those 1m+ repos all have code no human has ever seen or will see. I'm afraid of being a luddite. But I can't believe we're taking vibe coding seriously, especially with these enterprise SaaS startups aimed at it. Abstractions have always come up but this is knowledge handover, this is knowledge reduction or destruction.

What happens to all of humanities greatest inventions when the current generation of developers die out? Who's going to maintain the basement? Where things haven't been abstracted? Who's learning at that level, who's keeping the knowledge alive when everyone's being told you just need to vibe instead of thinking logically?

I know why the push, people who never wanted to be developers, people who never wanted to code got into this for a paycheck or something else, they're welcoming this with both hands. I've seen people slowly lose their abilities they tried so hard to make.

I'm being fricking dramatic here all because of that blurb.

There are now organic looking comments. Maybe it's just the way some people sound.

Nah then it won't show up in the known issues section. I hope.

There are still three players in smartphones realistically.

ARM makes their Mali line, which vendors like Mediatek license and puts straight on their chips.

Qualcomm makes their custom Adreno gpus. (Derived from Radeon Mobile). They won't sell it outside snapdragon.

Samsung again licensed Mali from ARM, but in their flagship exynos's they use AMD's gpus. They won't sell it outside exynos.

PowerVR makes gpus that are so outdated with features that Pixel 10 phones can't even run some benchmarks.

And then there's apple.

Hi do you have some examples or repos you'd be comfortable with sharing? This looks interesting.

The post is impressive but anyone else feel a bit icky about the comments here? Numbering out the advantages in lists? The phrasing, the exciting exclamation mark(!). This comment section feels like some kind of marketing exercise.

Which one would you recommend for regular users and power users?

Lesson learned. Yes you are right. I am indeed a junior, I made that comment when I was tired honestly with a rushed project. There's no delete button, otherwise I'd have deleted it when I cooled off. Thank you for giving me hope that good code is still being made.

A tangent, I keep hearing this good base, but I've never seen one, not in the real world.

No projects, unless it's only you working on it, only yourself as the client, and is so rigid in it's scope, it's frankly useless, will have this mythical base. Over time the needs change, there's no sticking to the plan. Often it's a change that requires rethinking a major part. What we loathe as tight coupling was just efficient code with the original requirements. Then it becomes a time/opportunity cost vs quality loss comparison. Time and opportunity always wins. Why?

Because we live in a world run by humans, who are messy and never sticks to the plan. Our real world systems (bureaucracy , government process, the list goes on) are never fully automated and always leaves gaps for humans to intervene. There's always a special case, an exception.

Perfectly architected code vs code that does the thing have no real world difference. Long term maintainability? Your code doesn't run in a vaccum, it depends on other things, it's output is depended on by other things. Change is real, entropy is real. Even you yourself, you perfect programmer who writes perfect code will succumb eventually and think back on all this with regret. Because you yourself had to choose between time/opportunity vs your ideals and you chose wrong.

Thanks for reading my blog-in-hn comment.

It's not just about elegance.

I'm going to give an example of a software with multiple processes.

Humans can imagine scenarios where a process can break. Claude can also do it, but only when the breakage happens from inside the process and if you specify it. It can not identify future issues from a separate process unless you specifically describe that external process, the fact that it could interact with our original process and the ways in which it can interact.

Identifying these are the skills of a developer, you could say you can document all these cases and let the agent do the coding. But here's the kicker, you only get to know these issues once you started coding them by hand. You go through the variables and function calls and suddenly remember a process elsewhere changes or depends on these values.

Unit tests could catch them in a decently architected system, but those tests needs to be defined by the one coding it. Also if the architect himself is using AI, because why not, it's doomed from the start.

Backend, regardless of language or framework are often set in stone. There's a well defined/most used way for everything. Especially since most apps when reduced is CRUD. Frontend by the nature of how frontend works, can be completely different from project to project if one wants to architect it efficiently.

I'm not taking OpenAI's side here but have you reviewed what claude did?

This won't beat manual research. But it won't matter.

Most people buy what the sales person is selling, they don't care.

The tech enthusiast minority watch and read reviews, compare specs.

The only realistic audience for this product is somewhere inbetween those two. Imagine that venn diagram. People who care enough to research but not enough to "research".

This is exactly why I come here. I just woke up and didn't feel like dealing with people today and made that comment. Now you got me thinking, I do like to be social. Just not the kind where the other person is actively trying to sell me something often by being dishonest.

I remember a sales person in a store actively trying to shame me for purchasing from a brand he didn't prefer. I gave him a lot of chances to get off of me, respectfully and firmly. Some really are like blood sucking leeches, they don't come off. He was probably paid to do that.