@runfrodorun as much as I hate close sourced Microsoft stuff, somehow my career has led me to C# dev. There's no escape :(

@Archetipo the idea is that working alone can be much faster without the communication deadlock. Compare putting together a solution to a problem on your own vs putting together a mockup for your company, agreeing on the business requirements, working with the team to build a reusable solution, and meeting a long term deadline.

Sometimes it's hard to understand that, at the end of our day, we're just supposed to build software. The only thing you can do when you have a strong disagreement with your company is look for another job. The good news is that this experience will help you grow and that this is a great market to be looking for a job

@JonnyCodewalker you'd have to disable memory protection, but it's something old microcomputer programs used to do (though it was usually in assembly). The official name is Self Modifying Code or SMC. Most modern OSs disable it since it is such an antipattern, and used by malware

That's legalish (hey, I guess it works), but I think that falls into the category of "Don't ever do this in production." I'm not positive if that falls into the category of undefined behavior, but I wouldn't be shocked if cranking the optimizations up on the compiler broke that

@Ashkin I learned to program with assembly and learned Ruby as my first general purpose language. Unfortunately, I think Ruby really does have a scale issue, but more generally, performance issues. Given lightweight and more active communities in the NodeJS and Go communities, I'd argue that learning Ruby is a bit moot at this point. I wanna love Ruby, but I just don't see it having much of a future without a significant rewrite or paradigm shift.