1,583 karma · joined October 27, 2020
The people vouching for this at Google are likely product marketing managers, public relations folks, social media managers, etc. All they do is write corporate garbage all day, and much like we have "nit"s in PR's for formatting, variable names, etc; they likely have similar reviews that get flagged for "non-inclusive language" or whatever this is. So they have brilliant idea: the Code people use auto linters/formatters that we enable by default (hey gofmt) and everyone loves it, how about we do the same for the Prose people!
Basically: "All I write is corporate garbage, and all the writing I consume is corporate garbage, and all my coworkers only write corporate garbage, therefore everyone would love a corporate garbage-ifyer!"
IME, F are the only ones to whip out their laptop at a house party or bar at 10PM on a Friday night because they felt an insatiable to work on some feature request; GMA may do the same when on-call, but I've never seen it otherwise.
I'm personally going the other route: Class of 2019, secured a decently sized FAANG bag (barely worked the whole time while doing it), and now I'm transitioning to a position with even fewer hours of commitment required but also lower salary. Going to focus on things I've come to find more important than money and code.
I wouldn't recommend dropping to WASM until you've ironed out the ideal data structures/algorithms to use, and have spent some time in the devtools profiler. Hacking on ideas in JS is (IME) much faster than doing the same in a compiled language, and the built in profiling in browsers works far better for JS than any WASM (again IME). Only after you have an optimized algorithm, data structure, and implementation, and still find perf isn't where you want it would I recommend rewriting in a compiled language -- even then I'd wager having the optimized reference implementation around will make this much easier and faster than if you tried to start from 0 in the compiled language.
Bonus points if you can reuse tests and/or have a debug mode that runs both implementations in parallel and throws on any differences in output.
Of course, this is somewhat tautological: if they weren't burning money, they'd just be a company. Startup phase complete.
Shame the recall didn't go through.
State of Jefferson FTW.
Unfortunately that term applies to basically everything... computation at every classical level we know only requires "maybe have state, maybe update state in response to environment, maybe move to new environment based on new state, maybe repeat".
Case in point: it's not TB, as you stated, but rather PB.
"hey I'm thinking of making this project, do you think you'd use it?" // "Yeah sure, seems helpful I guess"
you have:
"hey, person who told me they'd use this, here's the latest update where I've implemented X feature you and some others requested, I also am trialing Y feature that I think might be cool, and I polished Z item that I saw some others were getting hung up on, do you mind trying the latest version out and letting me know what you think?"
If you're unable/unwilling to maintain those kinds of relationships/conversations over the long term, consider a PM.