wikwocket
Joined 15 years ago
Joined 15 years ago
The goal of fizzbuzz in a phone screen should not be to see if someone can solve it in an optimal memory-efficient framework-idiomatic way. Clever syntax and data structure use is lovely, but these are really about finding whether someone can use a 'for' loop and an 'if' condition.
I agree that it'd be nice if they warned you about features you're using that will be turned off, but I don't think it's unreasonable to expect that people requesting downgrades understand which features are in which plan.
Maybe this could be suggested to GitHub's Paperclips project, to avoid future confusion?
There are conferences for most any language with wide adoption. There's also a Slack conference (not "TeamChatConf," but a "Slack Frontiers"). There's a GitHub conf (not "OpenSourceDevCon," but "GitHub Universe"). There is a Datadog conference, and so on and so on.
Maybe C just doesn't have one big company, or an ecosystem of smaller ones, that stand to benefit from gathering a bunch of C devs in one place.
In general, don't disqualify yourself. That's the hiring manager's job. Your job is to qualify yourself: present your best self, and demonstrate professional confidence and competence.
Another annoying one is how you can choose an exact song to play on tablet or on PS4, but not from your phone - you can only shuffle play there. Try explaining that to a 5 year old.
I worry that if you try to dumb down things for kids, they might become interested in dumb things. :)
Also, as the OP mentions, it can be a fun "pedagogical challenge" to try to explain free theorems or turing completeness or MySQL sharding to a young child. And you may find a clever way to describe it, that they can easily understand, which is satisfying for both of you.
This is the same idea as making your system work across availability zones/datacenters/cloud providers. At a certain scale it becomes a good idea.
Here's a rough sketch of possible headcount. I'm making these numbers up, but maybe you can see how it does take a lot of work to make a business like this work.
- Engineering
- 5 - frontend dev/QA (web, tablet, responsive, A/B tests)
- 5 - backend dev/QA (app logic, video/content hosting, scaling up & out)
- 5 - payments dev/QA (payments is huge and complicated, probably a few payment processor partners)
- 5 - app dev/QA (iOS and Android)
- 5 - product owners (web, 2 apps, email, internal tools for agents etc)
- 5 - management (cto, engr manager, director etc)
- Business
- 5 - creator experience, patron experience, outreach, community
- 5 - marketing, advertising, lifecycle email and email campaigns
- 5 - partnerships, relations with big creators, collaborations
- 5 - fraud detection and remediation (fraud is huge, chargebacks are expensive, and the ability to charge $1 to test cards attracts fraudsters)
- Operations
- 20 - agents handling creator/patron requests/issues (more if 24/7 or multiple languages)
- 5 - ops/systems (keep everything running, downtime means less income)
- 5 - HR, recruiting, accounting, etc
This is probably under-representing the business side since I am from the engineering side. Also it looks like they are hiring more people for all these teams. If you want more info, you can always look up Patreon's job openings:
https://angel.co/patreon/jobs
https://boards.greenhouse.io/patreon#.WcFitC-6z-Y
https://www.glassdoor.com/Jobs/Patreon-Jobs-E915057.htmIt may be impossible to say right now whether this change helps kids get better at programming faster, but presumably, more kids will play a game that they feel is more approachable, similar to how the playtesters responded.
As an example, my daughter had no real interest in doing anything with a computer until we showed her she could move Moana's raft around with some Scratch/Blockly code in a Disney Hour of Code game. Therefore, I think these games are absolutely worthwhile. Let kids start learning the "hard parts" of programming after we've got them hooked!
As a result, I would guess a lot of Twitter's engineers are working on infrastructure, internal tooling, and moderation.
Regarding your example, doubling the size of a tweet, that was probably more work than one dev writing ALTER TABLE tweets MODIFY tweet_text VARCHAR(280). In fact, I don't know if you were around 20 years ago or so, but there was a similarly scoped project to double the number of digits we were storing the year in. ;)