earlz
Joined 14 years ago
Joined 14 years ago
I think she was chewing the nicotine gum a few times a day, but I'd still be careful about it.. iirc the reason she did it was she wanted gum and the only gum her parents had regularly was nicotine gum and she was like 14 at the time
edit: note I say "easy", but its not a short process.. If you try to go immediately from 48mg to 3mg you won't have a good time. It takes months for each step down
I have 2 kids, so have to have some structure to my sleep schedule. Left to my own devices, my natural bed time is 3-4am and I'm awake at 11am-12pm. With kids during school (in summer they sleep in too) it's a bit more reasonable though probably less healthy. Asleep by 1 or 2am and wake up at 8am. They're 9yo and 6yo and the oldest is responsible for getting the younger up if she doesn't wake up with the alarm. They're both 90% ready by the time I wake up (they prefer to wake up at 7am or even 6:30am to have some play and tv time before school). This includes getting themselves dressed, hair and teeth, and the picky youngest packing her own lunch. Their school starts at 8:45am and I'm typically out the door at 8:30am and back by 9am.
I don't really start working until 10am most days, but I'll do some passive stuff like read emails and industry news type stuff while having coffee. At 10am I'm getting started, at 11am on a good day I'm hitting a stride. Typically not doing my best coding work until at least 2pm though after lunch. Depending on how in the zone I am and what I'm doing, I work until 5:30pm to 7pm. I have the benefit of being remote and setting my own hours though, so it's definitely a blessing I know many people aren't fortunate to have. Have dinner with the family after I stop working, and then just relax with dumb activities (TV, social media) and of course bonding stuff with family, until the kids go to bed at 9pm. When they go to sleep I sometimes work for a couple more hours (coordinating with 12 hour different timezone is fun), but more usually relax with peace and quiet playing games, messing around with interesting research (both hobbies and work), or just dumbly watching TV, or do some hobbies (analog photography/darkroom printing)
I sacrifice sleep more than I should, and typically will have a 10 minute power nap after I'm done working.. But honestly, as long as I'm getting 6-7 hours of sleep, I feel just as well as when I'm getting 8 or 9. When I get less than 6 though I definitely regret it the next day. And I don't mean just sleeping in on weekends. I had about 2 weeks this summer where I had no kids, no wife, and basically nothing guiding my sleep schedule. I'd tried naturally sleeping for a week with no alarm and realized I felt more tired and it was consuming a lot of time. I was waking up at 11 or 12. So I started setting my alarm to a more reasonable 10am and was in bed by 3 or 4am, and always felt well rested after I got out of bed.
Some people can not "relax" and enjoy mornings. My goal with mornings is to get that phase of day over with so I can work and then get to a free evening. When I'm jetlagged it's pretty interesting becoming a forced morning person, but it's always proven to me that having 3 hours of free time in the evening is so much more valuable to me than 3 hours of free time in the morning.
Also completely unknown how you'd do it, but giving any kind of data for pushing the B/W films would be really interesting too
As someone currently writing a (subset of an) x86 VM, I feel this pain entirely too much. My subset greatly simplifies things by not using segment registers and getting to (mostly) not have to implement the 16bit version of ModR/M.
The biggest problem with x86 is the sheer number of ways to do addressing within a single opcode using a Mod R/M operand. For instance, all of these lines of assembly can use the same primary opcode:
push eax
push [eax]
push [1000]
push [1000 + eax]
push [0x11 + (eax * 2 + ecx)]
push [0x11223344 + (eax * 8 + ecx)]
push [(eax * 8 + ecx) - 10]
If not for the Mod R/M and SIB operands, x86 would be a static-width instruction setI'm building an interpreter that goes the way of decoding to build a pipeline (really a "basic block") and then to execute the entire pipeline with minimal branching across execution. I'm less afraid of excessive cache use than the unpredictable indirect branch problem. The hope is that building a pipeline and executing it with a branchless unrolled loop will allow me to avoid that problem, while also greatly simplifying the implementation of each opcode where the actual logic just receives a set of operands it can get or set.
I think the SEC is interested in the conditions around their ICO, the misleading tactics, and the aftermath of it, more than the fact that they did an ICO
I actually learned C by writing an OS from ages 16 to 18. I don't know if I'd recommend it to everyone, but it is surprisingly accessible if you limit scope. The real hard parts are dealing with complicated hardware. If you care about the basics like keyboard, mouse, display, flat memory, no threads, then its incredibly easy in 16bit C for x86. 32bit C (i386) is also easy, but does require a bit more setup etc.
It is incredibly educational learning how to write your own libc and having to manage toolchains etc. You very quickly learn the exact boundaries of what is computer controlled and what is toolchain controlled, and of course what is controlled by your own code.
And yes, I had a similar experience to you re: emulators. Tried making a simple 8086 computer emulator. CPU instructions are really easy and really the part I enjoyed. Emulating the hardware and all the machine protocols gets very difficult and complicated very quickly. I ended up, after a few months of that, rescoping the project to only be an 8086 CPU emulator, which was one of the few projects of my youth I actually completed.
Anyway, I kept it and ended up digging it up in 2010 from a box of old stuff to crack it open and make it an IR camera. Something went wrong, so now it's fixed focus at ~3ft, and with a few bits of dust permanently on the sensor... but, it worked! The focus issue prevents it from being very useful, but it's really cool as it is VERY sensitive to both IR and UV light. Using a very deep 920nm IR filter with it, I have to decrease exposure on a bright day or it's blown out... and it can very easily see UV patterns on things inside when the sun is out. I have a faded shirt that looks just black, but with the camera it can see the original lettering etc as if it were new... but also it looks magenta rather than black. Even with tungsten lights, the IR sensitivity is stronger than normal light and can end up with some crazy pictures that have "color" but not true color.
Here's some example pictures:
* https://i.imgur.com/5ZKmgFm.jpg reading text on a letter through an opaque black shirt (UV/IR illuminated through windows) * https://i.imgur.com/IYzdhXP.jpg an out of focus look out of my house on a summer day (notice red leaves, brown grass) * https://i.imgur.com/STSPbq5.jpg IR "enhanced" portrait in a car. Her hair is deep red and the coat she's wearing is black and white only. * https://i.imgur.com/7gSzCTT.jpg looking partially through a deep IR filter
The only good UV-only photos I have tend to be flash pictures. The built in xenon flash appears to output enough UV that it will burn through IR filters. It definitely appears to be UV though because of different colors used and the way certain things will fluoresce
I've done some film B/W IR photography but with film it's so temperamental and I've never gotten good IR-only (though a deep red filter can be nice) pictures. There is Aerochrome, which is getting harder and harder to find for color IR pictures on film, but even it is hard to predict (though requires less filtration) and very expensive these days.
My comment was an early disclosure before I fully understood how sensitive the details were. Even without going into detail or providing any code it was very irresponsible of me to off hand just mention that possibility. It didn't click how sensitive things were until a bitcoin core dev confirmed it. Sorry anyone who sees this. I merely reported the exploit, David Jaenson is our genius security researcher that definitely should deserve all credit.