There's always been the need to verify the code matches the business requirement, right? It used to be when you asked someone why they wrote the code the way they did, they'd tell you they thought it was the right way because X or Y. But with AI they can respond saying they actually don't know why they wrote it a certain way. That's just what ChatGPT or Claude told them to do. So, that's the nightmare part that people are experiencing.

Code reviews are important and software architecture skills are just as important now.

But I also love that freedom of staying home whenever I want to. IMO, more offices should operate more like this.

Eventually I came back to tech as a contractor/consultant and like it so much more. My passion for development and engineering is much higher now.

The next step is going to explore building a local LLM into the application itself to then skip over the entire Google part. I want to implement some question/answer features that I THINK could be solved with a local LLM integration. But for now it's just a quick app to help you find coffee.

iOS - https://apps.apple.com/us/app/nyc-coffee-map/id6755573635

Android - https://play.google.com/store/apps/details?id=com.parkasoftw...

1. There's a map feature where users can assign their location to a photo that was taken. I suppose this could qualify as 'physical address'.

2. Businesses often have their physical addresses as part of their profile.

React Native mobile app + React web app that shows all the coffee shops across New York City. The idea is that you can open it and the app instantly displays the closest coffee shop to you. It integrates with Google Maps reviews AI summaries for a lowdown on the coffee shop and vibe.

I would much rather have that junior take some hacks at building some features with AI along with my guidance than context switching over to AI just to walk it through doing a task which means having to explain the business and our business rules over and over again.

To me cutting out a junior developer adds more time for senior developers than making their work lighter.

VS Code on a Mac works great and with the ability to run SQL Server in Docker you can have the old stack right there on your Mac.

I've had fun with building the data loaded, website and mobile app via Claude Code from VS Code. However, I didn't find building the project as enjoyable as actual coding myself. The code is a mess and is definitely overengineered and hard to read. I have had to consistently fix bugs and calibrate my prompts so the machine could produced the features that I was trying to create.

Another thing I learned is to commit early and often. Then create PRs to check what code was updated as things got away from me quickly without me knowing or asking the machine to do the thing it did. A few times entire sections of code were removed that had nothing to do with the feature I was working on. Being able to go back to the previous working commit probably saved me hours.

Vibe coding an entire project was a good experience. There's a lot to learn and focus on the next time I go this route.

Take a look! https://mplscoffee.com

Try to stay up to date on anything you don't know, but suspect you probably should know to provide value in whatever it is you're doing. You could treat this to everything under the sun, but I try to apply this principal to current .Net topics that make me a valuable .Net consultant.

Comments URL: https://news.ycombinator.com/item?id=44006643

Points: 3

# Comments: 1

I've only built it for Minneapolis and Chicago for now.

https://mplscoffee.com