The 2% of cases when you need the commit log (or more importantly: someone else who inherits your code...) justifies writing good messages imho.
If you make a change to your codebase, normally you know what you want to achieve and why (otherwise... what are you even doing?). A commit message is just putting that in writing... that only takes a few seconds, often less than it takes to write the code.
So it's just a good habit to have. It forces you to think more about the changes you do & why, so it makes you a better software developer. Creating any new habit always takes some energy initially, but it's worth it.
Cool, but I wonder... is this really a feasible workflow?
The way I use LLMs is, I enter a very specific query, and then I check the output, meticulously reviewing both the visual output and the code before I proceed. Component by component, piece by piece.
Otherwise, if you just "let it rip", I find that errors compound, and what you get isn't reliable, isn't what you intended, increases technical debt, or is just straight up dangerous.
So how can you do this from a smartphone? Don't you need your editor, and a way to run your code to review it carefully, before you can provide further input to Claude Code? Basically, how can you iterate from a phone?
It definitely makes me lose interest and trust in software that is openly described as being "vibe-coded".
I'm with the vibe of wanting to move on to the point where LLMs are just yet another tool in the process of software engineering, and not the main focus.
I'm sure that would work out fine. Just like the GDPR regulation made the web so much better & more private, and the promise of the AI act is boosting innovation in Europe...
The GDPR regulation is great and arguably does make the web more private and better. At the very least, it's better than having no regulations.
I've even been able to successfully use it to remove something private about me from the internet. I don't think I would have even gotten a response had there been no legal precedent.
You can always argue about how some regulations are badly implemented or incomplete but I believe it would be very misguided to believe that no regulations are instead the better alternative.
Exactly. So many local first libs don't cover this that it makes me wonder if the applications I am typically working on are so fundamentally different from what the local-first devs are normally building?
Most apps have user data that needs to be (partially or fully) shielded from other users. Yet, most local-first libs neglect to explain how to implement this with their libraries, or sometimes it's an obscure page or footnote somewhere in their docs, as if this is just an afterthought...
It's definitely quite a hard engineering problem to solve, if you try to cover a wide range of use cases, and layer on top of that things like permissions/authorization and scalability
Radar-based device for measuring athlete sprint & agility tests.
A lot of professional sports clubs, S&C coaches, etc.. use timing gates for measuring sprints, but those are a pain to set up, only capture split times, and are expensive. I think radar (+ optional video overlay) provides a far superior solution.
Meh, pretty basic. Most SaaS businesses have something like this in place already.
Closing inbound leads is relatively easy, since they've already shown active interest... The challenge I'm struggling with is (cold) lead generation: finding leads (and how to contact them) that match well with the service you're offering.
There are a lot of dubious scraping tools and B2B lead databases, but I feel like it should now be relatively easy to build a reliable web crawler & lead generator ... Does anyone know state of the art open source tools or services for this?
We are close to a point where bulk ai lead gen slop is going to be cheaper than smart targeting. I’d predict basically a slightly new / improved / arms race type incrementalism over the next 18 months. It will probably pay to stay on the bleeding edge, but it will be work.
I'm not in sales, but I imagine the customer attention is a limited resource in this scenario. If you create a fast, cheap and reliable way to generate leads, you'll saturate the market very fast. It's not really an edge if everyone uses it.
Curious why open source? At the end of the day, lead gen is mostly about data curation. You’re either paying for access to curated feeds or spending time/money building your own pipeline.
If you make a change to your codebase, normally you know what you want to achieve and why (otherwise... what are you even doing?). A commit message is just putting that in writing... that only takes a few seconds, often less than it takes to write the code.
So it's just a good habit to have. It forces you to think more about the changes you do & why, so it makes you a better software developer. Creating any new habit always takes some energy initially, but it's worth it.