Selfcommit
Joined 15 years ago
Joined 15 years ago
That last line gave me a chuckle… the most positive feedback Bartik could provide, which somehow hurt more for the writing.
I think a more realistic description is that everyone is a mapper. There isn’t a single body of knowledge that is “software engineering” - so it’s ok to encounter something new, “pack” it, then map it if it’s valuable.
Far better to encourage mapping than create false dichotomies that can easily work their way into cultural fit interviews.
“The candidate failed to find an obscure error in the JS console… clearly a packer - no hire”.
I am incredibly happy for those who have gained literal decades of life from this new treatment.
I do wish the wheel of progress could have moved faster.
1. You have a large number of peers who start chat conversations with “Hi, are you busy?” That question is begged with just “hi” and implies a forced urgency.
2. All your coworkers start email threads with “hi” and wait for peers to respond before continuing. If that seems ridiculous, you now have an idea what “hi” is like for remote workers.
Any good reads to recommend on self determination theory?
I wonder if there’s a measure for how well 2 GPT chat prompts collaborate with one another?
Joel was a great interviewer… that conversation turned into a game as Joel picked apart various ways he over compromise the script and asked how I’d respond in the next iteration.
I got a chance to talk about how it works at LISA last year: http://selfcommit.com
http://about.me/selfcommit