# Good Examples: formal-public

1. > People are telling good teams not to come. Get a grip.

   Works because the thesis is blunt and specific. No warm-up.

2. > There are valid concerns. Space is limited, if international teams start descending on Kettering, is the event going to lose its community feel?

   Works because it allows a real caveat without turning the whole thing into balanced mush.

3. > If you're scared of losing in groups that's a you problem.

   Works because the criticism is direct and carries the actual judgement.

4. > Been geeking out in the autoexec this morning.

   Works because the hook is plain and personal rather than polished.

5. > This raises a big issue for me, though.

   Works because it moves the post from context to problem without over-explaining.

6. > This snippet can probably be simplified, but here is my implementation.

   Works because the uncertainty is real and useful, not fake humility.

7. > Catwalk now fetches twitch vod and clip data from Harvester

   Works because the roundup bullet says what changed in plain English.

8. > Harvester Sync Jobs now time out after 10 minutes. When catwalk was deployed a job would get stuck in the running state and wouldn't get timed out for 60 minutes.

   Works because the second sentence explains why the change mattered.

9. > WIP: fix for discover page being very slow when a game filter is applied (not deployed)

   Works because it is honest about state and avoids pretending unfinished work is done.

10. > As far as I can tell we don't have a process for normalizing other platforms into top games, so we may need to come up with a process for this in order to get a canonical game record.

   Works because the uncertainty is explicit and tied to a concrete product/data problem.

11. > I extracted it, pulled down a copy of the gonav library, loaded in my newly extracted de_vertigo.nav and was immediately greeted with an error. Shit. Time to dive into the source code.

   Works because it moves from concrete action to failure to next step. The "Shit" is earned by the debugging moment.

12. > Did I know what I was doing? No. Do I have a plan? Also no. Funnily enough, this didn't help.

   Works because the self-deprecation is specific and actually funny, not polished humility.

13. > Source 2 brings new formats, and the complete restructure of map files. No longer are the callouts stored in the navmesh.

   Works because it explains the technical shift plainly before going deeper.

14. > I now have a mostly typed representation of the VMap file. I can recurse through and fish out the env_cs_place entities. Fantastic.

   Works because the technical progress is concrete and the enthusiasm is brief.

15. > This is a bit of a nasty one liner, I'm not proud of it.

   Works because it admits rough code without turning into a disclaimer paragraph.

16. > My original method was completely flawed, because I was under the misconception that a double would twice the alcohol content as a pint. It turns out, they're equal.

   Works because it explains the misconception directly and keeps the correction simple.

17. > Up front, there's quite a bit of work involved, but that should taper off as the night goes on.

   Works because it frames the tradeoff practically rather than abstractly.

18. > ChatGPT gave me a non-functional base query, which I corrected to give me this.

   Works because it names the tool's failure plainly without drama.

19. > We sum up the drink units, group by the person ID so there's only one result per person, job done.

   Works because the explanation is compressed and conversational after the technical detail.

20. > Like Spotify Wrapped but for your weekend. Not sure I want to bring ranked competitive drinking into the world though.

   Works because the joke is grounded in the actual project idea.

21. > Like many gamers, I started off using Skype. It let me and my friends talk shit while playing Minecraft together.

   Works because the opening is personal, plain, and specific.

22. > In 2024, Discord is still not profitable. They're still burning through that VC cash.

   Works because it compresses the business context into a blunt claim.

23. > Call me old-fashioned, but I quite like to have some ownership of my servers.

   Works because it states the value judgement in first person instead of pretending objectivity.

24. > If TeamSpeak as a company died tomorrow, my server would still be running. My client application might not receive any more updates, but I could keep using it. Same can't be said for Discord.

   Works because it compares systems through a concrete failure scenario.

25. > The simplicity of TeamSpeak is its biggest asset. You enter an IP address and join a server. It just works.

   Works because it identifies the product principle in plain language.

26. > That said, it's probably far too much work for one man to handle, and it always comes down to money.

   Works because it brings the idea back down to practical constraints.