One stop one question Daniel Tan

Wadge's law is where before every meeting there's a smaller meeting where important decisions are made. Newbies to office politics might miss this and get ignored when they try to push for a new idea during company or team wide meetings.

This is just a quick, unstructured update on why I stopped releasing podcasts for the last two weeks, save for one pre-recorded one.

Recently there’s interest on finite state machines on the backend and frontend. As someone who has used it extensively in the games industry, I would say while it’s a good step from what goes on in development right now, it takes some discipline to get it working, and I definitely prefer data-oriented functional programming over it, but I’ll cover data oriented functional programming some other time.

There’s a lot of other laws in programming out there, like Moore’s law and what not, but I find the one’s on programmer culture being especially interesting because programming is like half way between engineering and liberal arts, and there’s no hard and fast rule to it, so there’s always something related to psychology or what not.

This usually comes up when you’re doing an interview or preparing for one, and you’ve got all the basics patted down until you get questions on specific frameworks that you might or might not be familiar with. This happens to everyone, and no matter how old you are, as a programmer you’re constantly expected to be learning new things. New concepts, new frameworks, new anything under the sun.

There’s only so much time we have but so much to learn, so it’s best if we get some gauge on how far we should learn something.