twistedpair

I've got that house, spouse, kid stuff. It's awesome, but also an anchor that limits what you can do, where you can go, etc. You don't have that at the moment, so go be spontaneous. I don't travel any more, but you can. I don't do silly, dumb, or risky stuff any more, but you can.

You sound like a mid career dev, you should be well situated. OK 401K, pay, 'benes, etc. About wealth, they say "you can't take it with you." Spend some of it living it up now while you're well situated.

Historically it was common advice to avoid elaborate code formatting, as keeping up such formatting by hand was tedious, time consuming, and inconsistent, compared to the value add.

Given near all code (let's say for large projects) is authored with IDEs, elaborate formats can be applied consistently and automatically, at little or no cognitive or typing cost.

To me the question is then if such formatting can increase the legibility of the code. The grid of static variable declarations in [2] is nice, but I wonder if sorting the variable lexicographically would make it easier to read/find a var by name?

Not sure how splitting method signature names onto a second line helps, though.

To clarify, race is a construct too often abused to implicate stratifications of groups of people. "Races" don't naturally exist, rather only a continuum of ethnological and physical differences across the rainbow of the human genome [0].

As it's used today, race can be very divisive and polarizing. While I'm white, I've toured and been deeply moved by the Apartheid museum in Capetown and driven past the Townships that show how severe and pervasive the only recently struct down laws that ensconced the white elite in private neighborhoods while relegating everyone else to shanty towns were, and still are years after said laws were struck down.

While collecting racial data certainly plays a role in correcting for the still evident scars of past wrongs (and avoids denying the past), it strikes me as also reinforcing the existence of such racial constructs. I can only imagine what it feels like to be a teen in a minority group checking the box that they are that group on forms for every tooth filling, credit card application, warranty card, standardized test, and survey they take.

I sincerely desire my future grandchildren can see a title like this article and think it's a discussion of footrace algorithms, that we can live in a post racial society at some point. We certainly are not there yet. There is much inequality to resolve and too many latent scars to heal. Will we make it in my lifetime? That's on all of us to affect.

[0] https://sitn.hms.harvard.edu/flash/2017/science-genetics-res...

Here's an example [0].

[0] https://aws.amazon.com/blogs/messaging-and-targeting/forward...

If you've got a lot of domains, but need the `admin@<domain>.<tld>` registration emails to work correctly, you can route them all through SES + Lambda for nothing, rather than having to add hosting to all the domains. Impl works well for some use cases.

Perhaps the USB Chainsaw [0] will eventually be a reality?

DeWalt, are you listening?

[0] https://www.thisiswhyimbroke.com/usb-powered-chainsaw/

Funny, I find the opposite. Maybe it's a desire to feel efficient, but if asked "how long did that take you", I feel like saying ⅔N hours rather than N hours. Then again, I'm a full time employee, so I'm not billing by the hour, like lawyers that get $100 for responding to your email.

If I provided users with an IPv6 block to allowlist for my apps, I think most IT directors' heads would explode, but _everything_ works with 32 bit CIDR ranges.

I certainly support it, but I'm not sure we'll see an end to NAT for some time, even with an IPv6 option.

AWS SES Inbound + a Lambda function to drop the mail where you want it (e.g. a topic, an S3 bucket, or forward it to somewhere else). Overall monthly cost is practically $0.

Will we ever see a Tor Incognito tab in Chrome?

Computers have successfully been used to time 5K and marathons for decades.

Race is what you define it to be, such as in this ambiguous title. Whether we should have a concept of "race" is another matter.

Similar. Worked on a project where there were 50+ contractors to automate simple biz workflows. Run that for a few years @ their rates and you'll see how much enterprises spend on relatively simple software projects.

Why isn't there a browser setting that passes a standard header to declare what types of cookies you consent to? You set it up _once_ for your browser and you're done.

mabl | Boston, MA | Software Engineer | ONSITE/REMOTE | https://mabl.com/careers

We need your help to put our $40MM series C raise [0] to work and keep scaling up. We’re bring AI and cloud scale to software testing at mabl. We provide automatic, self healing testing of web applications using advanced ML and AI techniques to replace the tedious and fragile UI testing of yore.

We’re a 100% serverless operation built on Google Cloud Platform that rapidly develops and deploys features on a CI/CD model. Four years in, we’re a recognized industry player and growing our engineering ranks to keep building out our platform.

Our open positions:

- Software Engineer - Support - DevOps Coop - Software Quality Engineer - Product Manager - Inside Sales Engineer

Our stack is built with modern Java 11, TypeScript, and some Bash glue

Drop me (an engineer), any questions joe at-symbol mabl.com, and checkout our careers site [1]. We can’t wait to work with you.

[0] https://venturebeat.com/2021/11/18/mabl-aims-to-automate-sof... [1] https://www.mabl.com/join-the-team#jobs

A similar incident happened to Qatar Airways Flight 778 (another 777-300ER), from Miami in 2015 [1].

Incorrect runway lineup led to the plane only getting airborne after the end of the runway, after smashing through the ILS antennae. They then continued onto Qatar (13.5 hours away), with bits of antenna embedded in the tail.

[1] https://avherald.com/h?article=48c78b3a

The Germanwings Flight 9525 tragedy [1] was effectuated by the suicidal pilot inputting an auto-pilot target altitude of 100ft, while flying over high mountains. The plane dutifully flew into the mountains, murdering 150 people.

While there are airports with elevations lower than 0ft, this is a good design question to ask. In general, it's assumed the pilots will do the right thing to save the day, if needed.

[1] https://en.wikipedia.org/wiki/Germanwings_Flight_9525

<3 to Simon Hradecky for all his hard work over the years. Such a great AV safety resource.

Biggest jet engines ever made, at tree top level, running @ TOGA power. Yeah, that woke up the neighbors.

Too bad this was at night. Would have been some wild Nest cam footage during the day.

For reference, the max allowed GA airspeed by the FAA under 10,000 ft (3km) altitude is 250 knots. Doing so at 175 feet is wild.

It takes a while (think like 10min+) to reboot these planes. Checkout "cold start 777" on YouTube [1].

There are a ton of computers (FADECs for engines, fuel management computers, FMS (flight management), PFC (flight computers), weight and balance computers... and much more). All of these have state. Which way is up for the gyros. Proper direction for the compasses. Proper location on Earth for the navigation system... etc. Basically, a 777 has the mother of all POST sequences, so frames in line operation are rarely restarted, for operational efficiency.

Reminds me of the navigation systems for some rockets (Atlas, IIRC), that require 24 hrs sitting level on the pad to fully initialize their starting ground state (super precise gyros). This ain't like restarting your internet connected juicer.

[1] https://www.youtube.com/watch?v=z6UCD0o0NCU

Varig Flight 254 was another similar case [1].

Bad FMC data entry during preflight caused pilots to fly west, rather than east, until they were too low on fuel and crashed into the Amazon rainforest. Sun was setting, so cardinal direction was obvious, leading some passengers to ask flight attendants why they were flying the wrong direction, but they were brushed off.

[1]https://en.wikipedia.org/wiki/Varig_Flight_254

IIRC, iOS 8 cut the BTLE bitrate in half for using Apple APIs. I worked in the fitness tracker industry at the time, and this is why most major vendors used their own stack, rather than Apple's.

My no-name Amazon earpods knock offs work just fine, every time, for running. Not sure what fancy features they lack, but they "just work", better than my Bose QC35.

I'd push back on that norm.

I listened to a vendor pitch for a product that would need access to my cloud assets. They wanted me to export auth keys as strings and hand them over, with super high access rights. I laughed and pointed out OIDC, Workload Identity Federation, cross account user identities... etc as more secure methods that didn't require handing over any secrets.

Multi-billion dollar vendor; their engineer just gave me a blank stare as if the notion was completely novel. It's not. None of the products/integrations I build require a customer to share their cloud creds to work w/ their cloud assets.

2020 is calling...

L2 is very far from earth, well beyond the Moon. The Shuttle could never leave Low Earth Orbit, so it's a non-factor in repair missions once JWST is on station.

Rockets can easily accelerate with enough force to kill a human (cargo flights and unmanned flights use different launch profiles for this reason).

The less Gs you need to design a component for, the lighter/simpler it can be, so why unfurl early and add that extra mass and complexity to the design?

> Unlike say, the Apollo program, which had a guaranteed successful outcome?

Apollo was wildly dangerous. Apollo 1 killed the whole crew. The contemporary calculated failure odds for a Saturn V launch were 1/8. Compare that to the current Dragon 2 projected LOC risk of 1/276 [1].

[1] https://en.wikipedia.org/wiki/Crew_Dragon_Demo-2#:~:text=NAS....

They calculated that. Building a second JWST would have added 10% to the budget, but the budget committee nixed that.

YOLO (you only launch once).

While a farm tractor might have a factor of safety of 10, spacecraft are usually closer to 1.3, due to mass and efficiency constraints.

Space is hard.

"Can't" and "won't" are different things.

See discussions from the last outage about the VP signoff needed to admit, I mean announce, an outage.