Absolutely this. It almost seems like a controversial opinion sometimes, but microdependencies is a code smell imo. This could largely be improved by providing a more extended standard lib, at the cost of innovation and velocity maybe. I found this interesting: https://blessed.rs/crates
3h5Hne7t1K
People like you should be in leadership positions. The landscape rewards quick solutions, and quick solutions are rarely good solutions. "Whatever works" might still be a bad solution, just look at electron and that entire ecosystem.
Interesting. Im curious, what are some key areas of math that you think is the most interesting/useful for software engineering (that you would personally recommend learning)?
I will likely have some spare time in the following months and i currently plan to spend it on deepening my senses related to linear algebra and analysis.
I need that story
For those wondering, this seems to be MIT licensed. I didnt check all components.
I think you are misguided. Given your level of experience, you are not in a position to spew hot takes on software architecture.
There is something else underneath this. Did you try to use linux or something?
General advice when it comes to software is to just start. There are always different paths, depending on what type of programmer you are. My opiniom: choose simple, not easy.
This is terrible advice. Communication is the solution.
Very cool! This is the kind of stuff i want to see. Is AVR still the best choice for this? Any Risc-V ICs that can fill this type of role yet?
Of these, only zig compiles to binary code. The others are usually interpreted.
Name checks out
Dishonest and misleading. gdb ./main.elf, break 45. Learn your tools. Optimize for learning. Select tools that generalize. Avoid lock-in.