Comment by noisy_boy
2 years ago
> Most of my work has been jumping into some crazy existing codebase and figuring out how to understand and contribute to it, so greenfield buildouts are just not something I've repped out, and think that's a bit of a weakness.
Without any context of the details of the work, one thing that has helped me is to lookout for scope of improvements beyond on the codebase itself. E.g. is there opportunity to provide a UI to the end-users of the code base. If so, since you have touched the codebase to contribute to it, your suggestion to work on those things to improve end-user's life may get accepted and then you have something relatively greenfield to work on. Doesn't always work out that way but sometimes it might. Another approach is building something on the side that you know will be very useful, even though nobody asked for it - helps you figure out the quick way of doing it (what you mentioned) since these are POCs and you can't repeatedly spend too long on them.
Really good suggestions, thanks. I suppose since I'm looking for work, it might not be a bad idea to do this externally as well, if any prospective companies' APIs are available, and use them as portfolio items.