Posts
- Harassment: ASML, miscellaneous events
- Harassment: ASML, 2nd team: high-prio project
- Harassment: ASML, licensing (complete)
- Harassment: ASML, UX Trojan horse
- Harassment: ASML, 1st team: PO pushing features
- Harassment: ASML, organizing "Knowledge Sharing Sessions"
- Harassment: ASML, Dependency Injection
- Interim: ASML, Proguard
- Harassment: ASML, group lead team composition fuck-up
- Harassment: ASML, STI assisting with release management
- Interim: ASML, manual builds and continuous integration
- Harassment: ASML, 1st team: team architect conflicts
- Harassment: ASML, licensing (partial)
- Coordinated harassment - introduction
- Encoding: prefixed-compact
- Nostrkey - a program for nostr identities with hardware protection
- A simple, asymmetric AKE
- Very old project: driverinf
- Prevent linux system freezes because of dm-crypt
- Indicators for human advancement [Part 1]
- Analysis: the right angle
- The Venus Project - resource-based economy
- The imploded (third?) industrial revolution
- Human Advancements: Introduction
- Engineering: The unified OOP paradigm
- Engineering: The “minimal-objects” approach to OOP
- Engineering: References
- Engineering: Introducing simplicity to engineering
- Object Oriented Programming: (implicit) acknowledgement of the missing access modifier
- Prematurely abandoning simplicity
- Concluding the definition of 'simplicity'
- Evaluating 'simplicity'
- Absolute and relative simplicity
- Bad example demonstrates failure in complexity
- Questioning the scope of 'simplicity'
- Discussion for users, issues for devs
- Rust memory management: Reasoning from local scope - part 1
- Refining 'simplicity'
- git: merge only the completed work
- On Error Handling
- What if Programming Is Like LEGO?
- Proposal: refining Go export conventions
- The hackability of simplicity
- The definition of simplicity
- Setting the Linux CPU scaling governor through udev rules
- The symbiotic relationship of hash and AEAD
- Convert your site into a simple progressive web app
- On Class Design
- Java compile-time static analysis with Error Prone and NullAway
- Java fuzzing with JQF + afl
- How to be efficient
- Secure Boot Linux Shim (Mokmanager)
- What is in spotbugs annotations?
- The local build configuration for otr4j
- Secure Boot in Fedora 27/28
- Refactoring otr4j
- Object Oriented Programming: Evolving code
- Object Oriented Programming: Evaluation of design patterns
- TODO-supported development
- Object Oriented Programming: Objects as utilities
- Object Oriented Programming: Utilities - Next Generation
- Object Oriented Programming: Utilities
- Object Oriented Programming: Designing objects
- Object Oriented Programming: Concrete types in implementation logic
- Object Oriented Programming: Accessor methods
- Object Oriented Programming: Curiosity of access modifiers
- Object Oriented Programming: Implementation and usage - Generalized code
- Object Oriented Programming: Implementation and usage
- Object Oriented Programming series introduction
- What is your goal?
- Checked Exceptions for reactive flow control
- Error handling in modern languages
- Why I prefer error values over exceptions
- NetBeans - More static code analysis
- Object Oriented Programming: Expectations - The Silent Third Characteristic
- Features vs. Requirements - Conclusions
- Features vs. Requirements - Buffering
- Features vs. Requirements - I/O Operations
- Features vs. Requirements - Threading
- Features vs. Requirements - Introduction
- 'Draft' markers in listings for Hugo
- When to use Go's iota
- Windows 10 upgrade experience 2 - 32 Percent ...
- IRCv3 tls extension experiment
- Windows 10 upgrade experience - BSOD on mfewfpk.sys
- Ambitions in A.I. - Google Photos, why now?
- The curious side-effects of HTTP 2 push promises
- Netbeans - Improve speed by disabling local history
- Proxy support for Java SocketChannel
- Testing in a Vert.x environment
- Java signed integer types and alternative representations