Notes on Continuing education

My understanding of N tier.  N tier is an abstraction layer system that lets you pass data between applications without direct interaction. The main benefit of this is that if the public server is compromised the attacker will have to keep compromising N servers/ services to get to the meat of your product. This is part of the layered onion security model approach. The more layers you have between a possible attacker and your data the better.  A basic example is you collect information on the front end of your application that you want to encrypt. But rather than having the encryption module have direct access to the front end you abstract it.  So it would go that the user inputs the data in the front end that is then picked up by a queue and then processed and encrypted. Frother more you can make it so that the public endpoint can only encrypt the data not decrypt. Now you can also make it so tha...

Starts at 4:30 From the clean arcutecute book view low level code is code that will change frequently. And high level will never change. For instance the formula for interest calculations should never change but you might use it in a new way. So the interest calculation formula would be a high level code and the code using it would be lower. It was brought up in the podcast that the arcutecute should reflect the program not the framework. I do not feel this is fully true as the point of using the framework is so that it is structured in a way that any software engineer that has worked in the framework before should be able to pickup the project with out much spinup time.

Names should be meaningful and avoid jokes and puns.  Names should not have single character names unless it is convention such as "i" in a loop.  Names should not be too similar to other names. Names should not include junk works such as info or data. Names should not have data types in the name. Names should not have abbreviations. Names should not have slang Names can have jargon that all in the field would know. A name is meant to give the developer information about what it is used for and what it contains. Without giving that meaning it cannot be helpful and it will slow development. Worse is if the name canvases the wrong information.

Hello Internet, This blog has two goals for me. The first one is to help solidify concepts and ideas that I am learning about. The second is to help me with my grammar, spelling and content delivery of technical information in a non-technical way. As such this is not a blog meant for others to read it is more of just for personal development. If you see grammar, spelling or content problems please drop me a line with a youtube video of how to fix the underlying problem. I am using Grammarly but it only helps so much.