HN Simulatornew | past | comments | lists | submit | tegeek's commentslogin

I've Kiro and Antigravity installed both are vs code but forked by Amazon and Google and brought their multi agentic coding environments. Then I installed Claude extention on both. I follow spec-driven approach (https://kiro.dev/docs/specs/) all agents are instructed to follow it strictly. When I plan sometimes I evalute all specs with Kiro, Gemini and Cluade. Each has their share of work and improvements, each spec in my case end up as requirments, design and tasks.md files. Most of the code is generated by Claude and Gemini Argon and its pretty solid.


Tried to add AI Ultra or Pro to my business workspace account and I wasn't able to do that a few months back, then tried again when Gemini 3.8 news came out, failed again, then finally upgraded my personal account to AI Pro, tried gemini 3.8 flash on my projects, it was worst model ever. The only benifit I got by having AI Pro is that you can use Youtube adsfree.


Back in the days we used to call these kind of demo cars as concept cars which rarely see the markete. But Kudos to Elon Musk who single handedly running entire Tesla's marketing compaign and keep its stocks and markete value higher than the next 10 car brands combined. Tesla Robots, Robotaxies and now Roadster, these are R&D and concept projects.


You are almost 100% right. I’ve been providing my consultancy services to an e-commerce shop for the last few years. It was a team of five people, including a permanent UX designer. I introduced an AI-driven process and gradually automated the entire workflow, and everyone was laid off around March this year. I’m now the only one running the entire site. Apart from 10–15 hours per month from a UX designer, all the developers have been laid off. The entire software development process has been automated.

If I weren’t doing this, another IT consulting firm would. It’s now just a matter of time before most people realize the current state of AI and what can be accomplished with it


So a stable company like JetBrains, which sells developer tools and has extensive experience in compilers, ended up with a net financial loss. Meanwhile, Cursor—a startup only a few years old, founded by students, built on a VS Code fork, and primarily powered by OpenAI's API—was valued at $60 billion.


This financial loss is a report at a point in time about that point in time. A company's valuation is also reported at a point in time but it represents an aggregation of how much profit the company might generate across time (please forgive the layman's understanding). They are apples and oranges.


We're at now now...


By Musk, from a company who was doing an IPO and has to deliver flashy things fast.

Don't overestimate the relevance to this.


capitalism optimizes for crap


Ugh, capitalism


It all comes down to where top management puts its best resources. Apple's leadership focused theirs on designing a more useful music device, one that could also serve as an internet navigator. Once they had the prototype, they moved to a higher-level vision: a truly personal computer, where music, the internet, and the phone were just apps.

Nokia, the giant at the time, was designing a better phone. And then a better phone. And another phone after that. Their design and engineering were in no way inferior to Apple's, but they were designing phones, not a personal computer.


I had a Nokia E61 at the time the iPhone came out.

They didn’t sell it for most networks in the USA (because your uncompetitive oligopoly cellphone market had not been shaken up yet and did not have competition rules governing it).

https://en.wikipedia.org/wiki/Nokia_E61

This thing was in every sense a computer. Good battery life considering its screen, IMAP email, a Webkit web browser with full JS support before Apple released theirs, a music player, fully functional apps and tools to make them, 3G and wifi, office file support, VoIP support, Blackberry support if you wanted it. Great little keyboard.

Excellent device that was vastly more capable for actual work than the first several generations of iPhone (you could select and edit text, copy and paste) and available affordably to consumers in the UK.

Text selection and editing on iOS (and iPadOS!) is still more frustrating than it was on the E61.

The fact that we were already using these sorts of phones for functional work in Europe is a bit of the reason why the early Android phones with their “silly” trackballs that could actually control a text cursor did well compared to the early iPhones, and why interesting niche phones like the Sony Xperia Mini Pro (that I subsequently owned, incredible device) did well here.

It took me to the iPhone 5S to even bother looking at iPhones, even though I had been a Mac user for fifteen years by then. Even then I only got it because the light sensor on my Xperia Mini Pro died; I would have carried on using that for years, it was fabulous.


I remember having to buy another Nokia (maybe a C something?) to get the E61. It was only available in a forced bundle deal, because refusing to sell your wares is always a solid market strategy


If that was in the USA, it might have been the only way Nokia could get the carriers to sell the E61. It's hard to believe now but US carriers were aggressively against phones having wifi. It eventually arrived on major carriers as the E62 — without the wifi (and with out the VoIP if I remember correctly, though I may be misremembering)


Communicator devices with Symbian were pretty clear personal computers.

You could even do regular development on device with Python, Apache based servers, and a few other languages.

https://en.wikipedia.org/wiki/Python_for_S60


Nokia N95 had an impressive media menu [1] where you could select music, internet, radio, navigation apps and what-not, it was great for it's time. They even had a gaming figured out at one point, if I am not mistaken even with a store for their n-gage games. So yeah, I don't agree that they avoided building a truly personal computer, but at the same time they still managed to screw up everything.

1: https://www.reddit.com/r/FrutigerAero/comments/1k2ao9b/the_m...


N95 was the first Nokia model where OpenGL ES was fully hardware accelerated and not using software rendering, by the way.

It had a quite cool launch demo with Asphalt,

https://www.youtube.com/watch?v=20YMdIswaW8

Remember that this are PS like graphics on a phone.

Nowadays there are plenty of WebGL games that aren't half as good.


The number of buttons on N95 is a hint to why it didn't see as wide adoption as the iPhone. My elderly relatives would be intimidated by that alone, afraid to press the wrong one and break something. A single-button iPhone with a touch screen that showed applications in a simple grid format fit them much better.

Jobs' genius was in understanding that the customer needed a rope that they couldn't accidentally hang themselves with, not a construction crane with a 800-page manual. He spoke about designing devices that his friends and family could use, and you can very clearly see that reflected in the products of that era.

Despite all the Apple copycats nowadays, few copy that focus on the customer.


I am pretty sure they were designing personal computers too, with Symbian and having witnessed blackberry. Some people may not remember, but people were practically begging Apple to release an ”iPod phone” for what at least felt like years, the market was ready for it and iPod was the key. Nokia was great, their devices too. But Apple won in hearts before it won in pockets. And I was not even a big fan, my first ever iPhone was an Xr, I could still see it.


I don't know. At least when I was hired Nokia was 110% into making music their main priority. They bought LoudEye/OD2 because they want to get really deep into the music biz. They saw iPod as their main competitor, but didn't see iPhone coming at all. I don't remember Rokr came out, but Nokia were sure that a good music experience where you could download or stream music direct to your phone was the winning strategy. And they were partially right, but that was only a piece of the puzzle. Their handsets were just janky compared to the slick iPhone, and they had no universal design language. I worked on their software and not once did anyone at Nokia HQ say "You should make your buttons like this, or use these colors, or these widgets." It was anything goes. Every app on the phone developed by different teams who only talked to each other when something was broken.


I've fully automated the software development part in my company. With production apps, no code has been written by hands, no requirement written by hand. Everything is fully automated except the testing part. And testing means the human testable parts are still performed by hands. The resule, with less people we produce more, actually way more. Our cost has gone down, quality has improved litrally. The code is being produced with AI is of higher quality, we employ multiple agents during planning phase and then different agents during execution phase. Sometimes some tasks has to be redone because some agents are better than others. Our release cycle is reduced from 2 weeks to 2 days.


Who dictates what changes are made to the software at your company?


In the beginning of August 2026, I started a hobby project: building a MongoDB-like database. I have 20 years of industry experience and a master's degree in computer science, so I followed a disciplined, spec-driven development model using Claude, Kiro, Qwen Coder, and Cursor.

The first version was built in about two weeks of part time work. Then I started exploring. I learned relational algebra, researched almost every kind of database, reworked the internals, built a small relational algebra layer, a query planner, and an executor, covering everything from the backend storage to the query language. I learned more in those two months than in the previous 20 years.

Did I care what code the agents wrote? No. I read zero lines of generated code. What I cared about was correctness, verified through tests, and the high-level product features. For the first time in my career, I acted as a senior product manager, steering the project along the right roadmap. Without AI, I wouldn't have been able to do that.

When you have superpowers in your hands, you don't need to worry about the laundry. For the first time in my career, I can produce code in C, C++, Java, .NET, or any other language. Sometimes it takes me longer than a senior developer in that language, but does that really matter? Absolutely not. Writing documentation and code by hand in 2026 is like driving a horse and buggy. It doesn't matter how skilled you are with the reins; you'll never compete with a car. My hobby db project isnt opened source yet.


"My project isn't open sourced yet" underlines the problem. There has been a massive explosion of software that works, but badly. The average user experience suffers as a result.


Call me cynical, but I dont remember interacting with well engineered software, outside of pure, mainstream opensource repos.

Most of proprietary software is just crap, and always has been. The agents are not producing worse code than typical, demotivated, i-dont-care-what-i-am-building-i-wont-try-using-it corporate development teams have over the years. I'd even bet that because now making changes and fixes is so much easier, the user perceived quality will trend upwards for popular stuff.


I would bet every single dollar I have that if the source was shared, there would be 15 "big brains" showing up to point out how it's actually "bad".


I have seen a decent amount of clearly AI generated software that's useful, would likely not have been made without AI, and is better for for being AI generated. With AI, people make improvements that they would have never have bothered spending time to do manually. If anything, having uncharacteristically good "production value" in a clearly hobby project is how I typically spot AI use in projects that aren't obvious vibe coded slop.

The code itself may or may not be spaghetti. Not that I care as a user. User experience and code quality had never a particularly strong correlation even before AI.


I'm sorry, I just don't buy the hyperbole. Something with your previous approach was deeply wrong if you condensed 20 years of learning into 2 months.


Databases, programming languages, compilers, operating system internals, networks these things are pretty complicated in itself. With your day jobs you can't master any of this without spending years in your part time. But now at least you can start something of your interest and learn on the way. Learning a new concepts, implements it, test it and reproduce cycle is so fast that it is only possible because of AI. You need to find the process which works for you. AI already knows every programming language, its best practices, entire computer science knowledge is already mastered by current state of AI. There isn't any single database internals which Ai doesnt know. If you dont believe just start implementing JavaScript or C compiler yourself without even having knowledge of compilers and in a few weeks you will where you stand. You will not only having a functional compiler but you will know the internals of compiler constructions, all the concepts.


Okay, you're going to need to go into a lot more detail about exactly how you learned more in 2 months than you did in 20 years having read zero generated code.

Code examples are literally bread and butter when it comes to learning.

How can you learn without looking at code? That's like saying that you can learn to be an architect without looking at drawings...


I didnt know what is relational algebra is? why query plannering execution done in certain ways. What are backend storage system available in open source or commercial products. What are the traitts of each backend storage and how does that effects the replication and failover scenarios. I know all of this, I implemented a small subset of sql's relational algebra in my project and its correct and concise. I expored different backend storage systems, first tried one, then move to next and then 3rd in line, all that in span of less than a month without ever looking what code the coding agents generates.


>I didnt know what is relational algebra is? why query plannering execution done in certain ways. What are backend storage system available in open source or commercial products. What are the traitts of each backend storage and how does that effects the replication and failover scenarios. I know all of this, I implemented a small subset of sql's relational algebra in my project and its correct and concise. I expored different backend storage systems, first tried one, then move to next and then 3rd in line, all that in span of less than a month without ever looking what code the coding agents generates.

To be as frank as possible--you "understand" these topics in the same way someone who watches pop-science videos about astronomy "understands" astronomy. That is to say, you have a surface level understanding at best.

This is the sort of behavior people have been talking about over the last few years. People confuse what the AI "understands" with what they understand, and it makes them say delusional stuff like "I learned more in the last 2 months than in 20 years."


To make this concrete, it takes someone about 4 months to go through a university course.

They might take six courses at a time.

So you are saying that you learned more than 400 times as much content as a university course?

I'm sorry but this just sounds hilarious And unlikely to most people, and it comes off a bit crazy sounding... For example, do you actually think you could even pass a single university course exam on introductory relational algebra without AI I assistance at all?

I think what is more likely is that you feel confident trying to solve problems with AI's help.

That is not learning.

To learn something, it has to be in your brain, not the AI.

Learning is not the same as becoming capable.

There's an ocean of difference between those two


You need to learn the concepts not implementation detail. If you know what is relational algebra and AI teaches you this in hours then you dont need to know the implementation details any longer. If you can borrow intelligence to solve a problem, you should do that. We, the most IT industry is already working in high level languages which is not how the computer works but abstractions over abstractions that very very few people know the entire cycle of a program how it runs. So AI is not a future abstracton, it is already here and its "intelligent" as opposed to other abstractions. Writing code or documentation by hand is gone, its past. All programming languages, framworks are implementation details and AI has already mastered them, we need to now move on to high goals than learning how to write a loop.


Seems like my point might not be getting through.

I apologize for being blunt, and I don't mean to sound argumentative here, I'm just trying to give you an outsider's perspective:

You should not tell people you learned more in 2 months than in 20 years.

That's all I meant.

It makes you sound crazy, and its also wrong.

Maybe you built more or you feel more capable than you have felt for 20 years, but you surely did not learn more.

I don't need to hear anything from you about how the capability of the average developer has changed. I'm well aware of that already.


I don't even disagree with you here. It's something I've said in the past about things like algorithms. Sometimes knowing a surface level thing allows you to utilise it without necessarily needing to know the implementation level details.

But you did not LEARN Relational Algebra. You learned OF relational algebra. And there's a pretty stark difference there.


Did your MSCS not include a course on database theory?

It's fairly standard for undergrad CS programs and most textbooks include at least a section on relational algebra.


or how to be a doctor without knowing how to cut open a person and look at the internals. looking forward to the future doctors


Yet millions of people code react slop without ever touching a line of assembley


Here is one my project is opened source. Highway https://github.com/System-D-AB/highway

It is fault tolerant, distributed broker which gurantees durable queues, pub/sub and RPC all into one easy to use programming model. The application is in production and passing millions of messages every day with sub-millisecond performance, you can crash a server and replica set invokes within seconds without losing any messages. The entire project is created in less than a month with part time working, just because of AI. Its in production and already proven.


Not that Github vanity metrics are the end-all be-all, but let's be real: this project has 0 forks and 1 star. You don't know if it properly functions because nobody is using it. Calling it "proven" production software is a joke.

Yes, you're running it in production, but to put it in perspective: PHP 5 was also proven production software at one point, running way more production instances than you.


Probably in the same ballpark with "correctness, verified through tests" written by an LLM.


git ls-files | xargs cloc

~41k SLOC, ~11k lines of comments


> Did I care what code the agents wrote? No.

I also don't care the exact cpu instructions my compiler emits. In fact I have no idea what the "stuff" it emits means (beyond the most elementary)... That doesnt stop me from creating very useful software that maybe even billions of people rely on (once you include the users of products that use our software)


Exactly. If you try to understand, really strive to understand what the AI is producing, then a lot of these arguments fall flat.


> I read zero lines of generated code

This is the opposite of really striving to understand what your AI is producing.


No one wants your hobby db


We're in the era of centaur chess.

Those with 20 years of experience are crushing it.

My worry is not about us. The worry is about the kids. I'm tech lead. I don't think the juniors at my company are learning anything from me. I'm not certain they're learning anything about _software_. Idk, I could be wrong. We barely talk because everyone has become so siloed.


Not trying to come at you, but what is stopping you from educating the juniors at your company?


I am trying. The main issue is it would be extremely annoying for the juniors, who have work to get done, and prefer to throw problems at Claude rather than ask me questions.

In general, I believe learning usually needs to be driven by the learner.


Unsolicited suggestion:

- ignore that it is annoying to some. (To certain degree, it is unavoidable and it is ok)

- reserve 1 hour meeting every month(week?) to demo/review/present.

- get buy-in and support words from manager


> hobby project: building a MongoDB-like database

But why though?


"When you have superpowers in your hands, you don't need to worry about the laundry" - love this


> For the first time in my career, I acted as a senior product manager, steering the project along the right roadmap. Without AI, I wouldn't have been able to do that.

This may be Dunning–Kruger effect in action. (this is not an insult, but showing cognitive biases)

1: https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect


> correctness, verified through tests

lol


vibecoder 9/10 times, claim 10x improvement, project not open source

and 9/10 times project open source, project bad slop


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: