Weekdays are for my fulltime job, lots of activities to keep me focused throughout the week. When the weekend comes, I get to switch gears and focus on something different.
It’s my time to work on my side hustle. Currently I’m building my own SaaS product to automate marketing activities and plan to publicly launch soon.
Along the way, I learn new things to keep up with the changes in tech and the industry. These activities help me grow over time as an engineer ๐ช
Vibe coders without fundamentals do fine with basic and simple apps. But things go wrong when they are trying to solve a bigger problem.
The first issue is complexity. Large apps have many parts that work together.
Back when I built a global search feature for a B2B marketplace, users needed to search products, stores, documentation, etc at once. Before I wrote any code, I had to learn how each part of the system worked, how the data is synced to Elasticsearch cluster, and how we can rank the results.
Without understanding the system, you’re lost. What should you change? How do you make sure the AI doesn’t break things that already work? You can’t just ask AI and hope for the best.
The second issue is documentation. After you understand how things work, you need to write clear docs so your team knows what to change and future engineers can maintain the code. This is where vibe coders struggle. Without the fundamentals, they can’t explain how things work.
What happens when the original engineer leaves? Without proper documentation or deep understanding of the system, it’s hard to maintain it. This isn’t just a tech issue, it also hurts the business long-term.
Vibe coding works for some things, but building large systems needs solid foundations that AI can’t give you alone.
Don’t take this negatively. I do vibe coding too. Most of my code now is generated by AI also. My advice is don’t feel satisfied after you generate an app with AI. Keep learning the fundamentals so you can grow over time and be ready to handle larger problems.
There is a lot of discussion in Indonesia lately about vibe coding vs no vibe coding.
I think it depends on your objective and what stage you’re at.
If you’re learning to code. Starting from scratch is better because you feel the progress and understand each part of the code you write. This was my approach back in the days when I learned coding.
When you jump straight into vibe coding, a lot of details get missed. You end up with only high-level understanding without the fundamentals. When bugs occur or you need to update simple things, you’ll likely get confused because the lack of fundamentals.
If you’re building a simple app, vibe coding works perfectly fine. But for large-scale, complex systems it’s not the right fit.
Build the fundamentals first, then use tools to move faster.
I realized that AI handles most of my coding tasks now ๐
It makes things easier, but I started to wonder if my problem-solving skills are not getting enough exercise.
To keep my mind sharp, lately I practicing on LeetCode again, and unlocked new productivity tips. When stuck ask Comet to get the answer directly, itโs much productive than just copying code to ChatGPT, just ensure you try to solve the problem yourself first before ask.
I recommend you to keep the mind sharp too. Practicing this way helps you stay ready even AI changes the way we work.
The AI automation tools just got more competitive with OpenAI AgentKit ๐ค
It’s basically a new toolkit for building agents. There’s a visual builder, connectors, and tools to help automate tasks like n8n.
I think OpenAI is moving toward a whole new market segment with this, especially with their pricing. Meanwhile, n8n is still a top choice or makers and devs who love open source and cheap option.
I’ve been using the Comet browser from Perplexity for a few days, and it has changed my browsing experience. This browser makes me rarely search manually on Google. The workflow just feels more efficient.
The YouTube summarization feature is also incredible. I can paste any video link and get the key takeaways directly, very productive for learning new things.
Comet browser even helped me with GitHub, I asked it to draft a pull request description and the output was actually good, although it’s not designed specific for coding related task.
It’s impressive how well it adapts to different types of tasks ๐
You must be logged in to post a comment.