methods21

Been doing this strategy for over 20 years.

As a hiring manager / lead for technical positions, this is fine, and often proposed by the 'resume experts'. Where I get incensed is these statements where the original design/architecture that this individual was responsible for was the problem, and they are just bringing something back to baseline where it should have started. I see this ALL THE TIME. And this is with grace towards changing requirements etc. And not just on resumes, I see this on internal corp. accomplishments, and typically the higher the level the more the savings and more the unnecessary waste was to start. For example, CFO once claimed like $20mm in savings because he decommed a financial module that they bought and NEVER used and NEVER needed - this guy crushed is bonus this year.

Lets see how far from the $20billion offer they IPO at.

Bring back XML or a better format than both, or at least a DTD for JSON.

Never a fan of these 'click bait' headlines, and surprised it made it this high in hacker news. We get the 'premise', Mr. Money Mustache has been preaching similar for years, but these numbers are just not realistic. You need money to buy the house, maintain it, clothes, healthcare, NY is going to jack your taxes up, etc. and more, as all the folks have mentioned here.

Can some folks live more frugally, for sure, but this is unrealistic.

Dealing with this right now as a consultant. Also a 'semi-govt' company, with much more in annual revenue than in this article, running a highly critical production workload, and is having problems with a ESOL version Open Source software - that they are scared to touch/upgrade, and that is available in a fully up-to-date version, for purchase, with support etc., and indirectly asking us to support it, by essentially pawning off any and all changes related to said SW to me. Well, I recommended the upgrade path (to a current/supported and paid version) and I stopped making any changes to that component. They are still hemming an hawing, its unbelievable.

How can any trade be made and not know 'who' made the trade? Doesn't every trading account need to be registered/identified in some manner? KYC right? At a minimum the account holder would want to transfer funds to/from account....

I can't even buy sudafed without 3 forms of ID, yet we have 'invisible' traders of millions of dollars?

I haven't seen this guy in a while... tbh, at one point it almost felt like he was a shill for something.

Anyway check out the symbol: NANC

"Yet I think Tim’s single review was possibly as valuable as all the others combined".... and yet you don't even tell us anything about his review.... disappointing esp. considering the screenshots/level of details on other input.

On a different note, def. feel you pain regarding the copyeditor.

I see 'this guy' who wants or does build his own ORM, in every company I've worked with.

Reminds me of the BMW Heated Seats SaaS option.

What's even worse is the planned obsolescence, its such a huge waste of resources. I had a GE DW and fridge from the 1950s until 1995 and they still worked, albeit were a funky lime greenish color. And that DW washed the dishes better than the new replacement. Currently dealing with a 2 year old LG fridge that is dead.

I tend to disagree a tad with what you have said below, I've lost count how many interviews I've done at this point, one challenge is on the intake side and how many darn applicants there are or can be and that its typically the recruiting team interacting with them at this point.

The question in your example, is fine to include, but you need a non, yes or no or scale question to weed out unqualified candidates. For me, this is a very succinct question with a definitive answer. You'll be surprised at how many people will answer 'extremely comfortable' with Javascript yet not know what === means, so I'll ask something along the lines of 'what is the strictly equal operator in Javascript"... while any javascript programmer will know this, you'll be surprised that this type of Q alone knocks out 50% of the applicant pool, most of whom probably selected 'extremely comfortable' btw, and save my org. a TON of time.

"For example, for a role that requires experience in JavaScript, it's not unreasonable to confirm that experience in the questionnaire with a question like, Rate your comfort level working with JavaScript on a scale from not comfortable to extremely comfortable."

Yes - This.

What would be amazing is if Swift and/or Kotlin could just be the 'native' language across both platforms and work at native speeds on both platforms.