Software design and architecture

From monolithic to microservices . This is dangerous and even though this is how my mind works, sometimes, may be limiting our minds. The idea of microservices, I believe is an amazing approach to development, and much more currently that we have whatever/anything/everything as a service , companies tend to have cloud solutions and plug n' play compatibility with different services. The microservices architecture must be an approach that jumps into your mind immediately whenever you think of implementing something in a company, or as a developer, developing for a company. Nothing's more scalable and easier than services connected in between just by API endpoints. I'll defend microservices architecture all the way. (:

The main subject of this I believe is the self-learning idea. Currently many programmers may actually feel that after you get out of college you lack of some skills, and you actually do. I feel that university offers the very basics (in some subjects) of the skills you'll need in the many professional fields. Just like many skills, to be a programmer you must be auto-didactic, maybe you can feel that many languages are practically the same and only change syntax. You may be mostly right actually, but to learn even those similar syntaxes is just like learning spanish, french, any language. In order to perfect any skill you must practice and invest your own time and learn new things fueled by your curiosity.  Curiosity is, in my humble opinion, one of the greatest characteristics a person can have, it's one of the strongest fuels you can think of. This takes us to the term of Craftsmanship, a great developer is great a craftsman (a person skilled in a partic...

Sci-fi, I feel is just opening a window to the future. Many things considered sci-fi in 80s movies are quite a reality now, you can pick almost any movie prior to the 90s and you will most likely find the similarities immediately. The idea of having a teenager hack into a government's pc is not quite far from reality, in the recent 20 years we have found things like people hacking into systems accessing IP cameras or back when Valve was on their younger phases, a teenager found a way to get into their system and get a game's source code, he only wanted to see what the game was like... just like in Wargames. I mean he didn't almost cause a nuclear war, but he got a big scare out of it. Wargames not only is a quite enjoyable movie, it's a lesson in some subjects such as security, responsibility or accountability of matters. This movie raises the question... are we going to be able to program in such a way that our own logic doesn't play against us? (insert movie...

I think programmers are artists, and have evolved greatly... why do I say that? Before, code design was just to sit and code, there were no official frameworks, strategies or workstyles, now we have many paradigms, delivery styles, testing, etc etc. It's always cheaper to test than to correct once a software is in production, that's why we evolved our methodologies and styles over the years.  On the other side, extreme programming is keeping it simple, even getting to the point of hot having a design at all. This is a cheaper approach for development because you actually don't have any extra or unnecessary effort. Maybe a limit that can be found in extreme programming is the lack of diagrams, it's practically impossible to implement UML in it. Diagrams are quite useful of how is the interaction between components and gives visibility from high to very specific level.

Since I was a little kid I always wanted to change things to work in a more efficient/easier/convenient way, as simple as organizing my toys as per usage, this idea evolved all the way to my professional career. Currently I manage projects of commercial systems and what I've found are many learnings: Similarities between a project manager and a software architecture Get $#!T done, a PM has to ensure communication and that workflows happen, as well as an architecture according to the lecture, has to have some high convincing skills, as his recommendations have to be listened and applied  Experience and responsibility As said previously, recommendations and tips... there's nothing like experience of getting involved in projects in order to have your voice have a valid and substantial background Importance and scalability A PM as well as a SA must have under their scope how easily their project/software will be taught, learned, scaled, this is their res...

In the lecture of Code Craft we can see how software architecture is a high relevance topic for computer science, talking about how its evolution has increased the investigation and study cases. "Initial system design"... this is what Goodliffe mentions architecture is. This takes us to three pillars or cases in which architecture has jurisdiction: validation, discrimination and communication. Previous cases have direct impact in how you can avoid work duplication, redundancy, and wasting efforts (validation) When having proper software architecture, you improve communication as this helps with a high level view of what may be a complicated system or difficult to read to all stakeholders in a project. As for discrimination, it says how some situations can generate problems while decision making, having this concerns validated  we can then discriminate  some options. Mainly, the purpose of the lecture is to understand the importance and objective of s...