greyhair

I love the price on that.

I agree. Why memorize something that is well documented? Do you understand basic interrupt management and the existence of interrupt controllers? Good. Understanding basic concepts matter, but silicon implementations of a concept? No.

One question I have found useful in embedded development is asking someone to discuss the difference between a thread and a process, and the difference between thread based OSs and process based OSs. It is a general question, not bound by anything like CPU architecture, but just gives an idea into whether the person is comfortable about general memory domains.

I have mentored people, bright programmers that never worked in small embedded systems, that initially tripped all over the thread model, but eventually came to understand it.

I have been developing in embedded systems for 38 years, and I have the shortest skill set you will ever see on a resume. I only put down the things I know.

On the other hand, I have reviewed resumes from people with five years of experience that are 'experts' at twenty five unrelated technologies. As soon as I see that, I think, 'yeah..... no'. I worked with some genius level folk at Bell Labs back in the mid 1990s, ten years into my career, and they were each really good at two or three things. I took note of that. Yes, they could figure other stuff out, they could move on to new technology, updating the three things that they were good at, but that list always seemed to be short.

You have to laugh at 'experienced' or 'expert at' followed by JS, JAVA, Full Stack, Python, Linux, BSD, C#, AWS, C, C++, MySQL, PostGRES, Lisp, Lua, Azure, MathCAD, DSP, AI, Excel, SystemC, Perl, regex, Bash, git, assembly, Verilog, ...

Are you certain bitwarden has not? I read a thread here some time ago where 1password was bragging that they have never been breached, and someone basically commented back "they have never been breached that they are aware of".

I am concerned at some level on the lastpass breaches, but I am less affected so far than I have been by the equifax, target, and t-mobile breaches. I have had years of free credit monitoring since each one of those handed out enough data to compromise my identity several times over.

FIDO, UTF, WebAuthn. It can't get here fast enough.

User authentication has been a hot mess for at least two decades. Passwords need to go.

Being that the blob is never decrypted off your local machine, it would have to be a local data API.

I read the whole piece. My key observation, is the author's assumption that HR was 'there for the employees'. HR doesn't exist for you, HR exists for the corporation, for the protection of the corporation.

It astounds me, in this day and age, that employees think HR is there to protect them. I understand the misconception from young people at their first job, but the author is 60 (+/-) over the time of this story.

In my 38 years of working at medium to large corporations, I have had exactly one time when HR was useful to me, and that was on my way out the door in my prior job.

I like very lightly printed graph paper. Very pale blue at 5 lines per inch. I can ignore the lines for free hand, but they provide nice guidance for more structured drawings.

I found just the opposite in college. For me it was high write, low read, concerning my own notes. The only value to taking notes for me was the active nature of writing helped pin the information in my head. Other than assignment and test dates, which were just bullet lists, I rarely looked back at my notes.

I think that was the sole value of doing homework assignments and term papers. Going through the act of working out a problem, or researching then writing about a topic, is what reinforced the learning for me.

65. I went from 1975 through to 2010 not owning a TV. Not even one.

In 2010 we bought a 55" HDTV (but no cable service), a BluRay player, and a Nintendo Wii. We also got a Netflix DVD subscription. We had three young kids at the time. I carved a 16 foot by 16 foot square of space out of the basement, floored with resilient foam tiles, hung the screen on the wall, added some inexpensive Ikea chairs, and the kids would jump around playing Wii games, often times with their friends over, and the whole family would share a movie on occasion. Two years later we added a Roku streaming box. Still no cable service.

My wife streams something from roku, netflix or prime, while she folds laundry (she does laundry, I do most all of the cooking and dish washing). I rarely watch the screen for entertainment at all. I sit in front of a screen for work, eight or nine hours a day, for the last thirty eight years. I don't need to see more glowing pixels than that.

I know my wife and I are outliers. She sees maybe four hours of TV streaming a week. I average maybe two hours a month, only because on occasion we will sit and watch a movie together.

My note above, enough relates more to frequency than volume. Exposure to one serving (a serving is not a full glass!) two or three times a week matters more than five or six servings once or twice a month.

If you drink enough wine, and that means frequency, not quantity, you will eventually develop your own taste for what you enjoy. At the same time, you will also learn to judge good from bad. Will you be able to judge the individual grape or region? Probably not, but good from bad, yes. To the point that you will occasionally dump a bottle down the drain after taking the second or third sip. Not the first, because sometimes your first sip will be a lie, but by the second or third, you will decide, this bottle is not working, and you'll just dump it down the drain. Make sure to note the grape/vintner/vintage so you don't buy it again.

It is important to buy different bottles of the same grape to see how it varies across vintners and regions. It is also important to buy different grapes, because you may be surprised over time what vintages you settle on as your tastes develop.

Dude, my brain is already rusty enough.

I enjoy wine, I am not a connoisseur by any stretch, but I can differentiate enough that I know what I like, and what I don't.

Friends of mine have held two professionally run wine tastings over the years, and they were great fun, and very educational. The wines were all decanted, you could not see what they were, and it was interesting to see that every wine scored on a bell curve with the group. The scores were anonymous, so you didn't have to worry about how you felt about any given wine.

My favorite part is that in each of the two tasting sessions, the highest price bottle scored well, but not at the top. In each, the top white and the top red were both roughly $30 dollar bottles. Also in each, a couple roughly $10 bottles scored really well.

The other thing that I learned, and apply regularly, is that at the $20 price point, you are generally buying a good tasting bottle of wine. $16 to $24 seems to be a really safe range for my tastes

Yup. Exactly.Epoch times. Slightly less reliable than the National Inquirer.