phibz

The problem is that their leadership may not care. Bureaucrats at higher education don't take the job because they're good at it. They take it because they're not and want a job with high job security. The poor pay and unrewarding tasks are acceptable to them as a means to coast. Couple that with a job that can be quite stressful at times, students can be very demanding, and you have a recipe for entrenched apathy. I base my assessment on my time working for a University for 8 years.

The registrar's office are the wrong people to appeal to. The deans office can fix this, but they may only move if it makes the University look bad. That's where the news and media can help, but this guy likely needs help to make that happen effectively.

Their response on face value doesn't make sense. But if I had to guess, you inadvertently made someone in the registrar's office look bad. They probably had to answer to "why didn't you think of this?" If that is the case then it makes a lot more sense and is retaliatory behavior. You can't undo their insecurity and loss of face. Therefore you should not expect a reasonable response.

Act accordingly.

Educate yourself on your options. This is why people are recommending a consultation with a lawyer.

Reach out to your friends and contacts in the University. Leverage existing ones to make new ones. Others may be in a stronger position to put pressure on the registrar's office.

Use the news and media to further ratchet up pressure.

Stay positive. Fon't stoop to their level, it won't help you.

And if you have to walk away it won't hurt you too much in the long term. After about 5 years in industry nearly all companies stop caring about credentials. Just get your foot in the door somewhere and shine, that's what I did and it worked out for me 26 years later.

Hang in there.

I tried diesel about 5 years ago. I needed to do relationships where the foreign key lived on the other side of the relationship from what diesel wanted. IIRC diesel only supported the key on a specific side, I think it was a M:1 relationship. Diesel docs said this was unsupported. I was still learning traits at the time but navigating how to implement this in diesel was beyond me. I used sqlx and moved on.

I worked with a flash developer at its height and he used to say "it's ALL about the easing"

I'm really surprised they didn't even mention Len Sassaman

Backslash escape codes are a convention. They're so pervasive that we sometimes forget this. It could just as easily be some other character that is special and treated as an escape token.

I'm not surprised. If you do this again, maybe put a disclaimer at the top. Simply mentioning emacs will likely get you points with many.

Sometimes you just have to take it on the chin and move on.

I noped out of intelligence test when looking in 2020. It was a series of extremely difficult word problems that go increasingly harder. There were more questions than you could solve. You were judged on accuracy and speed. I took a 15 minute practice test and after a few minutes called the recruiter. You wanna talk architecture, you wanna judge critical thinking with programming challenges sure. But this, he'll no.

We use the LC exercises to screen people who can't program. They are on par with day 10 to 15 of advent of code exercises. An experienced, _practiced_ programmer should have no trouble with them.

I manage a devops team. We do ever thing from writing ansible, fixing broken services, to digging in to open source code and fixing sasl gssapi kerberos Auth.

You would be surprised how many senior people we talk to who can't don't code regularly. Building rock solid tooling is very much part of the job.

It really depends on what you're hiring for. Bit leetcode exercises can be practiced. You'll discover common patterns and themes. Being able to spot these and know how to solve them will save you time.

Also programming takes practice. I learned a ton of languages, but everytime I would use one I hadn't used in a while I needed to go to the docs. It was only after doing things like Advent of Code or forcing myself to code for an hour every weekend, that I became faster and more prolific.

This has only intensified as I moved in to management and my role shifted.

Edit: perhaps I got this wrong. Maybe they meant staff engineer as in very senior IC who does not manage? If this is the case your role is to be strategic. You might write production code, you might design architecture. Whatever your current project(s) they will have wide reaching business impact. Asking difficult questions that may make people uncomfortable is very much part of this role. Yes these roles are seldom hired in to by first timers. But once you've be in one before, being hired externally is possible. I have a hard time believing that this person could do this type role at this point in their career (yes it was 2020 so adjust accordingly).

I'll leave the below since it might be useful for someone seeking a mid-level career.

--

I think they are equating a staff engineer with a mid-level engineer. They say that companies don't hire for this role but in my 26 years of working this has not been my experience. Granted, I focused on < 1000 employee companies because I liked the transparency, mobility, and influence I had there.

I don't know what kind of role they were looking for, but not wanting to write production code in a software company usually means you are going to be in a support role. These are often not traditional software engineering roles. You don't have to have a college degree, but you need to know the material. Programming is a skill just like anything. You have to practice.

Interviewing is an inexact, unfair process. Keep trying, doing as many as your sensitivity to rejection allows.

The thing that many applicants don't know is that many parts of a positions requirements that seem fixed are actually flexible.

Focus on good communication skills, listen well, and demonstrate concretely how you exemplify the skills they're looking for. Often the how and the why matter more then the what.

Recruiters usually know very little about what they're searching for. Yet they are the first line filter. Say what ever you need to say to move past them. But be mindful that they will often report what you say to the interview panel or hiring manager. Telling them an outright lie can be a bad idea.

Leetcode exercises aren't fun and they're a time sink. You can and should practice for them. In many cases they are a first line screen to filter out the noncoders. If you're considering searching for a solution and cutting and pasting it as your answer, know that leetcode has basic tools to detect this. They track your time and keystrokes.

Most teams have a balance of dead weight, followers, doers, and leaders. There are usually more of the former than the later. This plays in your favor if looking for a mid-level role.

Good luck out there.

It reads like he is assuming that missing messages from the mouse is not allowable.

I would say think of it this way: what happens when the mouse moves between USB hid messages?

If the mouse moves between messages sent via USB HID do the later messages capture the delta between the last and current message. Including the movement that happened in between?

Do the input messages, both those sent over USB by the mouse as well processed and presented by Windows, give relative or absolute positions?

The messages already represent a discrete sampling if a signal. You should be able to recreate the original information reasonably well without processing every single message.

The article hit on some great high points of difference. But I feel like it misses Cutler and team's history with OpenVMS and MICA. The hallmarks of their design are all over NT. With that context it reads less like NT was avoiding UNIX's mistakes and more like it was built on years of learning from the various DEC offerings.

I never understood why people believed this BS. The process of administering an exam requires direct interpretation from another human. They are just as fallible as I.

Seems like having tailscale or at least wireguard would be really useful in this

The level of noise went up dramatically after the first year. I read that this is part of the panel aging. It hasn't gotten worse since then. My two biggest gripes are high brightness areas don't work on large portions of the screen. A windows file browser is basically unusable.

The heat is probably what will eventually get me to replace it.

I have the second to last generation Panasonic plasmas. 42" 1080p display. At first the picture was amazing but over time it degraded slightly with what looks like subtle noise affecting the entire display. Solid colors have a faint shimmer of noise in them. As if white noise was blended with everything.

I still use it as a bedroom TV. I can barely lift it myself and it claims to use 450watts of power. It's certainly a lot. It's notably warm near it and will heat my room if I don't open the door.

Still the picture quality is very good at a distance. Only oled or micro led displays look better.

Look up the YouTube series work from AngeTheGreat. He is building a realistic physics based parametric audio simulation of car exhaust.

Perhaps more entertainment than education but he is a great place to start.

Standardizing on an established shared standard was never motivating for Microsoft. Early they profited by ensuring backwards compatibility for ridiculous periods of time. That was their pitch to customers. Buy your software and it will likely still work in 10 years. Even when shifting from dos pre NT windows you had an OS that allowed programs that thought they had sole control of the machine to continue to run by using some fairly sophisticated techniques and features introduced with the 386. Their model: get users, keep users, get recurring profit was their model. Standardizing on anything didn't really matter unless a significant user base wanted it.

And not having open or shared standards was viewed as a feature to drive down competition.

ATT started out UNIX with their hands tied. Hence BSD was birthed and then later ATT tried to put the genie back in the bottle. But it the economics were different. Hardware costs were the main driver. The OS was a given.

Starting over sounds great. But if history repeats itself, which it usually does, then we are far more likely to see something take (copy) ideas from current OSes and evolve them rather than a radical sea change where we star over.

Also now that Microsoft is shifting (shifted?) to a business model where selling OSws isn't really profitable will their behavior change?

You could use local talk and another Mac with ethernet or a floppy drive. Mac file sharing is built in with system 7 and later

Why not something like Kafka or Redis?

Ken's footnotes are usually my favorite part of his articles!

I was half joking. I see. Thanks for explaining.

I meant that logistically you'd not be able to do it.

Sure you can still trade of course. but you might need things like preauthorization for every trade, and have to hold them for a given time before selling, which kinda makes algorithmic trading more difficult.

But hey ya'll just pile on. o/

The SEC rules if you're in the US are quite strict. You likely wouldn't be able to do quantitative trading own your own while working at a quant. Though, it might help you get hired as a modeler.

In the part about the Mac Portable it says "if you're feeling financial". Is this a typo or do you think this might have been written in part by an LLM?

This usage seems... wrong.

RIP #linuxhelp and #linux. Some good times there. Now bash.org is gone its like it never happened.

.bef Duck friends

You totally can and should. Being honest about not getting to something is better than covering it up. So long as its not a regular occurrence then it should be okay. And its even easier if you set expectations up front. "Hey im going to spend some time socializing with xyz today. I might not get to much sprint work"

As someone on dialysis, this would be amazing to see. I wonder if the same immunoresponse issues would happen with this like with a transplant.

The holy grail of transplant medicine for years has been acquired immunity, where you convince the immunesystem not to attack the transplant. Still hoping we see progress there, but this looks like a viable alternative to a donor transplant.

Read yes, understand... that's a different story.

I tend to treat code more like poetry or music. Its a shorthand for instructions telling the computer what to do. Depending on the language, naming, structure, and comments the original thesis may be lost or hard do understand. And in isolation short snipets don't often mean much or can change their meaning without context.