This is the first of a series of posts, I want to go over some of the groundwork of what it takes to make exceptions localizable into other languages. Nothing new here, but just want to explain clearly the requirements of a localizable exception messages.
Still reviewing that code base and finding more bad patterns for use of constants, this time for error messages. This is another “don’t do this” post. Continue reading
The documentation on Angular expressions is so sketchy that I really can’t work out what it means, so I have “decoded” what they say, and here is the two useful cases. Continue reading
Programming is an act of design, and in order for a programmer to do the job, they need to have a thorough understanding of the actual customer and actual situation. An abstraction will not do, otherwise, it is like asking someone who lives in a jungle to design a pair of ski gloves. Continue reading
Writing code, writing the manual, supporting the product, and testing the code all go hand-in-hand. When I get a question on the product, it is an opportunity to improve the manual Continue reading
This post contains a quick reference to the commands you need to know to use Git, the source management system. I assume you already understand the concepts behind source management. This quick reference is to the commands to use. Continue reading
My last post was you can avoid a lot of waste in a project by recognizing program logic errors, and keeping the exception being thrown very lightweight. In this post I talk about a particularly heavy exception, the individual exception class, which is constructed to communicate just one thing. They are just too heave for most use, and here is why. Continue reading