phibz

By gui i think the above posts meant the tailscale web UI for auth and account management.

The "tetris effect" is why I had to stop playing Lumines on the PSP. My sleep was dominated by dreams of that infernal game. Incidentally though I'm wicked good at it.

Or everything is just a list.

Sure. What if they are undecided about you. You're good but they want to consider other applicants. In that case you'll likely get silence.

But lets say they know you're not a fit. So they decline you based on your test project. What is the benefit to the hiring manager to have them or a developer sit down and tell you why you weren't a good fit? It costs them time a lot of time. That does not benefit their need, finding someone for their open role. The biggest negative to this behavior is a reputation hit for the company with that one person.

Liability: providing feedback gives you the interviewee something to argue about. It also is a communication done by acting members of the company and therefore relatively official. All it takes is someone being a bit rude, disrespectful, or even a misunderstanding to make this now official communication something somone could try and publically shame the company with. Its easier for them to say nothing or ver little at all.

With a third party recruiter there is an expectation that the recruiter will take a percentage of the placed applicants salary. And the employer expects the recruiter will bring them quality applicants. Therefore the rectuiter often has more leverage than you might and can sometimes eek out more information for you.

Im not saying I agree entirely with this behavior. Specifically i think ghosting an applicant especially later in the process is unforgivable.

But I also think its your personal responsibility to figure out where you stand technically and socially. Find resources, people who care about you and ask them for feedback.

The interview process is terrible and its only gotten worse in the 25 years ive been working. Hang in there and do your best, but try and keep your expectations reasonable; you'll live longer.

The payback on take home tests is seldom worth it. There is too much liability and risk and very little incentive to the company to provide honest feedback.

You should learn to accept the fact that you will not get an honest review. If you choose to enter in to a take home test go in to it with that understanding.

The interview process is a chance for them to review you, but also for you to review them. Make sure the process is equitable. If they ask for too much you owe it to yourself to push back. Ultimately they will respect you more if you stand up for yourself. It shows you have healthy boundaries and will protect their interests when you work for them.

What the author describes is many people. Being at an ivy league school doesn't change that. In fact it might make it harder.

Through overcoming stuggle and strife we become stronger. Most of us are scared children walking around in adult bodies unaware how tenuous our grip on life is.

Dont worry about them. Focus on yourself. When you get kicked in the teeth do your best to get back up.

I had a siamese mix cat that did this. It seemed to mean "hey. I see you." A kind of recognition with a touch of affection. Its definitely part of the cat language.

You keep coming back to them? Really? Why? They're interesting articles but they just scratch the surface and I don't see how further readings would change that.

I dont think i could give up the palm rests of my keyboard.io, but something like this looks interesting in that i might be able to customize it.

box_patterns exists on unstable. Unfortunately it's still not merged.

That's very hard to police and prove. It's easier if you pay them to be unemployed for long enough for their knowledge to be less valuable. This is very common with businesses like hedge funds. But I agree non-compete should be narrowly allowed and only in situations like this that are more equitable.

The article asserts that javascript is interpreted and was is bytecompiled so its faster.

I think this ignores modern JIT based javascript engines like v8. They're very good at optimizing hot path javascript code as native code. WASM should be easier to optimize give the lack of variability and permissiveness in calls. BUt as far as I know, this hasn't been done yet for WASM so it runs more slowly than it could.

It is possible to statically link everything except for libnss and link it dynamically. I used this trick to create recovery shells on Solaris back in the day that didnt need /usr mounted. Same thing worked on Linux from what I recall.

Seems like the solder paste + hotplate method would be preferable to hand soldering, especially for that buffer chip.

I agree. This is definitely about addiction and its bedfellow codependence.

I read the writing style as bizzaro, perhaps to soften difficult topics and to add intrigue. So to that end Michelle isn't actually puppeting Jeff. She's just a controlling girlfriend.

Hard truth #9. People won't stop clicking on listicles, so writers keep using them.

I have been going on a similar journey. My childhood was trauma over and over again. I learned to cope but those skills no longer serve me at 45. It seems you have been much more literal about "connecting with your inner child". I suppose there are many ways to do this. Good luck with your journey. I appreciate the struggle.

> I have periodic crises of conscience where I wonder if I've been doing programming wrong all these years, or if it's an example of a community barking up the wrong tree.

When I first learned of FP about 20 years ago I thought it was a terrible idea. But I've convinced myself I have been proven wrong time and time again.

I still think sometime it's complexity for its own sake. Eg. why is it so hard to define a monad? But I enjoyed parts of Scala 2 and later Rust. There are good ideas in FP that lead to programs that are easier to reason about and manage complexity. Languages are borrowing these good ideas and I'm happier for it, algebraic data types, pattern matching and destructuring, result/either, immutability, etc

When you program on a team choices like using procedural vs OOP vs FP aren't up to you since they impact others. You should be coding for your maintenance programmer, the person who will come behind you, need to quickly understand the code and make changes or bug fixes. The maintenance coder may be you, it might be a team mate or it might be someone yet to join the company.

Use your own time or projects foe exploring programming styles.

Interesting response from Mr Hegarty. I wonder if they would have gotten the same treatment by a US company?

Very cool. Although you confused me for a moment with the runit name. I was thinking the runit init daemon.

One of my college professors worked on long range ship gun munitions in the late 70s that were steerable through analog computers. He described the spinning of the round was used to drive an oil pump. Reservoirs around the circumference contained oil which could be moved from one side to another. As the round spun the oil was moved back and forth to change the center of mass, steering the round in flight. All controlled by a radio connection back to the ship. Very cool stuff.

I would never consider a work survey to be anonymous and treat it such that I would only say things I was willing to say directly.

I do 99% of my day job on a windows laptop connected to a Linux NoMachine session. It's not perfect but it works really well.

There are RDP implementations for Linux both client and server. x11rdp, remotedesktop,, etc.

Better than cast iron for me is enamled cast iron. It's not non-stick but it's extremely durable. Worth the price.

I discovered alacrity when I first learned rust and have stuck with it. It has good performance, despite possible exaggerations or regressions, good compatibility, a big enough scrollback, and real transparency. All my most important features YMMV

It's nice to see rust in an article not about rust.

It's more like the C programmer is a sushi master. They can make a delicious, beautifully crafted snack. But if the wrong ingredients are used you'll get very sick.

Excellent description of HKTs. As a rust programmer I sort of knew these things but this helped make it clearer.

One I've flipped on:

Functional programming has some really solid ideas.