The customer is often right.
Sometimes, the customer is missing a vital piece of context which would enable them to be right.
We have known for decades that adding people to a late software project only makes it later.
So why is it that nobody gets hired for a team that is ahead of schedule?
Seriously considering a ground-up rewrite of the #EpochLanguage compiler... Yet again. The existing project is riddled with assumptions that I don't like, is very poorly organized, and implements a language that is almost - but not quite - what I want it to be.
If I do it, I will keep large chunks of the existing code (linker mostly). But it's a big enough lift that I am very hesitant.
Anyone got some recommendations for reducing .PCH file sizes? Besides the obvious one ("include less").
I would love to have Clang's chained PCH support in Visual Studio, but oh well.
Presently doing 50GB of disk IO just on PCHs for every clean build of a certain project. Would love to make that number a lot smaller.
Computers are truly amazing. I can transfer literally billions of pieces of information from one place to another in a second.
Software is equally amazing. I can squander the immense performance capabilities of the computer effortlessly by writing some sloppy code.
Turns out cache invalidation is still a Hard Problem.
Renewing my search for users (or instances!) that might have an interest in #ProgrammingLanguages - particularly design and implementation.
Here is my current project: https://github.com/apoch/epoch-language
(It isn't very approachable right now, but I am making good progress on the second self-hosted compiler and IDE integration with VS2017.)
The quintessential Friday afternoon is listening to a discussion about design patterns get drowned out by random people saying "blood!" in silly voices.