Me too! I've found that books with characters whose names begin with the same letter tend to cause me great confusion.
Names are just firstletter+garbage, which also means I can't recall any of the characters names when I've finished reading.
1,792 karma · joined April 11, 2009
Names are just firstletter+garbage, which also means I can't recall any of the characters names when I've finished reading.
So I try not to take offense if visitors aren't interested in the same things I am - the real challenge is whether they respect the differences in those things.
One of the fun "get away from math and into experience" bonus parts of the question was about how to deal with ambiguity - for example, if your elements are laid out like the 5 on a dice, and you focused on the middle element, which do you pick when you press left or right? What if you'd previously come from one of those elements?
The short version is that while many users can differentiate, it's more a problem of WHEN they differentiate - Chrome's entire design philosophy was around speed, and the omnibox was designed so that we had a simple destination that a user could focus on when they had decided to go somewhere else, but before they had decided WHERE they wanted to go to or HOW they were going to get there, and then make it so they wouldn't have to think about the HOW. If their search term autocompleted to a URL so they don't have to go through search, that was a win. This same philosophy was what drove putting the most visited pages on the New Tab Page (which was a blank page in most browsers at the time).
Some users plan out their actions before they take them, but I wanted to make everything as streamlined as possible so you could interact with Chrome as you thought about what you wanted, and not making you wait until after.
[1] I was the designer and occasional engineer, but the entire team takes the credit - everyone was behind the idea from before we even started work on Chrome, and many smart people deserve more credit than I do for how good it ended up being.
- all a PCB is, is a flat version of your hand-wired prototype - all those crazy lines are just the wires - there's no special hidden EE magic until later
- the schematic editor shows your intent
- the pcb layout editor shows where things go
- the hard part is actually just finding schematic and layout editor files for the components you're using - github search is great for this
- you will make lots of mistakes and need a few goes - everyone does, debugging is half the fun, don't be afraid
- online PCB houses make those mistakes cheap
Things I have made with little more than introductory-Arduino knowledge:
- A wearable bluetooth ring: https://twitter.com/gmurphy/status/1372368637332389888
- A hall-effect volume control knob for my PC: https://twitter.com/gmurphy/status/1179831446204121088
- A long range garage door opener: https://www.instagram.com/p/B11m1y5J3qc/
- And currently working on a keyboard: https://twitter.com/gmurphy/status/1443048243101777921
Also, the debugging step for me got orders of magnitude easier when I got a set of PCBite probes - just drop them on and they mostly stay in place. e.g: https://mobile.twitter.com/gmurphy/status/136575328654495744...
A few things happened after that:
- A startup took the open source code and put it up a day or so later and got a few million dollars in funding to do image sharing, which made me feel bad at the time, but they later disappeared so it's fine
- Larry Page got a bit annoyed that I didn't do it as a Google project, and Sundar/my boss had to explain that I was just a Chrome staff member who got a bit excited about a new API - both of them were correct
- I had to panic-build a content moderation system from the airport on my honeymoon in response to some unsavory content
- It eventually got to 3TB of stored data, which was fine until billing policy changes at my storage provider meant that my monthly costs would've gone from tens of dollars to hundreds or thousands of dollars
- My day job was more fulfilling, so after a few years I shut it down
[0] https://techcrunch.com/2010/11/22/dropmocks-chrome-designer/
It roughly felt equivalent to the 2014 Napa Quake (which was also a 6). For normally geologically-quiet Melbourne, however, this would be the strongest quake ever recorded.
In the "segue" case, it looks like the dictionary lists two pronounciations, one as 'seg', so it uses the lesser of the two. Not sure that pronounciation is valid, though.
Thanks to you and frosted-flakes, I pushed a fix for the back button issue - good catch, I appreciate it.
The next morning, looking for an excuse to not get out of bed, I actually followed through:
You then have to deal with weeks of constant spam from the NYT about the failed billing process, further cementing the my view that cancellation was the right thing.
In Australia, many people tend to stay in the same city for most of their lives, whereas America is full of people who go to high school in one state, university in another, and work in more - even those who stay in the same state often move cities (America has way more cities with way fewer people) they are constantly making new friends.
This means things like: in my 20s in Melbourne, parties tended to consist of friends who've known each other for a long time. In America, the host often didn't know everyone at the party because the invitation is open.
Canberra is actually a little more similar to America - most who live there came from somewhere else, so the social situation is much more open.
I feel so incredibly fortunate to have been old enough to see and understand the start of all of this, and later, to be a part of all of it.
It does vary by person/activity though - I can ride a rollercoaster with a unmoving body and blank face and be having the time of my life, but cannot watch cringe-worthy things on TV without physically seizing up. Others are the other way around.
My process is largely:
- mock it up with arduino boards
- mock it up on a breadboard with straight chips wired up like an Arduino but without all the stuff I don't need
- make a KiCad design that matches that
- make the PCBs, realize I made a few holes the wrong size, make more PCBs
- build, test, use
- plan to do it without the Arduino parts, but then give up after trying and failing to make Atmel Studio do anything
So I rigged up a bunch of stuff using some RFM95 Lora modules, relays, and a smattering of crypto, and now I can start my garage door opening from several blocks away. Now by the time my car gets there, it's ready for us to drive in.
It started as breadboard/feather mess, but has progressed over time as I've taught myself PCB design to make ever-smaller remotes. It also means I can make multiple remotes, and put them on each of my bags, bikes, cars etc.
You have a fixed timestep for good reason, which works great if you're displaying by doing interpolation (your display frames lag the physics and are 'catching up' to them), but in some cases where you want low latency in response to player input you might want extrapolation (your display frames are ahead of the physics engine).
I believe people typically do extrapolation by projecting forward any motion in a linear fashion, but it seems this would result in occasional weirdness like geometry intersection. One solution might be to run the physics engine at a fixed timestep for the 'real' changes, but let the graphics engine use the physics engine at a non-fixed timestep to do the extrapolation, where the results of that simulation are not taken into account for the fixed timestep frames.
Is that possible in Dyna-Kinematics, and/or am I talking nonsense? :)
https://shop.pocketchip.co/collections/frontpage/products/po...
https://twitter.com/gmurphy/status/891863458005655553
It made practicing forgiveness for loud airplane noises much easier :)
The TX is a Jumper T8SG + FrSky M9 gimbals and recased into a 3D printed case I made. Haven't finished it yet (waiting on a third iteration to be printed), so writeup when I'm done :)
* The control joy/mastery feeling you get from activities like car racing, riding a bike on technical terrain, playing a game, or flying a plane[1].
* A sufficient risk/reward profile; you risk smashing a $100 device, which is expensive enough to be interesting, but low enough not to be paralyzing
* The gearhead thrill of ordering, rebuilding, designing, and discovering new combinations of equipment
In my case, I want to optimize for quietness and unobtrusiveness, which means aiming for lightness, which is its own set of fun design problems - I'm currently down to 25 grams for a brushless FPV setup[2]. Now I'm on to redesigning the RC transmitter[3], since I want one with nice gimbals that takes up as little space in my bag as possible. The set of things you can do is endless.
[1] I hooked up an RC controller and went FPV with my home flightsim setup. It was fun, but there's a reason RC sticks are tiny - you need to move them around a lot more frequently and quickly than in a plane: https://twitter.com/gmurphy/status/832698732361551872