31–34 of 34 posts
It's just normal gateway with a bunch of `if then else` for business logic to decide at the edge.
The benefit, is i can turn on/off easily, and it allows me to add new features without breaking existing features easily.
Earlier quoted context omitted.
When I was in software engineering school, we had a tongue in cheek word for this: patternitis. Many undergrads who took the software architecture class ended up catching this strange disease that compelled them to write abstract singleton factory builders and other silly things. The cure is basically to write enough software to figure out where these patterns make things more understandable and where they detect fro…
Patternitis is part of a cluster of diseases for a greenhorn dev. Abstractiosis - Adding layers of indirection which don't serve to make the code clear DRYicron - Overeager deduplicating code (usually by adding hard coupling) Fooflation - Avoiding descriptive names of methods/variables in favor of "result1, result2, goOn" All fixed with a little TLC and experience :) * ask your doctor if experience is right for you.
All fixed with a little TLC and experience :)
There's a funny overcompensation that greenhorns have when improving their code. Someone will ask them to use better names, then you get a few months of `let loopIndex = 0` when `let i = 0` would have been just fine.
Earlier quoted context omitted.
When I was in software engineering school, we had a tongue in cheek word for this: patternitis. Many undergrads who took the software architecture class ended up catching this strange disease that compelled them to write abstract singleton factory builders and other silly things. The cure is basically to write enough software to figure out where these patterns make things more understandable and where they detect fro…
Patternitis is part of a cluster of diseases for a greenhorn dev. Abstractiosis - Adding layers of indirection which don't serve to make the code clear DRYicron - Overeager deduplicating code (usually by adding hard coupling) Fooflation - Avoiding descriptive names of methods/variables in favor of "result1, result2, goOn" All fixed with a little TLC and experience :) * ask your doctor if experience is right for you.
Earlier quoted context omitted.
Patternitis is part of a cluster of diseases for a greenhorn dev. Abstractiosis - Adding layers of indirection which don't serve to make the code clear DRYicron - Overeager deduplicating code (usually by adding hard coupling) Fooflation - Avoiding descriptive names of methods/variables in favor of "result1, result2, goOn" All fixed with a little TLC and experience :) * ask your doctor if experience is right for you.
Metaprogrammitis - Im an "advanced programmer" now so Im gonna use the most advanced language features for the most inappropriate purposes.
"Yeah, I made a compiler plugin to generate code with my own custom preprocessor language I made up because I was so sick of write for (i in c)"
One guy in my company tied into Java's annotation processing engine to create his own server side UI framework driven by his random annotations.
The generated code? Usually just creating a method that populated a HashMap with stuff pulled from the annotation... Yeah...