BitsAndObjects

7 ms·

61.
by BitsAndObjects 7mo ago
"Sir", not "Mr." if you're going to be pedantic about titles ;) Edit: Oh and he has multiple honorary doctorates (at least 6!), so would be just as much "Dr." too!
62.
by BitsAndObjects 7mo ago
And, of course, the Go programming language.
63.
by BitsAndObjects 7mo ago
Further Reading for the curious: On specifically the relationship between Occam and Transputer architecture: http://people.cs.bris.ac.uk/~dave/transputer1984.pdf Wider reading: http://people.cs.bris.ac.uk&#x
64.
by BitsAndObjects 7mo ago
This post appears to have been hidden from the front page of HN?
65.
by BitsAndObjects 7mo ago
It’s also worth highlighting that the mathematical purity of the designs were also partly the problem with them. As a field, we’re still developing the maths of Effects and Effectful Algebras that are needed to make these systems both mathe
66.
by BitsAndObjects 7mo ago
“Inspired by” is an understatement of the century lol. David May and Sir Tony worked very closely together to enable the architecture to be as pure a runtime for CSP as you could get - at least in early versions of the architecture and acco
67.
by BitsAndObjects 7mo ago
Inmos’ Occam-based verification of their FPU in collaboration with researchers at Bristol and Oxford iirc? Citation: http://people.cs.bris.ac.uk/~dave/formalmethods.pdf David May was my PhD supervisor and always spoke
68.
by BitsAndObjects 7mo ago
This is the modern internet at work. People assume that a completely neutral statement that (to reword my original comment into a longer form) "here's a link to the same post from previously, because you might want to see it was t
69.
by BitsAndObjects 7mo ago
And what in my comment said anything about there being a problem??
70.
by BitsAndObjects 7mo ago
:thumbs-up:
71.
by BitsAndObjects 7mo ago
As I said, the contribution is good, it's the communication via this blog post that I don't entirely like. It could have been different. It could have acknowledged better ways of engaging with ffmpeg (that would've benefitted
72.
by BitsAndObjects 7mo ago
I've also had that experience of patching an OSS project internally, with the best intention of upstreaming externally-useful improvements in the future (when allowed). However, my interpretation of the article was that they did a lot
73.
by BitsAndObjects 7mo ago
Yes, they contributed to open source - this is a good thing. But personally, I took issue with the tone of the blog post, characterised by this opening framing: >For many years we had to rely on our own internally developed fork of FFmpe
74.
by BitsAndObjects 7mo ago
Same HN post from 6 days ago: https://news.ycombinator.com/item?id=47224355 [Edit: Why is anyone downvoting me linking to the previous post of this? What possible objection could you have to this particular comment?]
75.
by BitsAndObjects 7mo ago
P.s. In career terms, it's become a defining career area for now because there's basically no interesting work outside of AI-related stuff. That'll change in a few year's time. The industry can't sustain this level
76.
by BitsAndObjects 7mo ago
Picking up another tool and figuring out where it's useful to integrate it into my workflow. Much the same as when I picked up BeyondCompare, VSCode (replacing Visual Studio) and numerous other tools that have come (and some, since gon
77.
by BitsAndObjects 7mo ago
For a single machine, yeah Wireguard is fine. For my multi-user multi-machine many-service home lab, it’s quite helpful to have the extra small features that Headscale offers (and some it exposes in a more convenient way). Edit: Tailscale h
78.
by BitsAndObjects 7mo ago
Have a look at Headscale to avoid the cost of Tailscale for small home setups.
79.
by BitsAndObjects 7mo ago
(This affected TypeScript, .NET and other folk too)
80.
by BitsAndObjects 7mo ago
The Faster Python project would’ve got further if Microsoft hadn’t let the entire team go when they made large numbers of their programming languages teams redundant last year. All in the name of “AI”. Microsoft basically gave up on core co
81.
by BitsAndObjects 7mo ago
<3
82.
by BitsAndObjects 7mo ago
An expert would’ve at least taken a backup or checked existing backups weren’t going to be destroyed. Silently - without asking their manager - they just do defensive engineering as a good practice. Or they would’ve, at minimum, highlighted
83.
by BitsAndObjects 7mo ago
Sounds like something Claude could fix… /s
84.
by BitsAndObjects 7mo ago
True.. though an experienced engineer would also risk getting fired for doing all the other stuff the OP did too. Especially if they made minimal attempts to highlight consequences/outcomes to management in advance..
85.
by BitsAndObjects 7mo ago
Use Zulip. The migration out of Slack is actually quite easy and preserves all messages, files, etc. Even the user migration is straightforward, keeping Google or whoever as the identity provider if you prefer.
86.
by BitsAndObjects 7mo ago
That depends. As per my root comment, if you ignore a lot of the marketing of AI and view it as just a tool, then I agree with your point about it doing what you tell it but I still want the tool to help me avoid making mistakes (and I’d li
87.
by BitsAndObjects 7mo ago
"Anything that can go wrong, will go wrong. Including deleting production." I'm also waiting for the day we see a "Claude sold my production database on the darkweb" post haha.
88.
by BitsAndObjects 7mo ago
Yeah the videos hyping up Claude and other such AI tools don't help matters. For sure I've made mistakes. But I also don't write the following on my CV: "PhD-level expert in infrastructure and trained on the entire inter
89.
by BitsAndObjects 7mo ago
"To err is human; To really foul things up requires a computer." Extended with: "To really foul things up quickly, requires an AI tool."
90.
by BitsAndObjects 7mo ago
This is the purpose of sandbox environments.

More ›