Software engineering is highly contextual. As a professional, I write tested, documented code within mature and responsible architectures that harmonize with current and anticipated future business needs, my company's infrastructure, adjacent and legacy systems, pragmatic balance of technical excellence vs. deadline pressure, etc.
In a genuine passion project, I'm having fun. If you're checking whether I've dotted the Is and crossed the Ts in terms of testing, documentation, edge cases, etc. you'll find that I haven't, because the whole point of programming outside of work is release from the tedium of professionalism and an opportunity to go straight for the novelty and joy of making things work at all.
For projects specifically intended as portfolio pieces, I'm not sure how I could design software appropriately (or evaluate candidates' designs) in the contextual vacuum of "needing something to put on Github."
Comments
Software engineering is highly contextual. As a professional, I write tested, documented code within mature and responsible architectures that harmonize with current and anticipated future business needs, my company's infrastructure, adjacent and legacy systems, pragmatic balance of technical excellence vs. deadline pressure, etc.
In a genuine passion project, I'm having fun. If you're checking whether I've dotted the Is and crossed the Ts in terms of testing, documentation, edge cases, etc. you'll find that I haven't, because the whole point of programming outside of work is release from the tedium of professionalism and an opportunity to go straight for the novelty and joy of making things work at all.
For projects specifically intended as portfolio pieces, I'm not sure how I could design software appropriately (or evaluate candidates' designs) in the contextual vacuum of "needing something to put on Github."