8,045 karma · joined December 6, 2013
All opinions my own.
@athenot on Twitter
"Some of you might die, but that's a sacrifice I'm willing to make."
I'm all for puns, but at some point we need to stop the association between hydrogen and explosiveness. Absent the perfect mix of H₂ and O₂, Hydrogen burns like most other fuels.
(Just noticed that Unicode U+3379 is the DM CUBED glyph but doesn't render on the mac, unlike ㎣, ㎤, ㎦)
Yes you have to start with what people need and go from there. However, you can also start from what a niche of people need and go from there.
Honestly I think OpenDoc was way too ahead of its time to be groked by mainstream users. Currently we have various workbook online apps (like Observable) that are similar in spirit and super useful to those who know how to leverage them, but haven't yet crossed into the mainstream.
The result being that the immense majority of the food available to me is now "ok but not fantastic". I still take pride in being able to enjoy (almost) any food no matter how humble. But none bring me joy the way a rare fine dining experience will. And since I'm in no position to indulge on those on a regular basis, I'm never using food as a source of comfort and satisfaction.
TL;DR: appreciate and cultivate rarity (but try not being a snob about it)
The catch is than in many positions, one needs to blend these 2 modes of operation. Some collaboration, some deep work. Unless there's support throughout the organization, what ends up suffering is the deep work.
This has been my experience as well.
I think that's why "medium powered" languages such as Python and Java tend to get the widest adoption over time. They are less expressive but also have fewer gotchas, and in a team of 100s or 1000s of good-but-not-stellar developers who come and go, they end up being the least painful for the organization.
Walking also allows you to better appreciate the environment, fauna, flora and scenery, eg. on a hike. Sure you can take some of that in as an ultra-cross-trail-marathon runner but it's less contemplative.
It's whatever you are most comfortable in, and can move the quickest.
It's the stack where you don't have to re-learn how to do things you know are possible.
So with that in mind, it's probably not the latest and greatest technology (except if you happen to have been living and breathing it for the past few years). It's probably got some warts that you don't like but for which you are also very competent at overcoming.
If you are leading a team and need to decide that for them, try to find out which stack each member has gotten the most done in (in current or previous job), and average it across the team. It might be helpful to set expectation that this is not the most glorious technological project of their lives but that the goal is a rapid developement project with the goal to replace parts with something more robust once they get validated on the product/user side.
Hopefully Microsoft will eventually unify these apis and configurations into something coherent.
Not just for nostalgic reasons but also as a parallel with how the open web these days is being co-opted by Google / Facebook.
Yes, we need to move away from SSN as a { unique-ID + secret } combo. But that's a non-trivial task.
I'm starting to think we need something like PCI for SSN: want to use a SSN? Bam! You are now subject to intense audits that will evaluate all your data practices (and for which you will be billed). Orrrr… use a third-party vendor and never touch this data.
That being said, it's still not a perfect option because Credit Card numbers can be rotated whereas SSN seems to be engraved in stone. Still following the Credit Card analogy, having multiple numbers would greatly help. Just the same as you don't go around (anymore) showing everybody your bank routing information and have multiple cards for various purposes, have multiple identity numbers:
- tax ID number
- driver's license number
- passport number
- medical record number (yes, MRNs are a thing, just prefix it with the org ID)
- medicare number
- actual social security number for only social security (and at this point, a new one + rebranding is in order)
- credit-worthiness number
- etc.
Of course, that brings its own set of complexity which should be carefully weighed against requirements.
Environment variables are still one of the simplest—and yes, most deterministic ways—to alter behavior of a program.
Perhaps someone should ring the doorbell so it flows again…
Cisco is hiring an Incident Commander for Webex. That's essentially a Cloud Engineer who's focused on incidents, with a side of development for tooling & automation. Location is flexible since most of us were remote even before the pandemic (we dogfood our service).
Want to work in a large-scale cloud offering and get to interact with every moving piece?
Interested in a dynamic environment with great work/life balance & benefits?
SRE and generalist at heart?
Check it out and join our team: https://jobs.cisco.com/jobs/IsAJob?projectId=1317137
Note: US Citizenship required for this particular position.
News broadcast is a better analogy but still not as addictive as something that continually reaches out to you throughout the day.
Yes. It's also a good choice for horizontal scaling, but only if the other DBs won't do.
Another project involved some beverage being poured into a wine glass… it was actually constructed horizontally on a pane of transparent glass, with a half wine glass constructed over it. Truly amazing.
- get ID validated & ability to vote
- get an initialized smart card
- insert in polling machine, fill out stuff
- submit, get printout from printer
- scan printout into a machine
- return smart card
At the polling places I was at (we had a runoff), the staff + signage was emphasizing to check results on printout.
The printing and the scanning felt terribly wasteful but as it turned out, it became a precious way to audit. The bonus is that the printout is normalized, not some person's handwriting that could be subject to misinterpretation.