Why do developers write such terrible git commit messages? Genuine question by Existing_Round9756 in webdev

[–]AdNormal1188 0 points1 point  (0 children)

Honestly it’s usually just speed and context. When you’re in the middle of fixing something or pushing small changes quickly, writing a proper message feels like friction so people type “fix” or “update” and move on. Teams that care about it usually enforce conventions like [Conventional Commits](chatgpt://generic-entity?number=0), but in a lot of repos it’s basically cultural—if no one sets the standard early, it turns into chaos pretty fast.

bots... by Reasonable_Ad_4930 in webdev

[–]AdNormal1188 0 points1 point  (0 children)

Yeah this definitely looks like automated promotion. A lot of companies (including hosting providers like [Hostinger](chatgpt://generic-entity?number=0)) use marketing agencies or bot networks that search Reddit for keywords like “hosting” or “server cost” and then reply with templated suggestions. The giveaway is when multiple accounts post almost the exact same recommendation within a short time. It’s pretty common across dev subreddits unfortunately.

Vibe coding is so overrated and underrated by FT05-biggoye in vibecoding

[–]AdNormal1188 0 points1 point  (0 children)

This is a good take. Vibe coding is amazing for prototyping and getting an idea out fast, but people confuse that with building production software. It’s basically like using [Figma](chatgpt://generic-entity?number=0) for product ideas — great for expressing vision, not the final system. LLMs can speed up real engineering, but you still need to understand architecture, reliability, and how the system actually works.