Something still unsolved.
On the pitfalls of jumping to technical solutions for social problems.
The verdict, as usual, depends on context
Combinatorial optimization to end all bikeshedding
Separating math from rendering
Time moves on, APIs break
How do I do this again?
Lambda to the rescue!
Why grep is so damn fast
Lessons learned from haskell
Reminiscing and an outsider's postmortem
Running apt rootless without proot
Shrinking containers and running them without root
A striking difference between Software Engineering and every other Engineering
Deferring a hard problem
Port all the things!
Making the blur plugin work with the modern OpenGL API
A nice package manager for C++
Based on XUnit
Unexpected behaviour bites hard sometimes
An easily misunderstandable API
A short performance analysis
Debuggers are useful for things outside programming, too
Template metaprogramming to ensure that you're calling a noexcept function
A context-manager based idea to prevent an age-old memory problem with vectors
Some niche X11 API causing problems
A follow up to the comment on the other post
Some additional thoughts on another post
Coming to an HTPC near you
Some votes of thanks
Some documentation from a third party
Porting was fairly straightforward
An initial pull request
Testing poorly written code reveals that it is poorly written
A suggestion on using "death tests"
Some ideas about guidelines
Finding a balance between community and strategy
Theory to practice
Using GI data to generate code functionally
Some quick debunking
Testing the untestable
Blurring "behind" things
A tale of porting from fixed function to programmable pipelines
Something smarter than the regular double-buffering
A short congratulations
Repainting tricks to a desktop near you
A brief call
Moving on from the legacy OpenGL API
A trick to get more specificity in your CTest output
Written by Sam Spilsbury an Australian PhD student living in Helsinki.