ahmedalsudani

I carry a knife specifically to stab people who pronounce my name that way (the Achmed way).

... yes, this is a joke.

You can use a managed switch to get this working if you have a router with too few ports.

I have several gl.inet routers running openwrt but they all have 2/3 ports total. I put a TL-SG108E in front of them and use that to tag ports.

This particular switch has an interface that is quite easy to reverse engineer, so I have written a script that allows me to easily move ports between VLANs without bothering with the unintuitive web UI.

This is one of my favourite things I've read on here, and it frames working on a team the way it should be framed!

Going to adopt every part of it. Thank you for sharing.

Yes, they are less secure. VMs can rely on HW features to ensure memory isolation.

The strawman is reducing his comment to "really just a debate on ideal hours and the post fails to make an argument there."

It's not about ideal hours at all. I'll post the entire comment here for anybody that might not have clicked through so you can actually decide what it's about.

Quoting Carmack:

I find these “shorter work weeks are just as effective” articles to be nonsense, at least for knowledge workers with some tactical discretion. I can imagine productivity at an assembly line job having a peak such that overworking grinds someone down to the point that they become a liability, but people that claim working nine hours in a day instead of eight gives no (or negative) additional benefit are either being disingenuous or just have terrible work habits. Even in menial jobs, it is sort of insulting – “Hey you, working three jobs to feed your family! Half of the time you are working is actually of negative value so you don’t deserve to be paid for it!”

If you only have seven good hours a day in you, does that mean the rest of the day that you spend with your family, reading, exercising at the gym, or whatever other virtuous activity you would be spending your time on, are all done poorly? No, it just means that focusing on a single thing for an extended period of time is challenging.

Whatever the grand strategy for success is, it gets broken down into lots of smaller tasks. When you hit a wall on one task, you could say “that’s it, I’m done for the day” and head home, or you could switch over to something else that has a different rhythm and get more accomplished. Even when you are clearly not at your peak, there is always plenty to do that doesn’t require your best, and it would actually be a waste to spend your best time on it. You can also “go to the gym” for your work by studying, exploring, and experimenting, spending more hours in service to the goal.

I think most people excited by these articles are confusing not being aligned with their job’s goals with questions of effectiveness. If you don’t want to work, and don’t really care about your work, less hours for the same pay sounds great! If you personally care about what you are doing, you don’t stop at 40 hours a week because you think it is optimal for the work, but rather because you are balancing it against something else that you find equally important. Which is fine.

Given two equally talented people, the one that pursues a goal obsessively, for well over 40 hours a week, is going to achieve more. They might be less happy and healthy, but I’m not even sure about that. Obsession can be rather fulfilling, although probably not across an entire lifetime.

This particular article does touch on a goal that isn’t usually explicitly stated: it would make the world “less unequal” if everyone was prevented from working longer hours. Yes, it would, but I am deeply appalled at the thought of trading away individual freedom of action and additional value in the world for that goal.

+1 csk is as good as it gets. Had him for my first CS class there and to the end of my time there, that class stood out both in terms of quality and enjoyment/engagement.

If you're at Waterloo and have the chance to be in Craig's class, jump at it.

This is a neat problem! Thank you for sharing!

It's common for the obvious cases and obvious constraints to be assumed.

Adding "distinct" would have made it clearer, but it was obvious that the author meant distinct from reading the title alone.

In medicine those kinds of arrangements exist, but they charge 30% (I forget if it's off the top or the bottom).

Yeah I'm specifically responding to the question above.

Some things like REST/HTML/XML are familiar enough that the initialism is as good as a dictionary word.

SOAP, on the other hand, I forget what that was. Hopefully it's not important.

One of the 5 stages of grief: bargaining :)

I have tried to use a couple of tools with better types on the job and on the "productive/industry" side of the spectrum. That consistently led to disappointment. It's been a while since I gave up on TS; what drove me away then was the typings I had to download and update and debug.

Nowadays I'm working on learning the purescript terrain for frontend development. In that world, the limitation is not the language but my ignorance. That feels better.

It's way better when you learn the words. Now I understand it's about frequencies and channels.

DFS to a software crowd will always expand to depth-first search. I was trying to figure out if that's what was being discussed here (with plenty of skepticism, admittedly) until reading GP.