Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's simple: understand what the goals of your team are for the current year. Write the code with supporting those goals in mind.


It's interesting you call out a year as a time span. I have no idea what the goals will be in a year, let alone how I'll code it. A year seems like a really long time, but also just short enough to justify adding extra work in early. My timeframe is more like a week to a month. Obviously different orgs will have different time windows for real reasons.


Most companies have a revenue goal for the current year. From that revenue goal you can infer what software capabilities need to be obtained.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: