Most of the tutorials you have read or watched till now usually do one thing, spoon-feeding. This is “OK” to learn a new thing but not good when yo...
For further actions, you may consider blocking this person and/or reporting abuse
My most important tip is this: developing software is a team effort. It means you need to interact with people, plan with other people, architect the software with other people, work with other people, help other people, ask help from other people. Developing software has as much social aspects as it does technical aspects. It means you will be giving presentations, sitting in long boring meetings, working with people a lot smarter than you, a lot more talented than you, and vice-versa. But what matters is working together, to get to the goal, together. Otherwise, the software doesn't get done.
Great suggestions.
I only use paper when the problem is long or if I have to explain to others later or for ui process with multiple screens.
Big problems can be solved in small chunks. "Divide and conquer". Also double check with coworkers about the process and results, inclusive with final users.
Good strategy.
The point of the article is also known as Klang's Conjecture:
If you cannot solve a problem without programming, you cannot solve a problem with programming — @viktorklang
Oh I did not know about that. Thank you
Another great quote.
This is why I love test driven development. It forces me to stop and think about the problem and break it apart into smaller chunks. Jumping right into coding is recipe for diaster.
Thanks for your views.