(Unless the right time was last week, in which case you're out of luck.)
1,589 karma · joined December 12, 2011
I now work as a "consulting CTO" (see drtomallen.com/consulting) meaning I'll do anything from writing code, defining your architecture, hiring your team, through to persuading your board to raise investment for a new product line.
Cubescape (http://www.cubescape.com.au) is my side business delivering automated Escape Rooms. We've been running for over ten years now. I was the CTO and most of the time the only software developer. We own and operate The Curium Experience, which is rapidly gaining a reputation as Australia's best escape room. We won the only TERPECA top-room award in the southern hemisphere in 2024.
Best contact is email: tom@jugglethis.net
(Unless the right time was last week, in which case you're out of luck.)
If any of those products grows a more user friendly model for _thinking_ about how to do things (Flow is arguably the closest) they could revolutionise how things are done here. PowerBI has enormous power to express data as stories, but the technical hurdles are still high. It's not _harder_ than excel, but there's a competency cliff.
Shannon’s Juggling Theorem
(F+D)H=(V+D)N
F is the time a ball spends in the air (Flight)
D is the time a ball spends in a hand (Dwell), or equivalently, the time a hand spends with a ball in it
V is the time a hand spends empty (Vacant)
N is the number of balls
H is the number of hands
(http://lkozma.net/blog/shannons-juggling-theorem/ for more details)
My program spawns and runs in the main thread. It calls the main function. If it want it to run forever, I'll stick a while(1) loop in that function.
Now I want to have a particular thing go off and do some work in parallel with that main loop, and when it's done, I want the next iteration of the main loop to pick up on that fact.
Not once have I encountered a sane API for that use-case as easily expressed as those sentences of prose above.
That said, a better way to defuse the question without lying is to say something like "My former employers consider salary data confidential as I'm sure you do too, but my expected salary for this role is [true_target * math.randrange(1.1, 1.4)]."
I found this book in a library's junk pile, evidently unread. It has one of those bad 80s covers that suggest it'll be terrible, but to my great surprise, it's great! It's 80 or so one page missives/dictums/edicts that'll take barely half an hour to read through - I re-read it every time I have a job interview coming up or a some kind of major life choice. The author's tone is abrasively direct; this is how it is, not how it should be. And the advice isn't just for wannabe CEOs, it's accessible and attainable for everyone.
Source: I played a lot of Pharaoh as a kid.
And yet, then I think why would I bother carrying a laptop-minus-cpu plus a phone with desktop ability when I could just do what I currently do and carry a phone and a full laptop? I can see this brings a bit of flexibility, and my files/config would always be on my person, etc. But we have global and close-enough-to ubiquitous internet now - isn't that sufficient or even better?
I guess I just don't get the use case. Or maybe I get the use case(s) but not the business case.
I do have an embedded systems background, but the technology for this application is a step higher-level than that. It's 99% Python3 running on a network of Raspberry Pis.
I should probably expand on that somewhat tongue in cheek answer. It's a pretty cynical response, but there's truth in it. Following and/or playing sports provides people with a tribe and a set of shared values and camaraderie. Much like religion, I've never felt the need for this, but there's certainly a very large set of people who do.
1) http://americanhistory.si.edu/collections/search/object/nmah... 2) http://www.gettyimages.com.au/detail/news-photo/the-blue-tea... 3) https://www.youtube.com/watch?v=V1bkhviWgSg
By comparison, after a year of learning to ride a motorbike I barely make it to work each day without shitting myself.
D* can be pathologically slower than repeated A* searches under such conditions.
The pre-computation JPS(+) does is cheating because it's essentially providing a quicker-to-evaluate heuristic than A* gets to use.
So yes, I agree - the title is misleading! However, it's still a pretty cool efficiency for situations where it's applicable.