4 ms·
I'll save you some time. There's four ways, in order: 1. write an open source side-project 2. start a company 3. join a startup as one of the first employees
by baby 3y ago
I'll save you some time. There's four ways, in order:
1. write an open source side-project
2. start a company
3. join a startup as one of the first employees
4. become the best employee and prove yourself over the years at some corporation, and they might let you participate when/if a green new project comes up
- solardev 3y ago6. Work at a small or medium company for a year or two, and propose something better that will save the business time & money. That's how I've gotten all my greenfield projects (there's been many!)
- culopatin 3y agoSame here. I work for a big slow corporation but we’re a team of 2 and I’m the only one who codes and what the guy that left built was outdated the moment he started, now we’re getting ready to move to the cloud and nothing is compatible, so complete rewrite.
- LanceH 3y agoLots of consulting or contracting gigs are about building out something new.
- not_the_fda 3y agoI was going to say design services. Nearly every project I do is greenfield. Of course there are constraints, but its all new code just about every time.
- qd011 3y ago5. Be part of a new team.
- brotchie 3y ago4 is true. It’s a combo of proactivity , risk taking, skill set and reputation. I’m on my 6th greenfield project across different orgs at a FAANG: one wildly successful, some moderate, and others product-market-fit failures. In first joining, I was tasked with adding to an existing system, but befriended some Data Scientists on the side and started helping them automating their work, unofficially 20%. This spun out into a full on project that got VP backing. That set my reputation for executing zero-to-one projects, and has stuck since. It’s a high variance approach, since promo is tied to impact, and it’s borderline impossible to execute greenfield projects that ALL get product market fit. Some folks can’t stomach that kinda of career variance.
- xhrpost 3y ago3. Technically true but it's not always what you want. A lot of startups are often doing rather simple technical work. My last job at an early stage was just writing CRUD routes for form intake. Gets old quick. Just FYI for anyone searching.
- wg0 3y agoOr insist on a new Microservice out of an already existing microservice. Modularity, scalability, separation of concerns etc are your fig leaves. PS: Have a cool name ready. Rather already start it calling that even before it is commissioned.
- closeparen 3y ago4 is true at a stagnant/steady-state company, but a growing company needs lots of new stuff created, and people with a bit of initiative can create and own domains far beyond what their titles or years of experience suggest they ought to be entrusted with. Being in a context where doing big important new stuff is a positive-sum game can make a huge difference to a career.