Live data from Hacker News

Ask HN: What's your favorite programmer niche?

news.ycombinator.com

11–20 of 112 posts

Re: Ask HN: What's your favorite programmer niche?

#11
post #5

Tinkering with microcontrollers is probably the most satisfying, because it really challenges you to understand exactly what is going on at all times, right down to the electrical level. Developing for retro hardware can be fun too, for similar reasons.

>Tinkering with microcontrollers is probably the most satisfying Not so satisfying when seeing the pay-grade compared to other CS fields.

If your satisfaction comes from a paygrade, it’s probably a false positive

Re: Ask HN: What's your favorite programmer niche?

#15
post #5

Tinkering with microcontrollers is probably the most satisfying, because it really challenges you to understand exactly what is going on at all times, right down to the electrical level. Developing for retro hardware can be fun too, for similar reasons.

I was recently able to get into microcontrollers for the first time on a work project (paid to learn something interesting!), and definitely agree. Getting to the pulsewidth-level of different protocols and learning whole new ways to debug has been really fun.

Re: Ask HN: What's your favorite programmer niche?

#16
1) Cryptography done right - instead of blindly reading & using algorithms, figure out how people got there. Requires some math background, progress is very slow, but the reward is many "ahaaa!" moments.

2) Trying/inspecting all sorts of Lisps out there. There are so many crazy ideas tried and implemented over the last 40-50 years that IMHO, any new modern language feature probably already exists in some form in some Lisp compiler or interpreter.

Re: Ask HN: What's your favorite programmer niche?

#19
Since last year I've been using Pixi.js (https://pixijs.com/) to create an app that puts video meetings into a 2d virtual space (https://flat.social). While learning how to build it, I got really (possibly a bit more than necessary) into optimising graphics performance to make sure it runs smoothly even for users who access it on potato laptops.

This includes pretty much every aspect of the rendering process - how often are elements updated, textures, masking, interpolation, fonts and making sure that nothing renders more often than it should. It's a challenging but pleasant process as the result of experimentation is usually easy to measure (FPS + memory usage).

PS. If you're into it as well - try Safari's web inspector for measuring performance and investigating which frames were dropped. I found it much easier to use for debugging than Chrome.

Post reply on HN