The actual metrics (not necessarily easily quantifiable) are the desired traits you put in your job description; they don't correlate perfectly.
6,179 karma · joined April 18, 2010
https://danieljanus.pl
meet.hn/city/52.2319581,21.0067249/Warsaw
The actual metrics (not necessarily easily quantifiable) are the desired traits you put in your job description; they don't correlate perfectly.
Thanks for jank! It’s great to be reading about it, listening to you talking about it at conferences, and I can’t wait to try it out!
Automated CI was not quite as big back then as it is now; we had some in-house CI-ish facilities, one of which was buildbot: a small Python script that continuously built all of our projects one after another, reporting successes/failures in a simple UI.
One day I was puzzled to discover that buildbot hung trying to build a tiny Java applet. Just a handful of .java files. But it had been stuck for more than four hours at that point.
I ssh’d into buildbot and looked at what exactly the hung process was doing. It was not javac. It was jarsigner.
Then it dawned on me. jarsigner needed some crypto-safe randomness, it was trying to get it by default from /dev/random, not from /dev/urandom, and the machine ran out of entropy!
I ticketed a change, but as an interim measure, I went to the server room, switched the console to buildbot’s server, and moved the mouse vigorously for some seconds. It proceeded.
Arrays in TP were laid out in row-major order, and each character was represented by two bytes, one denoting the character itself and the other the attributes (foreground/background color and blinking). So, even better, array[1..25, 1..80] of packed record ch: char; attr: byte end absolute $B800:0000.
Replace $B800 with $B000 for monochrome text display (mode 7), e.g., on the Hercules.
> A careful programmer will check the return value of close(), since it is quite possible that errors on a previous write(2) operation are reported only on the final close() that releases the open file description. Failing to check the return value when closing a file may lead to silent loss of data. This can especially be observed with NFS and with disk quota.
Last time I checked, GCC’s implementation of ~ofstream() ignored failures from the underlying close().
I approached the math olympiad back in high school, but found it too challenging. Looking backwards, I think I might have benefitted from having a better math teacher.
I’m 41 now; AMA.
ISC also supports Polish (with OSPS).
> Rev. Robert Prevost bears responsibility for allowing former Providence Catholic H.S. President and priest Richard McGrath to stay at the high school amidst sex abuse allegations that dated back to the 1990s.
> That's according to Eduardo Lopez de Casas, a clergy abuse survivor and national vice president of the Chicago-based Survivors Network of those Abused by Priests (SNAP).
[0]: https://willcountygazette.com/stories/671124585-if-he-saw-an...
In 2004, Gavin Barraclough’s mini-OS [0] won the IOCCC, packing a 32-bit multitasking operating system for x86 computers, with GUI and filesystem, support for loading and executing user applications in ELF binary format, with PS/2 mouse and keyboard drivers, VESA graphics, a command shell, and an application into 3.5 KB of highly obfuscated C code.
In 2021, Justine Tunney wrote SectorLISP [1], a Lisp implementation that fits into a bootsector and is able to run McCarthy’s metacircular evaluator.
[0]: https://www.ioccc.org/2004/gavin/index.html [1]: https://github.com/jart/sectorlisp
Is it, though? I play at around 1000 Elo – I have a long-standing interest in chess, but my brain invariably turns on fog of war that makes me not notice threats to my queen or something – and I solved it in something like one minute. It has very little moving parts, so the solution, while beautifully unobvious, can be easily brute-forced by a human.
I love the concept and the execution. This is a rare instance of a Show HN that I not just admire, but can easily see myself using regularly and paying for.
Please, please monetise this in such a way as to avoid enshittification.
The Right Thing for Polish would be to leverage the Polish inflection and freeform syntax, in the vein of Perl’s Lingua::Romana::Perligata [0].
[0]: https://metacpan.org/dist/Lingua-Romana-Perligata/view/lib/L...
; in: THE 'END
; (THE 'END)
;
; caught ERROR:
; Error while parsing arguments to special operator THE:
; too few elements in
; ('END)
; to satisfy lambda list
; (VALUE-TYPE FORM):
; exactly 2 expected, but got 1In the vast majority of cases, it’s not. If removing comments breaks roundtripping, then so does altering the indentation or adding/removing whitespace, even ever-so-slightly.
EDN parsers strip comments when read – it’s not an issue in practice.
Kudos for the nonviolence. :)
Also, the Beast puzzle in ’The Edifice’ [2] by Lucian Paul Smith comes to mind.
[0]: https://www.eblong.com/zarf/zplet/lighan.html