sam_bristow

10 ms·

91.
by sam_bristow 2y ago
I assume that first picture is supposed to show it kicking or balancing on one leg. But but _looks_ like it's about to land on its arse.
92.
by sam_bristow 2y ago
I remember a discussion back when the first M1 chips came out where someone observed that it was quite likely that they had the Linux kernel running before they got XNU ported. The theory was that the hardware engineers would've probab
93.
by sam_bristow 2y ago
But Rocket Lab is based in New Zealand, and NZ isn't part of AUKUS... (disclosure: I work at Rocket Lab, but not on anything to donwith this.)
94.
by sam_bristow 2y ago
If you're going to use Makefiles as a top-level build wrapper you might be interested in self-documenting targets. https://marmelab.com/blog/2016/02/29/auto-documented-makefil...
95.
by sam_bristow 2y ago
I recently came across some UX work from the US Space Force that covers this type of Mission Contol software. I wonder how much overlap there is. https://www.astrouxds.com/
96.
Multicast and the Markets(signalsandthreads.com)
1 points by sam_bristow 3y ago|0 comments
97.
by sam_bristow 3y ago
I believe newer ESP32 chips are based on the Risc-V microarchitecture.
98.
by sam_bristow 3y ago
It's even more blurred with this vhip because it sound like it has both a 64-bit Cortex-A35 MPU and a 32-bit Cortex-M33 MCU core. As an aside, I'm pretty sure these chips were announced months ago despite what the article says.
99.
Astra Space to Be Taken Private(astra.com)
2 points by sam_bristow 3y ago|0 comments
100.
by sam_bristow 3y ago
You'd end up with a bunch of shady "data recovery" firms that may or may not be related to the ransomware crews.
101.
by sam_bristow 3y ago
Pretty sure I interviewed with this company about 10 years ago. Their software stack was all assembly on the embedded side. They were in the process of developing an new hardware with a soft-core processor because the original hardware was
102.
by sam_bristow 3y ago
Pretty sure you could identify anyone who grew up in New Zealand just by saying "Tutira mai nga iwi". You'd either get an almost immediate involuntary response from a kiwi or just confusion from anyone else.
103.
by sam_bristow 3y ago
https://without.boats/blog/notes-on-a-smaller-rust/ And the follow-up: https://without.boats/blog/revisiting-a-smaller-rust/
104.
by sam_bristow 3y ago
Joining a team with short tenure and high turnover is high risk. Often there are very good reasons noone sticks around and you'll just end up burned out.
105.
by sam_bristow 3y ago
CISO: Cyber Incident Sacrificial Offering
106.
RTO doesn't improve company value, but does make employees miserable: Study(arstechnica.com)
137 points by sam_bristow 3y ago|104 comments
107.
by sam_bristow 3y ago
Without a CLA or equivalent mechanism they would need to get the agreement of every contributor to change licences. Once a project gets large enough the sheer number of people involved usually makes this impossible
108.
by sam_bristow 3y ago
I think the opposite is actually a stratified repo with snapshots of the "new hotness" back through the history of the project. Each never _quite_ replaced by the next.
109.
by sam_bristow 3y ago
Newer ARM chips already have opcodes to speed up Javascript's handing of numbers. https://developer.arm.com/documentation/dui0801/h/A64-Floati...
110.
by sam_bristow 3y ago
Build systems like Bazel provide mechanisms for controlling access at the module-level. If you're disciplined about not just making everything "public" it can be really powerful. Bazel is a very big hammer though and might be
111.
by sam_bristow 3y ago
A tangentially related tool you can use to look at a repo over time is Git of Theseus[1]. It shows things like "what percentage of the code in this repo survives 6 months. [1] https://erikbern.com/2016/12/05&#x
112.
Python-based pinball software framework(missionpinball.org)
25 points by sam_bristow 3y ago|3 comments
113.
by sam_bristow 3y ago
My personal sweet-spot for writing technical documents these days is Asciidoctor with semantic line breaks [1]. There are some warts in the asciidoc syntax but it covers a lot more of the features I need for the types of documents I'm
114.
by sam_bristow 3y ago
The Altera (FPGA) acquisition could have made sense, but they never really followed through and now it's being spun off again.
115.
by sam_bristow 3y ago
It might be a myth, but I seem to remember the ASICs used to flicker older LED designs were often repurposed from audio greeting cards. The light was actually just Happy Birthday playing through an LED or bulb rather than a speaker.
116.
by sam_bristow 3y ago
The newer versions of the Wind River compiler is based on Clang under the hood. I wonder how the comparisons shake out vs with older versions which were more custom.
117.
by sam_bristow 3y ago
For a moment there I thought you were the first person to actually follow the new branding guide for the platform formerly known as Twitter. Of course, I should've known better.
118.
by sam_bristow 3y ago
Also, the commit adding the failing test isn't breaking anything, its demonstrating the already broken nature of the existing codebase.
119.
by sam_bristow 3y ago
$DAYJOB codebase is mostly C++ and Python with a bit of custom configuration DSL for code generation. Getting hermetic Python was pretty straight forward, hermetic C++ for cross-compilation to our target hardware was a bit more challenging
120.
by sam_bristow 3y ago
Some (not all) still applies. I just reworked the Bazel CI at $DAYJOB to simplify the entry points and just call `bazel build //...` And `bazel test //...` erc rather than a bunch of more specific targets. We've got

More ›