I see the sceptical comments, but no one says this "vibe-coded" projects/apps/tools will be ready for your customers. It basically scratches the itch for the given users/company/whatever. Also, it doesn't have to be fast, stable or handle 1_000_000 concurrent users. You don't have to worry about that.
Not everything has to be a SaaS, but I don't think all SaaS apps can be vibe-coded to a weekend project.
If it is solving my issues and problems, why do preaching about the merits of a proper product or paying. I'll pay for what I see value in, and vibe-code where I don't see the benefit of paying.
Maybe I miserably fail and get back to paying to product. It's all good, I take that responsibility while I start my vibe-coding session.
It's like they all vibe-coded all the new 26.XX OSs across devices.
I tend to ignore these kinds of things, but sometimes applications are unresponsive, lose focus, and iOS apps don't show the keyboard, etc. so I cannot take it anymore.
I wanted to open a file from the Files app on iPad, a PDF. It opened the Preview app, but it couldn't allow me to scroll through the file. I tried to close it, but, back button goes to the Preview app, not to the Files. Then closed the app, and from the Files, but again it kept opening this separate app, instead of the in-app PDF viewer, and I guess I have never seen a malfunctioning state or application flows in default iOS apps ever.
The new reminders app is a joke. It has weird things that randomly jump from date selection to time selection, and sometimes select random dates.
It's like, they did, `claude new-reminder-app.md --dangerously-skip-permissions`, and "is it working? working! release it!"
I know (hope) it's not the case, but, since the last few weeks, it feels it's like that.
- Eliminated complex caching workarounds and data pipeline overhead
- Simplified architecture from distributed system to straightforward application
We, as developers/engineers (put whatever title you want), tend to make things complex for no reason sometimes. Not all systems have to follow state-of-the-art best practices. Many times, secure, stable, durable systems outperform these fancy techs and inventions.
Don't get me wrong, I love to use all of these technologies and fancy stuff, but sometimes that old, boring, monolithic API running on an EC2 solves 98% of your business problems, so no need to introduce ECS, K8S, Serverless, or whatever.
Anyway, I guess I'm getting old, or I understand the value of a resilient system, and I'm trying to find peace xD.
Makinas | Fullstack Engineers | Full-Time | Berlin | ONSITE
At Makinas, we build a platform for deploying, optimizing, and orchestrating ML models on edge devices. We want to help the ML community worldwide to move faster from the research into the production phase so that engineers can focus on what they do best: create amazing apps and devices.
We're looking for Fullstack Engineers to help us build our platform, tools, and SDKs with Next.js, Prisma, Typescript, and Python.