标签：#hack

As a software dev, I really enjoy having live coding videos playing in the background while I work. But it's surprisingly difficult to find hour+ long videos of coding without commentary on Youtube. What I really wanted was an infinite coding video, so I built one. Pick your IDE/monitor/ambience of choice, hit the Screensaver button, put it on a second monitor or TV, and enjoy infinite coding ASMR.

I judged three hackathons over about ten days this July: MLH x DigitalOcean "AI for Social Good" on July 11, the Sports World Cup Hackathon in San Francisco on July 17, and Aethera Hacks, an online event on Devpost, across July 19 to 21. I came in from the sports technology side, building athlete monetization tools, so I was usually the judge asking who pays for this rather than the judge asking what is your bundle size. That turned out to be a useful seat, because the questions that decide scores are mostly not technical ones. Here is the part builders rarely get told: a judge is scoring under a hard constraint. Some number of teams, a fixed window, and by the middle of the block the demos start blurring together. Judges are not evaluating your project against an ideal. They are ranking it against the six they just saw while trying to remember which one had the map. Everything below follows from that. The rubric is real, but it is not what separates teams Most events hand judges four or five categories with numbers next to them. Technical difficulty, originality, design, impact, something about use of a sponsor API. Those categories are real and I filled them in honestly. But they compress. Almost every team lands mid-range on most of them, and the spread that produces a winner comes from two or three things the rubric does not name directly. 1. Whether the demo ran This sounds too obvious to write down. It is the single largest score differentiator I saw. A working demo, live, on the judge's screen or the team's laptop, beats a more ambitious project shown as slides almost every time. Not because judges are impressed by working software as such, but because a live demo removes doubt, and doubt is what a judge is actually managing under time pressure. The practical version: cut scope until something end-to-end runs. One complete path through the product beats four half-built paths. If your architecture diagram has six boxes and two of them work, demo the two and de

Hi HN community, As a busy techie with kids and other family obligations and my recent health diagnosis, I wanted an efficient way to integrate workouts in my daily routine and my research indicated that HIIT/Tabata style routines fit that requirement much better than a dedicated long running/planned workout routine. I made a simple PWA to help me with that endeavor that I have found useful and hoping some of you may like it as well. No sign ups needed but you can sign in if you'd like to save c