> When worn, people could see Morse code-like signals flashed from an infrared LED and tell what direction infrared light came from.
So wearers aren't really resolving an image in infrared, although it does appear to at least be a bit directional.
187 karma · joined October 2, 2016
> When worn, people could see Morse code-like signals flashed from an infrared LED and tell what direction infrared light came from.
So wearers aren't really resolving an image in infrared, although it does appear to at least be a bit directional.
So I was naturally extremely excited for KSP2, but all-along I had a strong feeling this would happen. What's sad to see is that it's not just a second-system effect of being too ambitious, which was what I was assuming would cause issues, but an even more pathetic failure than that.
The joy I get from games has a really wide variance, and barely any relationship to the actual amount of money I spend on the game. I'd pay $1000 for a truly good KSP2, yet all the games that would actually _let_ me spend $1000 are shallow skins over gambling.
It _is_ a pain to self-host, but unlike claims elsewhere in this thread I do also self-host the API and database.
After some articles recently about this on AstralCodexTen I'm reading 'The Mind Illuminated" to try and decide for myself if such "unfalsifiable internal states" exist.
https://www.idownloadblog.com/2018/12/19/create-smart-playli...
I’m an insane person so I listen to all my liked songs on shuffle and ride the wave of tonal inconsistency, so this feature is very important to me…
When kids ask about undergrad I say, 'Do a degree called "software engineering" if there is one, otherwise "computer science" is the same thing'. Some unis just have one general coding degree and pick the name randomly out of those two, some have both with either an industry or research focus respectively.
eg in my CS undergrad degree I got some theoretical & research stuff (simulations and queuing models, computer vision being two of the research focus areas), but also some good old Operating Systems, compilers, databases, practical programming, software engineering, etc. Vocational stuff; has been very useful!
Masters students (back then at my uni, and seemingly now too) mostly wrote essays and had the option of doing very, very little coding at all.
I've been hiring engineers for a few years, and I've come to associate a CS/IT Masters + unrelated undergrad with bad candidates and generally use it to filter _out_ candidates (unless something else on the resume catches my eye). Conversely someone with a science degree and a bit of experience (or some decent personal projects for fresh career-switchers) is a much better sign.
My experience (read: anecdata, opinion, bias) is that the IT/CS masters candidates I've interviewed have switched for money and because of failure-to-thrive in their original industry, and have no care or passion for software, and have done poorly on interviews. The non-CS-undergrads-but-no-masters candidates are just the normal spectrum, with a higher variance (some with 0 skills but much hope, some with really interesting backgrounds and wide-ranging interests like how you sound).
Data disclaimer: I'm only at ~500 total lifetime interviews/10 years experience so far, I'm in Australia, I have no recorded numbers or hard data just "feelings" and "intuition".
The cops in Oz are truly awful! There was a recent scandal where cops were strip-searching teenage girls just for fun. Cops there will also spend more time fining people on bicycles that don't have a bell, than they would in any important crimes.
It differs a bit by state. Apparently NSW and Vic have it worst, although QLD is right up there. Of course in the nation's capital, Canberra, they have the soft ones.
Agree with you that I never got it working consistently in Linux. Just getting normal BT headphones to use A2DP rather than HSP was always a bit tricky. I've not dared try my gamer headphones...
In the few years since I left; I worked as a solutions architect managing a team, a team lead, a remote dev, and now in a startup. Front-end, back-end, flip-side, all the ends. So I've been deliberately trying different angles of my career to see what suits.
I'd describe this process as grueling, ("challenging" is too friendly). I honestly think I would have been happier staying at Google, farting around, and being social. I agree with a lot of the comments here. However it's a catch-22, because the me that exists now wouldn't choose to go back and overall I think this has been good for me – and not just because of the, er, _character building_ aspect of it.
If you stay at Google, make the most of it by progressing deliberately in your social life. If I'd've stayed, I could have comfortably raised some kids with my wife by now - but that's still on the todo list.
If you leave, just jump right in. I didn't study anything, I just picked it up as I went along. If you were able to follow Steve Yegge's advice and Get That Job At Google, then I'm sure you're a smart cookie and can fake it til you make it.
Basically I'm saying you can be happy either way. If you leave, know what you're getting yourself into. If you stay, don't waste this time but use it on yourself.
I like to leave Todoist open in a permanent/pinned tab. Often, when I open that tab, the pre-filled date for "today" in the new-task-entry area is stale, yesterday or a few days ago (right now it's 5th September). I assume because that's populated on page load and never updated?
What will happen is that I enter a task without setting a date, meaning I want it for today. It then saves that task as ONE YEAR IN THE FUTURE minus one day. The task then gets forgotten and not done :(
Also, I cannot get Siri to understand "todoist". I've tried every pronounciation, even "2-doyst"!
I really love Todoist, but that one bug hits me so often!
I don't know much about ML, but would it be possible to use some kind of attention model to iteratively construct the final colouring? The memory limit of the GPU would then limit the attention region size, but not the maximum image size. Talkin' outta my rear here, though.