Rumen Dimov

After publishing this article, all my code started getting back to me. Most probably, not related :-)

Maybe worth mentioning that you can avoid chaining if statements by using an enum with a proper search method too.

Extracting data from patterns example is strange - how an Integer can be a Dog?

Log4j ... come on

The code based on ngrx appeared to be much harder to read, understand and maintain. Especially when someone decides to build a "framework" over it. It is even specified on their site. So, use it at your own responsibility.

"However, realizing that using NgRx Store comes with some tradeoffs is also crucial. It is not meant to be the shortest or quickest way to write code. It also encourages the usage of many files."

https://ngrx.io/guide/store/why

Regarding encapsulation - like any other high-level concept, it should only be applied to the extent where it helps.

As a side effect of wasting time on searches I learn a lot of related or things. Browsing is not a waste of time to me.

Short and comprehensive enough to read at once, thanks. To me, the only real advantage of using REST is when you communicate with ECMAScript, because of the minimum effort of data conversion. However, consuming services in the back-end is much safer and loosely coupled with SOAP, especially when it comes to versioning.

Nice, but isn't it simpler to create a check constraint that limits the values to a set of string/varchar?

When you start revisiting your code regularly, you'll have much better comments because you'll need them yourself. Three months later there is nothing in your mind, so comments should be there to help.

I remember some 20 years ago I had to automate the control of a heating and air conditioning installation. Very short in budget, decided to use mechanical relays. With top quality parts, it took a week and came at a price 20 times less compared to the same using an industrial controller. Guess what the client chose ... the industrial controller, of course. They could not imagine it was possible to do it the other way.

Being creative is not enough.

Nice overview, thanks for compiling. Regarding access to sensitive data, maybe worth mentioning its full lifecycle, including backup, restore and archive/clear, for example.

I'm afraid I'm not an expert in the area, this was a big effort to my former colleagues in the flight and hotel reservation area. My personal opinion is this should be a continuous effort given the speed the internet language evolves. Most probably it is impossible to avoid all such cases, or even the majority of them. Maybe keeping a record of the generated and mark the complained ones ... but again - I'm not an expert. Wishing you best of luck generating :-)

Nice overview, but how do you deal with offending acronyms for example? A well know factor is the target users' language that can make some "safe" combinations offending too. Same for the cultural background.

IOC is not an option all the time. For example, you may want to use a singleton's functionality together with another framework that fully controls the lifecycle of the object. In such situations one may consider using an enum with a single member.

I often get the feeling that "popular" is more important than "good". The good things last just because they are good. If not sabotaged, of course. It was initially clear that there can't be a cross-platform GUI package apart from the browser. Therefore, Swing was just the best effort for the time. No big progress by far. GWT is like all the Google things - a huge blackbox. It is not my observation that the software developed by people is for the people and should be thus human-readable and understandable. Everything else goes away very fast.

Yet another way to say the software development is mainly driven by human interactions. I like the assumption that everybody's intent is to make it better :-) Nice spot, thanks!

Nice spot, thanks! Together with JSON, worth noting the XML type too. I personally find it more convenient for ORM purposes.

Needless to say it is.

XM(Language) vs. JSO(Notation) - is there a room for comparison at all? Each of these has its own field of application.

Keeping it simple :-) Thanks for spotting.

Nice spot. I'd touch the wording a bit to make it clear from the very beginning. This method really shines in cases when we need to manipulate the old value (if any) and not just update it with something we know in advance - a trivial operation on Maps.

36) The question is ambiguous. The proposed answer talks about implementation, which can be any. The right answer is DOM parser gives you a DOM object, while SAX parser just navigates the XML tree issuing events to the provided Handler, i.e. you have the chance to react before the whole XML structure is fully parsed. It is arguable if SAX parsers load the whole tree in memory, because they don't act on non-well-formed data and to find out about well-formedness the data must be traversed entirely.

34) The answer is "yes, through reflection, given the Security Manager allows"

In Java, if you don't mind working with anonymous subclasses, you may consider using instance initializers.