Going to the example used thousands of times, maybe the horse drivers thought the same way, but guess what? now we have cars, race cars, super cars, flying cars. The engine kept changing, car markets kept evolving.
People kept adapting.
Adapting is the only way or the Penguin way :P
Lets take HN for example, tons of blogs and articles recommended, but how do you keep track of all. ZenRead is simple way to track what to read and how much time you have it will take. For all the busy tech folks, it useful. As far as I know its useful for me.
It does make sense to shift focus on Architecture, but you also need people who are able accept that design. It takes a lot of people to agree on something in an enterprise context.
I really thought that vibecoded tools will be next gen of tools to be used in corporate industry/enterprise, but they just dont want it anywhere near. The demos are cool but that's far as it goes.
I did read that maintenance becomes a hurdle.
So C, C++, and Rust programmers will be in demand, and other languages will shrink?
Does this also relate to rising DRAM costs, which will make memory-efficient code more usable as we head into an unseen future?
The costs of hardware will take a long time to percolate up to software architecture, if they ever do.
Until current computers cycle out, people will largely keep their 1-3 year old machine with sane amounts of memory. If we start seeing large numbers of machines in the wild with 4GB of memory, then maybe software will adapt. But that won't be for several years yet.
It definitely doesn't relate, the time horizon is wrong. The software needs much longer to change, and that change needs much longer to appear in the job market. Compared to the timeframe in the article DRAM prices have only just spiked up now.
Projecting into the future, hardware expenses have always been dwarfed by salaries. I don't expect that will change enough for it to be noticeable.
It's essentially a book progress tracker. There are many apps that allow you to add the books which you are reading currently, but not at what pace.
It's simple, no complicated stuff, no AI shenanigans.
Created as I was overwhelmed by the number of books I want to read and thought it would be helpful to plan ahead.
You add a book name, number of pages and how many pages you want to read in a day.
It calculates and gives you the number of days and on which date you will finish.
It's also flexible to increase the number of pages so that it can recalculate.
It's a PWA for now. Still working on notifications and stuff.
Impressed? The average employee is more worried about his job security than the latest model release. The execs in their yachts only see profit bar charts that their model spits out.
Seems like a candid idea. Will the companies actually use this product as opposed to other product which they might be using. What stands out apart from AI?
It's just Next.js and just a basic implementation. There is no backend, and I am planning to take it further. It needs an LLM-based response mechanism.
I do see some potential for idea validation when paired with AI and a bunch of other tools. But for now it's more of a hobby; hence, I was asking around to see if people are interested before I invest more time into it.
reply