I mean, I have seen both sides of the story. People putting too much effort into simplifying things where the product users just do not care about it, as well as people overcomplicating things while implementing features up to the point of the program being non-functioning (or very hard to update).
I would say that it is more about how coupled your field and the product you are building are with it being implemented properly. For some areas, like most of the web or building SaaS, it is not as tightly coupled as for other areas like system engineering, building high-performance products, etc.
I've been using The Corne keyboard for about half a year now. And this is a compilation of my thoughts on where the idea to use such a keyboard came from, the process of making the keyboard, some difficulties I encountered, and my general observations throughout this process. Hope it benefits some people.
Just because the story is believable doesn’t mean that the people who are in the story are without responsibility or fault.
When you get into a lease agreement you should know how to pay going into it. If your landlord doesn’t take a form of payment you can handle you don’t sign the lease in the first place. That’s your life responsibility as a functional adult. Paying rent every month isn’t a surprise. Being low on funds isn’t an excuse and being low on funds isn’t the issue at hand.
Exactly. I use comments either when some inherent complexity is at play or when I've written seemingly weird code and need to make it easier for myself and others to understand why it's hacky.
I generally try to avoid the latter case, but sometimes, especially when I can't afford to refactor, I just do it, and in such cases having comments is just better than having nothing.
I have experience in both backend and frontend development, mainly in fintech but not limited to it.
I've primarily used JavaScript and am well-versed in popular frameworks and libraries like React, Fastify, and Lodash. Have also used other mainstream programming languages (Python, Java, C++, and C) for both recreational activities and university projects in the past.
PostgreSQL has been my go-to database, but I've also worked with Redis, MongoDB, LevelDB, and Prometheus for various projects.
I have experience with sysadmin and DevOps tools, including Linux/Unix, Bash scripting, Git, Docker, and Nix.
I’m a passionate developer who enjoys learning and building new products. Feel free to reach out if interested in collaborating!
I don't feel qualified enough to judge the quality of the design itself.
However, presenting your ideas in the form of a chat log, just like some philosophy books that explain their point by using dialogues is a creative approach.
I guess this would also work well when presenting written interviews. :)
> However, presenting your ideas in the form of a chat log, just like some philosophy books that explain their point by using dialogues is a creative approach.
It’s just an FAQ with different styling. “Conversational” FAQs aren’t rare, though they usually tend to be humorous too.
some sort of pattern which can be considered in one of those new minimalist designs like from teenage engineering.
I don't know but I also couldn't read the whole thing because dark reader messed up the colors so I would probably have such website work well with dark reader
reply