me: i’ve single-handedly written software used by tens of millions of people, you can see it right over at github.com/april
prospective employers: sorry, but unfortunately you did poorly in a high-stress 40-minute coding exercise, writing code with no time to think about how to solve a problem you’ve never seen before, in a terrible dev environment, while someone stares at you the whole time
=> More informations about this toot | More toots from april@macaw.social
@april they want people they can put in a crunch
=> More informations about this toot | More toots from licho@kolektiva.social
@licho @april
Speaking, demoing, and applying for a job create a type of high stress that's very different from the stress of, say, fixing critical production issues or working under a tight deadline.
I would argue that there are very few conclusions to draw from that kind of crunch.
=> More informations about this toot | More toots from tcurdt@mastodon.social
@tcurdt @licho I could see an exercise like this for a sysadmin, asking them to figure out why something is broken. That is frequently their job. Code developed this way, however, is almost universally garbage.
=> More informations about this toot | More toots from april@macaw.social This content has been proxied by September (3851b).Proxy Information
text/gemini