If you have any use case like one the author describes, maybe use an in-memory cloud database with tiered storage or a plain RDBMS. Iceberg (and similar formats) work great for the use cases for which they're designed.

I interviewed at Riot when I was trying to move back to Saint Louis. I could not muster up very much enthusiasm for League, and you could just feel the room shift into "just get through this interview ASAP" mode.

Can't help but feel I dodged a bullet.

- The Chinese government clearly has its tendrils in TikTok and uses it to push its oppressive censorship policies around the world

- The security implications of giving China a backdoor into a large percentage of American phones is too concerning to ignore

On the other hand:

- Explicitly targeting specific companies feels wrong. If security and censorship are real concerns here, Congress should be passing laws that apply to all companies, not just TikTok

- Even though there are sound reasons to restrict TikTok, this is still a transparently protectionist policy by the Trump admin and fits right into his nationalistic, totalitarian, xenophobic playbook. A broken clock is still right twice a day, I suppose

- Requiring a sale to an American company is the mirror image of China's forced technology transfers for foreign companies. Two wrongs don't make a right

I think the best scenario is for Congress to preempt Trump with laws that protect American security and free speech interests without executive action. That's easier said than done, though.

- Keeping his coworkers sane (barely functional codebases that are difficult to work with have a way of killing morale) - Having an intimate knowledge of the code base that can inform future feature work - Paying down tech debt that's generally uninteresting to more feature-oriented coworkers

Having a whole team of Freds is probably not a good idea, but having one in a senior engineer or tech lead role is really useful.

References:

https://www.ncbi.nlm.nih.gov/pubmed/28271513 https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4070655/

Exactly this. I got tired of lugging around my gigantic DVD collection and having them scratch or break with time. I've since ripped all of them, and Kodi makes for a fantastic frontend for my HTPC.

I attended my university's CS job fair, only to find that I had become almost completely unemployable to tech companies (granted, I only had a 3.3 GPA in CS; damn you, WoW!). I ended up taking a tech support job with a scientific computing software company after I was promised a quick transition into development. However, that too evaporated, ironically due to the stigma of working in tech support.

After about 8 months, I interviewed for a developer position at a Midwest branch of a major tech company, but was again turned down. Luckily, I was instead hired to be a QA contractor on a different team, whereupon I quickly transitioned into a non-contracted developer on the original team that didn't hire me about a month before the company's new CEO announced that we would not take anyone with lower than a 3.5 GPA. I took the opportunity to mention this fact at every opportunity to one of my co-workers who had originally voted not to hire me.

After about a year, I started interviewing new candidates at this company. You would think that, given my prior experiences, I would be more forgiving than my peers in looking at past experience. While I didn't make any judgments based on school or GPA (in fact, those were filtered out before the resumes ever made it into my hands), I did turn down several candidates who were "too enterprisey", i.e. did not have experience or interest in whatever tech was trendy at the time. Granted, these candidates also had trouble understanding and debugging simple perl scripts I showed them, so I was already not on board, but when those candidates were borderline hires/no-hires, that was something that swayed me in the "no-hire" direction.

Now, as a married thirty-year-old with two kids and several non-coding hobbies, I have neither the time nor inclination to use my free time to learn today's trendy languages and frameworks. My work keeps me relevant for now, but if that ever changes and I need to look for work, I'm terrified that my experience and ability to learn quickly will be irrelevant to prospective employers, who will just want to see the right technologies appear on my resume.

Before the switch, our team (advertising pipeline on Hadoop) used the waterfall method with these gigantic, monolithic releases; we probably released a handful of times a year. Almost without exception, QA was done manually and was painfully slow. I started to automate a lot of the testing after I arrived, but believe you me when I say that it was a tall order.

Soon after I moved into development, QA engineers without coding chops were let go, while the others were integrated into the development teams. The team switched over to agile, and a lot of effort was made to automate testing wherever possible. Despite some initial setbacks, we got down to a bi-weekly release cycle with better quality control than before.

Around the time I left, the company was mandating continuous delivery for all teams, as well as moving from internal tools to industry-standard ones like Chef. I left before it was completed, but at least as far as the data pipeline teams were concerned, the whole endeavor made the job a lot more fun, increased release quality, and weeded out a lot of the "that's not my job" types that made life hell for everyone else.

I know the comment was tongue-in-cheek, but it bears mentioning: when dealing with the police, your objective should be to escape the situation unscathed, not to provoke them. Remember that criminal charges, severe injury, or even death are possible consequences of any encounter with law enforcement.

1) Actually "work" a 40 hour week 2) Spend the other 40 looking for a new job