I respect some of what’s being said about “mappers” vs “packers” - but the article presents the idea that there are 2 kinds of programmer and you’re one or the other, largely based on growth as a “real” mapper.
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 wonder if your tone and advice still make sense in these similar scenarios:
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.
I had my “first Joel review” while applying to work at Stack.
Joel still did the final interviews for all applicants back then.
After 4-5 back to back on site interviews, I was spent. Somehow we ended up talking about old AutoIT scripts I’d written - many of which include apologies to future readers in the comments.
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.
So the overhead to begin a video stream is due to the size of video data? Would video behave generally more like audio data (could stream immidiately) if the typical user bandwidth was larger?
The silence here is stunning. Most of the support I've found is on slack or Google groups related to Mac administration (google macadmins) / munki packing tools. Not quite macos development, but a good place to learn how to package things.
I feel that pain on the splitbrain docs. That's my number one complaint about their API's - I'm never sure if I'm on the newest. That said, there's a "familiarity" to them... once you figure out how things changed it's easy to quickly determine the age of a code sample.
You should try the custom runtime again! It's come a long way since Beta.
I don't think that unique really applies here - You can do the same with Google app engine standard runtime, or custom runtime if you want to use your own dockerfile.
https://cloud.google.com/appengine/
You are making an assumption that obesity is because people overeat, and that "moving around" is somehow a counter to that.
Have you considered the amount of sugar found in virtually all SAD based food could be the problem? (Setting aside the movement debate and the false premise it creates about energy in vs energy out).
That last line gave me a chuckle… the most positive feedback Bartik could provide, which somehow hurt more for the writing.