I had an elective class that was open notes/book so I collected all the notes and resources the professor provided, put them into a single PDF, and then just text-searched them in the class. Worked well but the class was a joke and it didn't matter if I left knowing any of the material. Just had to check the box.
Check out https://www.hey.com/. I've found once I categorized the majority of my regular senders to either go to paper trail or feed, I get so little actual mail. Then when I want to go see my feed for Patagonia's latest marketing mail, I can. No number says how many are there, nothing is bold. Just a click or two and I'm looking at my feed. It can even auto-delete after 30 days if you want.
Despite the fact that it may sound like it, I am not affiliated with Hey, just a happy user.
Speaking only for my own org's stated goals, they try to hire within the same timezone or close-by. So South America, for a west coast team, would theoretically work but Europe would be a tougher sell. Amazon also hasn't historically done a lot of remote work (as far as I've seen anyway) so, pre-COVID, an office would likely need to exist in a given area.
Something I run into a lot is a JSON-like blob of text I'd like to be formatted as JSON (new lines and indentation). Most JSON formatters choke on improper JSON (understandably). It would be great to have a tool that was more lax. Like browser support for terrible HTML lax haha. If I could paste JSON-like strings into a text area and have it fix and format it as best as can be, that would be great. Some examples of non-JSON syntax to handle would be like single quotes instead of double, arbitrary JSON nodes (not necessarily wrapped in `{}`), some pre or post text (some non-JSON text at the beginning or end), comments amongst the JSON, etc. Another JSON aspect that would be useful is something to escape/unescape JSON (specifically double quotes). I deal a lot with JSON that includes escaped JSON in values and it would be great to have some better way to visualize and process those blobs. Sublime Text has a nice plugin to handle some of the escaping/unescaping[1].
My team makes several commits locally, then rebases, squashes, and pushes the squashed commit to the trunk which has CI. This maintains a local, regular backup of your code and collects features into single commits for the trunk which are easily revertable if found to be problematic. This flow will not work for everyone, but it works very well for us (a team of 8 at a FAANG company).
Edit: Rereading your comment, I suspect you mean non-local backups. Our organization has a special remote only visible to you and those you allow for pushing code you'd like to backup off of your box.
That sounds like feature branches but with more steps and worse. You can't share your unfinished work non-locally, for one thing. And it has none of the advantages of CI because you still have infrequent large merges.
This ticket wasn't an encrypted ticket (and thus was not locked down). I'm looking at it right now and I have nothing to do with security nor PR. I don't find this surprising as it contains no proprietary, classified, or customer information.
There is potentially traceable information there including laptop browser extensions as well as phone camera specs. I'm not sure how doxxable it is but if the Intercept were exercising appropriate caution they wouldn't have published the photo.
Sorry, I wasn't trying to dispute your statement on the Intercept's actions. I was just pointing out that the ticket wasn't any more secret or locked down than any normal ticket and thus a large swath of the company had access (although the ticket has since been made private), not a highly restricted distribution list.
The key mental shift (for me anyway) is that if a system can be brought to its knees by a single person, then the system is very likely flawed. You need to design a better system when the flaw in the system is the people. What that often looks like is changing/instituting processes such that quantitative measure (metrics, checklists, etc) governs decisions (thereby removing much, but importantly not all, of the human element), or you design processes in such a way that one person is not in charge of making the decision (the "two person rule", CRs, leadership approval). There are of course other tools but these two are pretty common in my experience.
> if a system can be brought to its knees by a single person, then the system is very likely flawed.
That just means that the person who designed the system deserves the blame.
I'm only half-joking here. You can't just rely on the "system" – someone needs to be responsible, either for the decision or for creating the system that makes the decision.
Having a system/process is not about removing accountability, it's about reducing discretion/cognitive load where it's been identified as risky. In fact, having a system/process in place to point to and say "this individual did not follow the steps/process/rules" makes an unbiased conversation about their performance much more possible.
Yes and this works when you're doing something for the 10th time. It totally doesn't work when you're doing something innovative and risky, which I assume is the kinds of conversations we're talking about here (this subthread is contextual to a senior amazon exec, he's probably not PMing someone forgetting to change the backup tapes)
As someone who has been on these calls multiple times, I think "rip someone apart" was an attempt to portray the bluntness with which feedback was provided but (as other commenters have mentioned) not to import any ad hominem attack characteristics to the feedback. Although admittedly the language used was contrary to that. While Amazon certainly has its flaws and has plenty of room to grow in the hospitable work environment category, cbell's feedback on weekly calls is not one of those areas imo.
I consistently have to switch to Chrome devtools as FF (my default browser) devtools crash or hang on large (1.29MB gzipped) bundles like one of the apps I regularly maintain. While we want to do some code splitting, module lazy loading, and refactor to make tree shaking more effective, the fact that Chrome just works when FF does not is very frustrating.
