Recent submissions

Comment · 3 years ago
Being old as dirt, my observation is that potential tech revolutions take ten years after the initial exuberance to be realized broadly, or three to five years to fizzle. Of those that fizzle, some were bad ideas and some were good ideas replaced by better ideas. FWIW
Comment · 3 years ago
Still upset about Wikipedia too?
Comment · 3 years ago
This is amazing. Great format. It would be cool to link original recordings too, but merely nice-to-have, not essential. I love being able to listen to the solos unaccompanied.
Comment · 3 years ago
Large companies’ CEOs need to be wealthy in order to be in the club with others whose influence might matter. Wealth == Power.
Comment · 6 years ago
Comment · 6 years ago
Right, excuses carry no weight. Got it. Agreed! But fuck football coaches and sports analogies for business. Sports is a zero-sum game. Business sometimes is,sometimes isn’t. Depends on agility, creativity, and the market you’re in. If your boss quotes football coaches just quit on the spot (unless of course you are in sales).
Comment · 6 years ago
Yes, this!
Comment · 7 years ago
Democracy is ostensibly majority rule (don't nitpick). The majority of people are poor. Therefore, democracy is the rule of the poor (Aristotle). We do not live in a democracy.
Comment · 7 years ago
Sometimes what you need is change. I am sixty-five years old. I was a programmer for fifteen years, started a consulting company, then a software business. Was acqui-hired. Became VP Product Dev over 27 locations, 1200 developers, hundreds of products, then semi-retired for four years and worked on digital audio production. Got bored, did another startup, wrote code. Sold it and became CTO of a product division. Later worked for an investment group, became CTO for one of their acquisitions for almost ten years. Six years ago went back to technical work on my "reverse career plan" (junior programmer by the time I'm 75 ;-) ). Wrote js/react analytic front-end apps, Python back-end analytics, got into machine learning, co-authored a book about it, got some big data consulting gigs, learned Hadoop/Spark. Currently hands-on dev for Spark and ML apps.

For me, changes were the key. Burnout melts away. But you can burn out in any role. If you have the skills to do tech work, try to keep them alive. Coming back to hands on tech work is incredibly refreshing. So is leaving it behind for awhile when you've reached the burn-out point.

Comment · 9 years ago
It's a thing, isn't it? I mean, as words and phrases go, it at least means something, like not just front-end, back-end, or client-side view-model reducer mapping specialist. AI is much close to fully content-free.
Comment · 9 years ago
What's up with the phrase, "Still programming?" Would anyone think it odd for a 60-year-old physician to still be doctoring, or a 60-year-old lawyer to still practice law. Or for that matter for a 60-year-old artist or craftsperson to "still" pursue their craft.

Corporate culture embraces the notion of management as a profession. I think programming would benefit greatly from more of a tradecraft model, where leadership is provided by the master practitioner rather than the professional manager. In the alternate universe that's how we do it. The bottom line productivity boost is awesome. I don't know if it scales, but I don't care to scale.

-- 63-year-old full-stack web and machine learning programmer...living the dream

Comment · 9 years ago
This discussion misses an important element, the skill of the interviewer. It is unsurprising that unskilled interviewers' assessments are poor predictors of future performance. It would be interesting to measure the accuracy of interviewers who have had years of experience interviewing, hiring, and managing people.

Here's how I think it works. Skilled interviewers are biased toward rejecting candidates based on any negative impression. Structured interviewing has the same effect. It's the precision versus recall tradeoff. For this use case only precision matters. Extremely low recall is fine.

Also, in the GPA prediction example, the interviewer is penalized for predicting a low GPA for a person who performed well. But in hiring, there is no penalty for failing to hire someone who would have performed adequately.

(Yes, I understand there is an implicit assumption in my argument that candidates are not in short supply, but that's usually true, certainly at Google)

Comment · 9 years ago
The Triumph of Politics by David Stockman - totally changed the way I understand the operation of government.
Comment · 9 years ago
All the time
Comment · 9 years ago
Never ever take any kind of test before talking to a person, preferably the hiring manager. Not even for fun or practice.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton