Question, do you "build LEGO" as in "make what's on the box it came in", or do you use LEGO to build things yourself and not following instructions?
(I am old, but as a kid, I remember building what the kit was supposed to build once or _maybe_ twice, but using the parts from the kit and various other kits I had to make things purely out of my head pretty mush all the time. I _think_ that's not how people "play with LEGO" these days?)
Both, I enjoy the process of building, so following instructions. But then it's done and boring. I.e. LEGO supercars sets are nice, they're so nice until you marriage chassis with drivetrain - you can play with all the gears and see them, after the marriage it's just boring. So now I'm working more towards reusing parts and building things of my own.
Edit: LEGO Architecture Set (not sure if they still make it) is super nice for building random stuff - it's a set of pure white bricks, super fun.
Alternatively, ensuring you have enough slack in the schedule is, at least for some tech leads and project managers, an essential tool to enable meeting deadlines.
(So, I suppose using "slack" in a positive sense by project management, while probably still being considered a pejorative thing by non technical management or beancounters...)
yep, having some slack is the only way for someone / something to able to respond to uncertainty. technically having firefighter on standby and policemen on patrol are a form of slacking, and we (should) have no problem with that.
> Am I supposed to be having issues with TCP connections right now? (I'm not.)
If my skim read of the slop post is correct, you'll only have issues on that machine if it hasn't spent any of that time asleep. (I have one Macbook that never sleeps, and I'm pretty sure it hit this bug a week or two back.)
> very few users are likely to be affected by this
I have a reasonably strong suspicion that I experienced this a week or two back, on a MacBook that doesn't go into sleep automatically and quite likely had 50-ish days of uptime.
It had all the symptoms described - tcp connections not working while I could still ping everywhere just fine, and all the other devices on the same network were fine. Switching WiFi networks and plugging in to ethernet didn't help. A reboot "fixed" it.
Yep, I concur: this explains a bizarre behavior I’ve noted in my Mac laptops for ages now. I have a tendency to just suspend them without rebooting for ages, especially the work one that doesn’t leave my office as frequently. Periodically, I’d come in to find the system bizarrely frozen just as they describe: TCP stack blocked up, but everything else on it behaving normally. (Well, mostly: some apps would block starting and bounce eternally, but I suspect that’s because they’re trying to make a network call while starting up and it’s blocking.) The only fix was a reboot.
It’s not a disaster, but very annoying. At least now I can just schedule a reboot every 30 days at minimum to keep things running.
> Still, I had assumed there might be some kind of master key that would handle this automatically during a password reset.
This assumption, by a clearly technical person, is a fundamental problem that keeps "the rest of the world" locked in to centralised services where that is true, and where that master key can be used against them by law enforcement, fascist regimes, and surveillance capitalists.
Author of the blogpost here:
Firstly didnt expect anyone would read my blog post (Atleast not this soon) let alone someone posting a link on hackernews.
Yeah I realized while i was writing that if somehow that (my assumption about master key) did happen then it would be bad press and completely destroy Apples reputation for a privacy first. At the same time for an usecase like mine where i want my work isolated from personal it is weird that without proper way to get the data back they would allow this to happen. I mean if i really didnt remember my password then my keychain data would have been gone without which lot of work related info would have been hard to recover.
> I mean if i really didnt remember my password then my keychain data would have been gone without which lot of work related info would have been hard to recover.
It is reasonable to expect that having a password it is used to protect the data. A passwordless account does not protect or encrypt data.
Windows by comparison does the same for credential storage. If you forget account password and go your way to reset password, you will lose access to existing encrypted credential store (a keychain).
It was sent to Mars with a plan for 5 flights and a total of 7 or 8 minutes flight time. It ended up flying for over 2 hours in 72 seperate flights before it damaged itself with a bad landing. Not quite the "this thing is still doing science almost 50 years later" that Voyager can claim, but impressively engineered so it lasted way beyond it's initial mission plan.
Note that it is wrong to think that David was at a disadvantage. I know that is not how the story is taught today, but slingshot troops of that age we the snipers of their age: very deadly (not at the range of a modern sniper, but...).
If the fight between them was started at some distance, the David should have been the expected winner by pretty much everyone on the field. Think "bright a club to a gun fight" sort of vibes.
David had a sling, not a slingshot. They are very different tools. slings need more skill, but are easy for a shepard to learn. (I suspect more powerful as well but I'm not an expert)
(I am old, but as a kid, I remember building what the kit was supposed to build once or _maybe_ twice, but using the parts from the kit and various other kits I had to make things purely out of my head pretty mush all the time. I _think_ that's not how people "play with LEGO" these days?)
reply