Software

Coding Philosophy/Goals/Mindset: Achieve business and technical requirements Agility means these may change as the environment changes, or coding realities drive changes upstream We must adapt to these changes Consider those (including yourself) who will be reading/modifying the code : Extensibility How easily can new features be added? Readability Includes formatting, proper ID naming, and good quality comments--not too many Maintainability How easy will it be to make changes to this code? Scalability What about growth?  For example, another server, or database may be required Efficiency Especially for larger projects, it is important to minimize resource consumption Project velocity While subordinate to the above and within the bounds of efficiency completing quickly/on-time matters There are many techniques and guidelines for achieving the above such as avoiding magic numbers (use constants) and keeping methods short and single purpose. ...

Guidelines for RESTful URLs Finding restful rules between REST clients and servers was more time consuming than other searches.  It must have been a block for others, too as I saw the question posted on various groups.  So I thought maybe it made sense to post my results here. Books as an example seems common, so I use books in my sample below. References: My instructor This reference.  While under a Ruby site, it applies to other languages: https://guides.rubyonrails.org/routing.html#crud-verbs-and-actions   This reference was very useful, but it only goes what I call "one deep"  that means in their example of "photos" we can act on photos/collection of photos.  However, it does not teach us how to add other "things" to photos.  For example, if the application is about users having photos, then we would add photos to a user. Or, if about the various users who have a certain photo, then we would be adding photos to that user A Tutoria...

Software developer, constructor, coder, writer, builder, engineer, architect, or something else... Here I plan to make notes as to my software experiences and maybe some observations. So what best describes those that "do software"?  I think all of these are appropriate. I like Steve McConnell's discussions in which he favors builder, or maybe engineer. He points out that writer sounds like something like a novelist telling a story.  It is true we write and we code but we are assembling something that does something.  I think I like engineer the best, but all of these describe. I think his observation says much about the profession: Computer science has some of the most colorful language of any field. In what other field can you walk into a sterile room, carefully controlled at 68°F, and find viruses, Trojan horses, worms, bugs, bombs, crashes, flames, twisted sex changers, and fatal errors? ---- Code Complete , Steve McConnell;  978-0-7356-1967-8 ...