Obsidian Source: Writing good software is really hard!

Summary

Pending synthesis from local Obsidian source.

Original source title: Writing Good Software Is Really Hard!

Extracted Preview

I cannot emphasize it more. What do i need to do?

the requirements to problem solving arc: Given a very vague problem statement to a clear working solution, so anything that helps you build that

why consistency is important
end of cycle, and how 80% of stuff happens in the last 20% time window.
why projects fail?
why you cannot predict the future?
what is something you can do to be a better software developer?

---

Note: This blog is in a long time making. I've been meaning to write something along similar lines, but didn't know how exactly to structure this. Still, I have a lot to learn, but here goes a blog written to the best of my abilities.

Introduction

If you are even vaguely interested in the tech field, the story of Zuckerberg and how he built Facebook must have made you think just how much this field pays to little goblins called "software developers". With many such cases of bagging riche salaries, spending vacations abroad, sending their children to Ivy League schools - software engineering became such a coveted job that many people have made cracking the job their livelihood(sorry Topmate, I just hate you). Especially in India, there are so many developers that .... <insert some graph, statistic>

So... What Exactly Does A Software Engineer Do?

Integration Notes

Source folder: /home/yashs/Documents/Docs/Obsidian/Research-Notes
Local source: /home/yashs/Documents/Docs/Obsidian/Research-Notes/Writing good software is really hard!.md
Raw copy: raw/obsidian/research-notes/Writing good software is really hard!.md