When building software, there's one activity that consistently brings me:
- a lot of value
- without waste
I can summarize it in one sentence:
👉 Think before writing any code
Especially for complex features, I like to have a clear idea of what I need to build and why, what tradeoffs are involved, and what's the simplest solution I can come up with.
Simple can mean many things:
- simple UX
- simple code
- simple design
Simple is not always easy. But if I can find a simple solution at the intersection of UX, code, and design, that's usually a win for me (less complexity) and for the user (easier to use).
So you want to build a stable app? Check out this article to understand how the Flutter framework handles errors.😎
Read article: https://t.co/5bHsiYHjVX
Writing clean code might be hard🥲, but it’s achievable. Sometimes, trying to write clean code would discourage you from actually coding. Whenever you feel that discouragement, write your spaghetti and refactor later. That’s the only way you can tell a bad code from a clean one.
I've been too busy (everyone is...), but I'm here today to spend time with you. Feel free to ask me anything. I should ask too😎...
What have you been working on lately?
What can you do when you don't feel like coding but you have unfinished tasks?
Most of the time, this happens as a result of the frustration you faced trying to fix a bug on a complex project or when you're trying to learn a new technology.