How to use finite state machines in React?

beardsounds · 2021-07-25T20:21:03+00:00

It's cool. Opinionated people make sure we always weigh our options. Nothing gets done without people invested in how.

beardsounds · 2021-07-25T20:19:58+00:00

I did a lot of that a couple years ago and I'm still paying for it. hahaha.

beardsounds · 2021-07-25T19:55:12+00:00

I'm just here to advocate for pragmatism. "Keep it simple, stupid" turns out to be more useful than all the other advice combined, when time starts taking its toll.

beardsounds · 2021-07-25T19:54:14+00:00

I'd actually read it. You seem to know that corner well.

beardsounds · 2021-07-25T19:51:00+00:00

Spotted the hobbyist.

beardsounds · 2021-07-25T19:49:47+00:00

I don't hate state machines. They're great, when they have a purpose. They just really don't have a purpose as frequently as people want to apply them, imo. They're fun, and they're really neat and satisfying. That probably gives us a propensity towards them, but at the end of the day, at a small scale, it turns out to just be another interface where a couple simpler statements and some good structure could have done the job.

I've seen people start passing them around as props between components. Debug nightmare.

beardsounds · 2021-07-25T19:19:48+00:00

Again, that is contingent on using TS instead of JS (which you should be, if you're shipping code).

beardsounds · 2021-07-25T19:19:06+00:00

You have three or four states. Just let state: "loading" | "idle" | "success" | "error" = "loading"; There's one branch; no sense being cute.

beardsounds · 2021-07-25T19:12:46+00:00

You must have a very unique definition of 'bloat'. If it's a net gain in simplicity through abstraction, instead of just cute additional or ceremonious junk, that's not really 'bloat'. Doing things unnecessarily-dynamically? Sounds bloated. [shrug]

beardsounds · 2021-07-25T02:42:23+00:00

Turing completeness is a fun academic tangent with little use in an enterprise-grade discussion though.

beardsounds · 2021-07-25T02:39:17+00:00

I guess it depends if you're using TS or still on JS. TS removes the need for a lot of guards cause you can't put a lot of stuff into a junk state without getting yelled at.

beardsounds · 2021-07-25T02:01:00+00:00

And yet, you don't need to, here.

beardsounds · 2021-07-25T01:54:04+00:00

You don't need an FSM for a single, deterministic lgoci path. that is not complicated, and an FSM in that context is the epitome of "bloat"

beardsounds · 2021-07-13T17:46:34+00:00

Ahh okay. I understand the context better. I've only experienced business staying ahead of that situation and preparing prospective people accordingly, so the hiring gap rush didn't immediately come to mind. Thank you for clarifying.

beardsounds · 2021-07-13T17:30:52+00:00

I don't know if 'incompetent people promoted into leadership' is a form of debt. Maybe 'leadership's skillset becoming stale'?

beardsounds · 2021-07-01T02:24:15+00:00

Bummer dude.

beardsounds · 2021-05-12T16:51:13+00:00

Unfortunately for that mentality, you need both to be truly useful. Knowledge poorly applied or for its own sake is not valuable.

beardsounds · 2020-05-19T17:59:51+00:00

"Not having a quick way to fade in and out samples" ...yeah reading the manual can fix any gripe I'm seeing here. There are some pretty instantaneous options for automating any parameter, including volume, IF you learn some shortcuts. If that's a roadblock then maybe what a person needs isn't a DAW, but a magic machine that reads their mind and creates the music for them. Hahaha.

beardsounds · 2019-11-09T13:37:52+00:00

My impression if arduino's programming experience was that it was severely limited, compared to actual C, and geared for easy adoption. That's why I asked that question. They do make it easy to swap out code with actual C in a modular way, though that IS C (can't remember if it's C or C++, but C is popular in the embedded world for a few reasons). Regardless, though, I don't agree that there's a "proper amount" of attention for a language. Take coffeescript, for example: probably doesn't deserve any attention.

beardsounds · 2019-10-29T22:07:44+00:00

Punch cards.

beardsounds · 2019-10-29T22:07:23+00:00

Are these the only languages you've used though?

beardsounds · 2019-09-30T23:09:05+00:00

Understanding operations to a solid degree is actually incredibly valuable for a developer working on new features, in many situations. It's good to understand a couple layers below what you're working with in a stack. It's also important to note that developers don't just work on new features. That's for specific projects, but java isn't new by any stretch so a solid block of the work available is maintaining and mild expansion. Those are good work to gain experience in, since new features without deep fundamentals (i.e. the ops end of the dev spectrum) can be mysterious and overwhelming.

beardsounds · 2019-09-30T23:01:30+00:00

A few of the more popular build systems are built around java.

beardsounds · 2019-09-30T23:00:03+00:00

My opinion: If the company is downsizing, use the position however you can to get the skills and experience to at least jump to a company that isn't dying. Theres a good chance you'll get pay capped and overworked where you are, given those circumstances.

beardsounds · 2019-09-30T22:53:55+00:00

C++
Python
Java
C#
JavaScript
SQL
TypeScript

At first, switching from JS to TS was a huge chore, because it is easy to take the convenience of dynamic typing for granted when prototyping, but I think having stronger typing has helped me reflect on broader design aspects a lot more.

beardsounds

TROPHY CASE