HNHacker News
TopNewBestAskShowJobs

the-alt-one

53 karma · joined November 30, 2021

submissionscomments
the-alt-one··on AirPods don't “just work”
Good to hear the gripes with AirPods are identical to my $80 earpods, nothing missed out on in other words :-).

Edit: I have a pair of JBL LIVE300TWS. They're good!

the-alt-one··on Why I use a debugger
>The goal of most IDEs seems to be first help with a debugger / executing code/tests, second help with writing code, and only thirdly help with reading code. The older I get, the more those priorities seem inverted to me.

I'd be interested in developing more tools based on abstract interpretation and symbolic execution of the programs themselves and generally be able to query your tools more.

For example, let's say that you find a program state with the debugger which is invalid, the next question is then "How can this function reach this state?". This can be answered by the symbolic execution engine, giving you a function-local path. Then you can look at the callers of this function and ask the engine to do the same resolution on that level.

Being able to formulate questions and have them answered would lead to a question/reply-driven method of working, which I think would be very helpful.

the-alt-one··on Why I use a debugger
How quickly do you guys whip out the debugger when you encounter a bug?

I often can figure it out by reading the code (I'm the quickest jump-to-source in the wild west!) quicker than I can from inserting print stmts or hooking up a debugger.

I've also decided that I dislike having my IDE be my debugger, I prefer having an entirely separate UI for that. Maybe this is because I use Emacs and DAP mode and gdb is quite poor there, I'd rather use something like gdbgui.

the-alt-one··on Scientists believed Covid leaked from Wuhan lab, but feared debate could hurt
It took a very long time for the Swedish FHM to say that masks work, so I don't know why everyone assumes that the rest lied to prevent a mask shortage.
the-alt-one··on OCaml Multicore merged upstream
It's been a long time since I was hyped about something in programming! Very cool, I really want to try OCaml now.
the-alt-one··on Against 3x Speed
Tides of History, In Our Time, Revolutions, Stronger by Science.

I like finding and listening to lectures on Apple podcasts too, like Zizek.

the-alt-one··on Worker pay isn’t keeping up with inflation
Nah, I was straight out of uni so taken on as a junior by the company and then given a raise as they didn't consider me junior after having me work there for 8 months or so. The union is probably involved in standard pay levels, but not much more than that.
the-alt-one··on Worker pay isn’t keeping up with inflation
Eh, I'm unionized and had a 13% pay raise. To be fair, they motivated that by saying that I should get up to speed with other engineer's raises instead of staying at a junior level (yes, I'm bragging).
the-alt-one··on Go Replaces Interface{} with 'Any'
It's not a hack, it's the natural way of expressing it in the chosen type system. The use cases for interface{} are often hacks, because of a lack of parametric polymorphism, but that's different.
the-alt-one··on One-more-re-nightmare – A fast regex compiler in Common Lisp
>language features will for sure limit the optimizations a compiler/interpreter can do

For example:

Common Lisp has a full numerical tower, meaning it will automatically convert fixed size numbers into bignums (and more cool stuff). This means that an addition has to branch if it can't prove that a result won't overflow from fixnum to bignum. Yes, C also needs to use bignums, but they're on an opt-in basis. In CL they're opt-out.

There are more examples of this, often related to the dynamism of your language. The more introspection a language is capable of, the less a compiler designer can do to cheat and optimize your program.

the-alt-one··on Event Sourcing Is Hard (2019)
This isn't unique to event sourcing, I definitely took the opportunity to soapbox.
the-alt-one··on Event Sourcing Is Hard (2019)
The big issue, to me, with concepts such as event sourcing is that they are fundamentally presented as software engineering concepts. You get a nice picture showcasing the overall structure and a story or two of how succesful this is, but we never discuss computer science matters. I want to know things such as "what safety properties does this system afford me?", "how is it abstractly modelled?", "what global invariants must I uphold for this system to work?". These are missing in regular conversation with other engineers, and I miss this kind of more formal reasoning. Ultimately, this kind of discussion should form the basis for the answers to questions of value to the business.

Bugs arise and are solved in these informal systems, but I rarely hear people ask "how do we never get this particular class of bug again?". These questions are kept for researchers (either academic or corporation), never to reach the regular software developer.

← PreviousPage 2 of 2