When programming something 'new' (somewhat complex to really complex), do you:
1) Write tests first.
2) Draw something, with pencil or with a chart program.
3) Start programming, see where it leads.
4) Procrastinate and think, "I believe I will know what to do when I have to do it".
5) Grab a coffee and just look at the internets for as long as possible to see if someone has already made this and you can copy/paste as much as possible.
6) Take a poll from staff to see if anyone wants to work on this first before you absolutely have to commit.
7) Say you did it the thing, and say it's in production, and really check if anyone notices.
8) Read up on internal work-related pages to see if you can build a "someone else should do this" case.
9) Find a way to tie in 34 other concerns you have with the software in general, that's definitely more important, and ask for a 14-month extension.
10) watch youtube videos that criticize movies you like just so you can feel something and then tell everyone, "There are some issues with this, we should remove the deadline as I am waiting to hear back from people, out of my hands".
11) Go on a meeting blitz, departmental tour to see if you can find anyone that will tell you not to do it.
12) Tell your stakeholders the requirements aren't defined enough. Continue that loop until the stakeholders have to write out the logic themselves. Teach stake holders how to write an if statement. Hire your stake holders.
13) YOLO, hardcode 200's on all endpoints and blame frontend developers for not requesting data properly, and when they schedule a meeting, claim you have covid symptoms, and learn how to paint on your down time.
14) write a giant list of excuses you fantasize about.
15) Let the stakeholders know that this gets very specialized, and you need to attend a conference in Hawaii to find a consultant that specializes in this XYZ thing.
16) Create a blog, get active on twitter and linkedIn, investigate Rust and how it's going to save your career and quit.
17) Quit.
18) Pretend you will actually finish the coding challenges necessary for FAANG jobs, get burnt out and research "onshore fishing" as a job.
19) Learn the use cases, understand that you could white label this mofo and make millions. Yea... dream about it. Think about it all day. Start making it. Never finish. Get fired. Research unemployment benefits.
20) Consider unemployment benefits as Series A funding.
21) Go hard, super hard, understand that you can change everything with this new software, work 24/7, people will bother you, "you should, like, hang out, take showers, and stuff." But you know, if you deliver on this, you will... doesn't matter, something great will happen. And you work. And you circumvent all blockers like Keanu in Matrix 1, not Matrix 4 cause it sucks. Boom Boom Boom! You finish! It's huge! You research "onshore finishing" as a job.
0 comments
—
Ask HN: How do you start new projects/tasks at work? · HackerTrans
1) Write tests first.
2) Draw something, with pencil or with a chart program.
3) Start programming, see where it leads.
4) Procrastinate and think, "I believe I will know what to do when I have to do it".
5) Grab a coffee and just look at the internets for as long as possible to see if someone has already made this and you can copy/paste as much as possible.
6) Take a poll from staff to see if anyone wants to work on this first before you absolutely have to commit.
7) Say you did it the thing, and say it's in production, and really check if anyone notices.
8) Read up on internal work-related pages to see if you can build a "someone else should do this" case.
9) Find a way to tie in 34 other concerns you have with the software in general, that's definitely more important, and ask for a 14-month extension.
10) watch youtube videos that criticize movies you like just so you can feel something and then tell everyone, "There are some issues with this, we should remove the deadline as I am waiting to hear back from people, out of my hands".
11) Go on a meeting blitz, departmental tour to see if you can find anyone that will tell you not to do it.
12) Tell your stakeholders the requirements aren't defined enough. Continue that loop until the stakeholders have to write out the logic themselves. Teach stake holders how to write an if statement. Hire your stake holders.
13) YOLO, hardcode 200's on all endpoints and blame frontend developers for not requesting data properly, and when they schedule a meeting, claim you have covid symptoms, and learn how to paint on your down time.
14) write a giant list of excuses you fantasize about.
15) Let the stakeholders know that this gets very specialized, and you need to attend a conference in Hawaii to find a consultant that specializes in this XYZ thing.
16) Create a blog, get active on twitter and linkedIn, investigate Rust and how it's going to save your career and quit.
17) Quit.
18) Pretend you will actually finish the coding challenges necessary for FAANG jobs, get burnt out and research "onshore fishing" as a job.
19) Learn the use cases, understand that you could white label this mofo and make millions. Yea... dream about it. Think about it all day. Start making it. Never finish. Get fired. Research unemployment benefits.
20) Consider unemployment benefits as Series A funding.
21) Go hard, super hard, understand that you can change everything with this new software, work 24/7, people will bother you, "you should, like, hang out, take showers, and stuff." But you know, if you deliver on this, you will... doesn't matter, something great will happen. And you work. And you circumvent all blockers like Keanu in Matrix 1, not Matrix 4 cause it sucks. Boom Boom Boom! You finish! It's huge! You research "onshore finishing" as a job.