Skip to main content

Software Design Principles - SOLID

The SOLID software design principles weren't called SOLID while I was in grad school, but the concepts were there in my Object Oriented Design course. They're worth mentioning here, primarily because I think once you start coding and become dangerous, it's one of the best ways to stay organized once you incorporate it into your daily coding routines, and it even changes your way of thinking for the better:

https://en.wikipedia.org/wiki/SOLID

Comments

  1. The article makes an interesting point that the ideas behind SOLID existed in Object-Oriented Design before they were grouped under the SOLID name. The emphasis on incorporating these principles into everyday coding is particularly relevant because good design is not only about individual classes but also about maintaining organization as a codebase grows.

    These principles can be applied when structuring JavaScript applications, particularly when responsibilities are divided across classes and modules. In that context, JavaScript Online Course concepts provide a practical environment for applying object-oriented design ideas discussed in the article.

    ReplyDelete
  2. The same object-oriented concepts can also be used when designing Python applications, where classes and composition provide ways to separate responsibilities. From this perspective, Python Online Course learners can relate SOLID to practical code organization rather than viewing the principles only as theoretical design guidelines.

    ReplyDelete
  3. TypeScript adds explicit interfaces and type definitions that can make some design boundaries easier to express. This makes TypeScript Online Course relevant to understanding how SOLID ideas can influence the organization of larger applications.

    ReplyDelete

Post a Comment

Popular posts from this blog

C++ Development Environment

Trolling through some forums today, I found some great resources for C++, so I expanded on it and inserted some annotations. Categories are Integrated Development Environment (IDE), UML Interface, Team Collaboration, Coding Standards, Bug Tracking, Version Control, Unit Test Library, and Performance Testing. A bracket sits next to the resource which contains a W for Windows support, L for Linux, and M for Mac. A $ indicates that a standard version of the software will require a purchased license. IDE: Eclipse CDT ( eclipse.org ) [WLM] Visual SlickEdit ( slickedit.com ) [WLM$] UML: Eclipse MDT ( eclipse.org ) [WLM] Team Collaboration: Skype [WLM] Zoho [WLM] Sharepoint [W$] SourceForge [WLM] Coding Standards (Platform Agnostic): The Lockheed Martin Joint Strike Fighter C++ coding standards ( att.com ) The MISRA C++ coding standards [$] ( misra-cpp.org ) Bug Tracking: Bugzilla ( bugzilla.org ) [WLM] Unfuddle ( unfuddle.com ) [WLM] Version Control: mercurial subversion mercurial git cvs ...

The TL;DR guide to git

While in the past I've held a pretty high opinion to using mercurial for version control, the majority of version control these days seems to done in git.  Here were the commands I found most useful to get productive with git right away. # Clone a repository from an origin, i.e. my github MaskingUtils repository git clone git@github.com:caelumvox/masking-utils.git # Add a file after it's been updated to stage it for commit, or add a new file git add filename # Commit the file to local repo git commit # Push the file to the origin so the rest of the team can see it git push # List all locally tracked branches git branch git branch --list # Get a list of all branches from the remote git branch -r # Create branch locally git branch develop # Push the branch to the origin repository to make sure it is tracked there git push --set-upstream origin develop # Pulls latest from all local branches tracked from origin; won't pull non-tracked branches git pull --all # Fetch the branch ...