97 Things Every Software Architect Should Know

This will be my list of the 30 out of the 97 that I felt most identified, if you want to read all 97 here is the link of the book.

So, let’s begin

1) Don’t put your resume ahead of the requirements

This first one is kinda obvious (most of them are tbh) but not really. The important thing to underline here is that it is more important to use the technology that fits better the user, even if it is not the most challenging, it is better to have something that works perfectly done with an «easy» technology that doesn’t look that good on your resume, than something complicated that looks «pretty» on your resume.

At the end of the day, it is way better for your career to have happy costumers, than an «impressive» CV. I mean, if you have happy costumers, they might tell their friends about you, and before you know it, you have more work and a better reputation.

2) Chances are, your biggest problem isn’t technical

It is very easy to blame the technical aspect when a project fails, buuuuuut in most cases it didn’t fail because of it, it failed because of the people that were involved in such project. Because, well, people are what make the project and if you can’t communicate with the ones that are not performing as well as the others, then your project will probably fail. Conversations are key, and that’s what I’ll talk about next.

3) Communication is king; clarity and leadership its humble servants

To have a good communication between the Software Architect and the Developers, the first thing to do is be there, with them, don’t sit on top of the tower, as if you were more than them. Next, you will need to use clarity and leadership to communicate whatever you need to communicate.

I mean, if you’re not clear no one will understand what you’re trying to say; if you don’t have good leadership then no one will believe or take you seriously; and if you have neither, well, let’s start working on getting those servants, because without them your projects will end up failing.

4) Stand up!

This one also talks about communication (what a shocker) and how important is to be heard, to stand up and say what you think, also stand up if you’re the one talking (like literally stand from your seat) so you look like you’re in charge of the situation, you’re the man (or woman) with authority with self-confidence.

So, now communication needs you to stand up, and to have clarity and leadership as servants.

5) Everything will ultimately fail

This sound very apocalyptic and like hell will break lose, but it is important to understand that software and hardware can (and most likely) fail. So you have to be prepared for the worst, you have to be prepared and have a plan in case something goes wrong. Designing for failure is being prepared for the worst, and as they say: «A prepared person is worth twice as an unprepared one».

6) One line of working code is worth 500 of specification

While having specifications is great and all let’s be careful with how you write them, because it’s one thing what is written in paper and what can be done with code. That is why it is important to always keep in mind that the end result of the project is the product, not the specifications. It is better to have specifications that the coder can understand, rather than something so convoluted no one will get the point.

7) There is no One-SizeFits-All solution

This should be one that is pretty obvious, but sometimes people forget the importance of diversifying solutions. Trying to solve everything with the same way, the same technology, the same resources is virtually impossible. That is why you have to keep learning new ways to solve problems, or to have in your team people with diverse knowledge.

8) Commit and run is a crime

Lesson one: never commit without testing first. Lesson two: create an atmosphere where testing can be done easily and without wasting much time. Lesson three: never commit without testing first.

9) Use uncertainty as a driver

This is something that I hadn’t thought of before. We make decisions all the time, starting with what to wear that day, ending in the time we want to go to bed. For architects it is the same, the difference here is instead of choosing, we have to ask ourselves «why are we choosing?» and «how can we make the decision less significant?» Because if we can take uncertainty from the equation, things can be better solved along the way.

10) Warning: Problems in mirror may be larger than they appear

As mention before failure happens, things break, but sometimes the sign of it appear early on; but few people catch it, or no one really pays attention to it…until it is too late. That’s why there has to be an organized approach to tests, also, believe in the «bad smells» just try to find a way to back it up with tests.

11) Get the 1,000 feet view

Software quality, it is so important and yet sometimes we don’t really know how to do it. In most cases we check the source code, which is like looking at something from the ground; or at the whole project, which is like looking at something from really far up. That’s why we need a middle ground, the 1,000 feet view, so that we can see a lot, and yet be close to see details.

12) Time changes everything

Yes, time changes everything, including you. It is important to have this in mind when looking back at certain projects, because the way you think right now is not the same as the one you had last year, then years ago, and that is okay, you just have to embrace the change, because at the end: time changes everything.

13) Skyscrapers aren’t scalable

When creating any software project you can’t just do everything at once and expect it to survive in the real world. It is better to develop component by component, as if you had mini projects, that way each component will be able to survive  on its own and when you add all of them, there won’t be much problem with integration.

14) Talk the talk

Everyone has its own way to communicate, that’s why Software Architects have their own, and to be able to talk their talk it is important to understand the basic concepts of software architecture and design patterns, so that when communicating with each other, both parties understand what is being said.

15) Context is king

Well, we found another king: context. The importance of this one, is that there is no one solution (as stated before), because the context of each project helps to figure out how to solve it. Not only that, but also the surroundings matter: emerging technologies, leadership strategies, etc. That’s why you have to keep all context in mind.

16) Welcome to the real world

The real world is not like the one we see during school, outside things constantly change, promises are broken, you don’t always get what you expect. In school, everything is simple, you either do something or not, pass or fail. Outside, things are different, and we have to be prepared for that, because if we’re not, then we’re in a lot of trouble.

17) Record your rationale

This may sound funny, but it is true: keep a dairy. Keep a dairy with the «whys», «why did I chose this?», «why am I doing this?». Keep it close to you, and update it regularly, so in the future you can remember why the decision was made and in that way, it will help you make better decisions in the present.

18) Prepare to pick two

You can’t always have it all, and that is something that also applies to projects. It is impossible (or too expensive) to have the three aspects of CAP (consistency, availability and partition tolerance). That’s why you’ll have to choose only two, but the thing is choosing which two fit better to the project.

19) If there is only one solution, get a second opinion

It is very important to have multiple solutions to the same problem, because in that way you can see how the different solutions apply to the problem and in doing so, the product will be most likely suited to the intended purpose.

20) Shortcuts now are paid with interest later

Imagine that you’re buying something and you have the money to buy it right now, all of it. But instead of doing so, you decide to pay it every month; what you didn’t realize is that at the end of the day you’ll end up spending way more money by paying it monthly, that what you could’ve paid at once. Exactly the same happens with software, if you push things, you’ll end up doing them later, at a higher cost.

21) «Perfect» is the enemy of «good enough»

There is no such thing as absolutes, that’s why I don’t believe anything can be «perfect». So it is important to know when your project is «good enough» so you don’t fall into the temptation of making it «perfect». Most of the times, when trying to achieve perfection, we just get stuck again and again, never being happy with our project.

22) If you design it, you should be able to code it

Again, this is self explanatory. It is kinda obvious that you shouldn’t expect that someone does something (or uses something) that you’ve never done/used. At the end, developers are also humans, and they have learning curves, so if you have no idea what the learning curve is, you have no idea how long your developers will take in understanding what you asked them.

23) A rose by any other name will end up as a cabbage

So, in summary if you can’t put a name to what your software does, you are probably doing something wrong. When your name is vague enough, you probably don’t really know what you’re doing and that is a major warning that something is completely wrong. So, beware!

24) Take responsibility for your decisions

Decisions, we’re back to them, but this time, we’ll talk about the repercussion of decision, or well, facing those repercussions and taking responsibility. It is important to take responsibility of our actions because it helps us grow as better software architects. So, don’t be afraid to take the blame.

25) Don’t be clever

Lesson one: be dumb. Wow, those are words that I thought I would never say. But it makes sense, sometimes what you need is something really simple, so in our efforts to see everything with all of our knowledge we create something complicated, when in reality all you needed was something very very simple.

26) It will never look like that

Back to the difference between school and real world. In school, when you plan something, when you design it, the result will probably look a lot like the design; in the real world it won’t, and that is okay. So, don’t spend too much time making the design «perfect» because at the end, it will change.

27) Don’t be a problem solver

The thing is, let’s not rush to solve the problem, but take a step back and ask if the problem is really a problem, I know I sound like Ricardo Arjona, but maybe we’ve been trained for so long to solve problems, that we forget to ask wether they really are problems or not.

28) Learn a new language

By language let’s not think of English or Spanish, not even Java or C++. By language, it is the terms used by Programmers, Customers, Business, Testing. It is very important to know how they talk, so you can talk to them in the same way, in doing so, it’ll be more likely to be understood (look, communication IS king!).

29) The user acceptance problem

When creating new systems we have to consider how the public will react to such new system, even more if it replaces an already existing one. It is not as if you’ll try to have no negative reaction from the public, but you might be able to mitigate it a little bit, or reduce it. At the end of the day, you want your costumers happy.

30) The importance of Consommé

Finally, let’s talk a little bit about requirements and how refined they should be, how understandable, how many times you should spin it around and around. Because requirements are important, they mark what the programmers will end up coding, so it is important to have them clear, concise, but always remember, there’s no such thing as perfection!

Thanks for reading!

The end

The semester is done, my 8th semester studying ISC came to an end and I don’t know how to feel about it, but that is not what this post will be about. I will talk about what I learned throughout the Security course. This won’t be a huge blog post, I’ll just point out a few things that I am taking from this course.

  • Update, the importance of keeping all my devices updated so that I have the latest security.
  • Backup, keep a lot of different backups in case something fails with the computer you won’t lose the data.
  • Layers, it is of great importance to have as many layers of security as possible, so it becomes harder and harder to break into your system.
  • Trust no one (or almost no one), check who your giving permission to see your social media, who sees what and why they see it.
  • Stay up to date, keep checking the new things that come up, the new technologies, the new threats.

And those are the things that I learned more from this course, thanks for reading it has been a great ride!

Bye.

YouTube’s way of flagging videos

In the last months, right after the series of Apocalypse that YouTube faced, YouTube decided to create a new algorithm to flag videos that weren’t «advertiser friendly». This new system worked, well kind of, depending of who you ask. According to the Google CEO this new system removed over 8 million videos from YouTube, of that number 6.8 million were first flagged by the computers, which is about 76% of the total.

Now the question is, does it really work? Does it actually just flag bad content, or does it also take down content that follow YouTube’s policies? And that is the core of the problem, because the system is not perfect (nothing really is) but YouTube is leaning a lot in a system to catch the «bad» videos. I

am sure that a lot of the videos that gets flagged are actually non advertiser friendly. But a fare share is okay.

Here is where we get to machine learning and if it will be good or not. No matter how much we try to, we won’t be able to program emotions or common sense to a computer (or at least any time soon). So, how much should we depend on a computer to do work where there is a lot of common sense involved? Yes the systems do the work for us, but at what cost?

In my opinion, we should keep a check on it, monitoring their behavior, us the humans making sure that the computer actually does what is supposed to do without damaging others, just as YouTube is trying to do. I am a little scared of what a system like that could do unchecked, but I hope it never happens.

Portafolio ISC

A lo largo de mis casi 4 años siendo estudiante de la carrera de Ingeniería en Sistemas Computacionales he creado diversos proyectos, gracias al consejo de mi amigo Gerardo Velasco, decidí hacer un blog al respecto. En este blog hablaré un poco de los proyectos más relevantes.

Wallet Dots/e-Dots (Enero 2015 – Mayo 2017)

Este proyecto lo desarrollamos Gerardo Velasco y yo a lo largo de varias clases, la idea comenzó en la clase de Diseño de Interfaces y la estuvimos continuando en Fundamentos de Software, Algoritmos, Bases de Datos y terminarla en Diseño de Aplicaciones Móvil. Esta app detecta si estás en clase y te motiva a tener tu celular bloqueado durante las clases, ya que entre más tiempo pase mientras tienes bloqueado el teléfono, más puntos te va a dar; mismos que después se pueden cambiar por cupones en diferentes tiendas.

La app estuvo un tiempo en la Google Play Store, pero la tuvimos que dar de baja.

Video:

Participando Por México (Enero -Mayo 2018)

Este proyecto fue desarrollado en la clase de Emprendimiento Social junto a mis compañeras Mariana Sánchez y Mariana Benítez. La idea es crear una plataforma donde los jóvenes puedan encontrar las herramientas que les hagan falta para convertirse en participantes ciudadanos en cualquier aspecto de su vida, desde votar, hasta ser parte de alguna A.C.

Video:

Tay Tay Love (Enero – Mayo 2016)

Este proyecto terminó siendo un juego móvil creado por Gerardo Velasco y yo en la clase de Desarrollo de Videojuegos. El objetivo de dicho juego es hacer la mayor cantidad de órdenes posibles de café antes de que se termine el juego, entre más pasa el tiempo más difíciles se vuelven las órdenes.

Link del juego: https://play.google.com/store/apps/details?id=com.WhiteGirlSquad.TayTayLove

Redes (Enero – Diciembre 2016)

Durante todo el año estuve en dos clases diferentes dew Redes (I y II) en ambas creamos (Gerardo Velasco, Daniel Jimenez, Alfonso Ruiz Velasco y yo) un par de proyectos de los cuales estoy muy orgulloso. Estas fueron una de las clases que más he disfrutado durante mi carrera, por lo que estoy muy emocionado de llevar Redes III durante el verano.

Videos:

Habitioli (Enero – Mayo 2018)

Finalmente, el último proyecto que voy a mencionar es Habitioli, este fue diseñado en la clase de Arquitectura de Software y desarrollado por Gerardo Velasco, Daniel Jimenez, Alfonso Ruiz Velasco, Sebastián de la Hoz, Manlio García y yo. Este proyecto es uno de los más complicados que hemos hecho durante la carrera, pero aún así siento que es en el que más aprendizajes me llevé. Es una app en la que pones cosas que tienes que hacer más hábitos. Fue creada usando micro servicios, por lo que adjunto un link a lo que yo hice:

Frontend-https://github.com/rudylepe5/HabitioliFrontEnd

WiFi on Airplanes

Have you ever used a wifi service while traveling on an airplane? Well, you might not want to do it again after reading this; or if you still really want to do it, I’ll give you a tip on how to be safe.

First of all we can all agree that the speed of the internet is not that good, we can’t really do much with it, it is very basic. But that is not what I’ll be talking about. I’m going to focus in the security of it.

I’ll start with a personal experience, I was flying from Dallas to GDL, just finished my book, and had nothing to do. So I connected to the wifi, but it wasn’t working. Because I was bored, and I had nothing better to do, I decided to see if I could connect to the router. To my surprise I saw that the router administration credentials were: username «admin» and password «admin». I was in pure disbelief, like, how hard is it to just change the password? That was my first try and I got it right.

Once I landed I decided to look up if more people have tried what I have (and yes they did!). And that’s how I stumbled to Shannon McMahon’s article of Why You Should Never Use In Flight WiFi. On it, she touches upon some points, but most important she mentions two things: it is not secure and thus, someone could be watching. And yes, if they are watching you and you log in to something that doesn’t have such great security, they could see your password.

That is also something Michael Horowitz talks about: the security in the planes suck. Horowitz found that the main network is wide open! Imagine, completely wide open. I don’t know why the airlines don’t care enough to put at least something, some kind of barrier, something to avoid others seeing your traffic.

But there is a solution! If you still want to enjoy of some wifi while your flying, there is something you can do to make yourself safe (or at least safe from anyone spying on you on your plane). Getting a VPN and connecting yourself through there. That is something Andy Higgs and Elizabeth Weise talk in details.

If anyone wants some more information about VPNs, here’s a link to Lazaro Cardena’s post about it.

So that’s it, don’t use wifi on planes and if you do use protection!

Have a safe flight.

Trust the Security Experts

The other day I was on Twitter (I’m always on Twitter if I’m being honest) and I stumbled across a rant from Brian Krebs ( @briankrebs ) and oh my! His first tweet was this:

Screen Shot 2018-04-05 at 11.08.34.png

Afterwards he goes on an incredibly long rant about Panera and what they did. If you want to see all the tweets I recommend you go and look at them, I’ll give a brief description of the timeline.

It all started because Brian ran a story about Panera and the leaked customer records. That same day Panera issued a statement to Fox News that the breach only impacted 10k customer accounts. Interesting enough, Panera told Brian they had no numbers for him, that’s when the show started.

Brian then goes to criticize Panera, telling them they haven’t fixed the issue and that the 10k isn’t really 10k, but a number much much higher… somewhere around 37M. The next thing he does is pretty much yell at Panera for not trusting the security experts (a.k.a. people like himself). He then criticizes them a little bit more for not admitting what they did and asking a security expert for help.

The moral of the story is trust the security experts! Don’t downgrade them, don’t think the truth won’t come out, c’mon it’s the internet, everything come to the light at one point or another, if not, ask Cambridge Analytica.

I’m going to finish this blog with something Brian said and companies (or no one really) has to do: «most companies respond to breach notifications like they would a stranger telling them they have a cold sore on their lip». Please don’t be that guy, and Panera, next time don’t mess with Brian.

tumblr_n8eipyPolE1qd9dz2o1_500.jpg

Facial recognition glasses in China

On Monday, China announced that their police will have facial recognition glasses , so that they can spot people traveling under false pretenses, some Chinese media outlet  featured a policewomen wearing a pair of those. This is huge news, because the glasses are connected to a police database that has over 10,000 suspects . And it analyzes everything in under 100 milliseconds. Imagine that, having a pair of glasses (or sunglasses) capable of analyzing such amount of information in such few time. This could very much help when trying to identify suspects with large crowds.

But also imagine if someone puts your picture on the database. That would just be terrible, the police officer would think you’re actually a suspect of something, he/she would arrest you, send you to the police station and wait for everything to be sorted out. Or also imagine if someone spies on the connection between the glasses and the database, and can actually see everything the glasses see, plus all the pictures that are on it. Yeah sure, they were made for helping police officers. But what if the technology gets in the wrong hands, and they create a database of their own, I don’t know, downloading pictures from Facebook, from, let’s say, kids of wealthy people, or them themselves. And they use the glasses on their help on kidnaping someone, so that they can identify the target easily on a crowd. I mean, it is just a thought.

And that is the just the first step on a long road to trying to make the world «safer». The sad part is that all technology that is made for us to be safe can be used against us. But this is not a blog about guns or weapons or anything like that, so let’s get back to security.

What if someone makes the glass see something they didn’t really see? What I mean is this, you’re already tapped in the communication between the glasses and the database, at some point you might change a «No, he is not here» to «Yes! He’s part of the database» and just send a picture of the guy who you want arrested. It is such a wild thought, but it could happen (and it most likely happen in some point of the future).

What would you do if you were wrongfully arrested because of some «glasses» that said you were on their database? I would freak out, because that means they broke into the system. Yeah sure, the officials will say that it was just a malfunction, a misunderstanding, some bug, a flaw on the system. But I would take that with some concern, because they wouldn’t use them unless they were sure that it was almost perfect (it is impossible to have a 100% bug free system). So I would be worried.

But let’s hope it doesn’t get to that, let’s just hope that those glasses bring more good than evil, bring more criminals behind bars, than innocent guys being dragged for no apparent reason. Let’s just hope…

Happy Safer Internet Day!

Today is the Safe Internet Day 2018, and because of that Naked Security posted two articles: one talking about 3 things you can do for your social network, and the other side of the coin 3 things your social network can do for you. On those articles the authors talk about  three important things: 2FA, behaving in the web and logging off.

Two of them are pretty self explanatory. You need to behave while being online, just as you would if you were in the «real world», and the Social Networks should monitor and punish those who aren’t following the rules and standards that are set. Logging off is a concept all of us know, but few people actually follow, must of us (myself included) leave our accounts logged in in our computers/phones/tablets, because it is way easier to just open the app or the browser and be there, there are quite a few reasons why we shouldn’t stay logged in, the first one if someone takes your phone they can just impersonate you, or when you are logged in the Social Networks track your movements around the web; to the Social Networks we ask to make it a little easier to log off to the different apps, so that we can automatically set it to log off when we’re not using it.

The third one, 2FA, stands for Two-Factor Authentication , and it pretty much means to add an extra layer of security. How it works is pretty simple: you add your phone number or there’s an additional app and with that a code is sent to you so you can put in after putting your usual password. With this, hackers won’t be able to access your account even if the have your username and password. The sad part is that not a lot of people know about this functionality, about this way to protect themselves, and that could be because the Social Networks aren’t doing enough to letting users know about it, or they just (the users) don’t care. So I urge the Social Networks to make 2FA default, because let’s be real, it will take you a couple of more seconds to access that code, and with that we are all a little bit safer in this online world.

And that’s it. I’m sure that if we stay here, we can come up with a lot of different ways to make the social networks safer. But that something for another time. For now, let’s go and activate the 2FA in all those places there’s an option to do it (here’s a link to all the sites that have 2FA).

PD: Happy Safer Internet Day!

SID_Thunderclap_(2).png

For more information go to: https://www.saferinternetday.org

Updating is a must.

Earlier this week Brian Krebs published an article about the first «Jackpotting» attacks in the U.S., he mentions that the U.S. Secret Service quietly began letting ATM operators know that their ATMs were being targeted in the United States, for the first time ever. He then goes to talk about how this can happen, but I won’t go in full detail about it. If you want to read all about it I recommend going to his article where he explains everything perfectly. By the end Brian mentions that the reason this hacks were possible is because ATMs were still running on Windows XP, yes the same Windows that was released in 2001, 17 years ago!

This begs the questions: Why haven’t they updated their operating system? Why are they still using a software that was first released so long ago? It’d be as if the download speed of your intent is the same as it was 17 years ago, or if you were still using the same T.V. you bought at the beginning of the millennium.

This+was+my+rich+kid+tv+in+2000+built+in+_471406e1298636884b6482ebd2125064

Yes, this is a TV from the 2000.

Still the question remains: Why not change it? There is no clear action, but I’m sure that it goes along the lines of: «commodity», «I didn’t think they could hack it», «it is too difficult to change it», «it would take too much time and effort». But to that I can just ask: Have you updated the hardware of the ATMs in the last 17 years? Because, if they have, why not do the software too.

And now let me ask you a question: Have you been updating your softwares during the past year, month, week, day? Because if you haven’t, you’re more likely to be hacked. Check your computer, phone, tablet, watch, apps in all your devices, everything that is connected to the internet; go and check if you have it updated to the latest version. If you do, congrats! You’re one step ahead; if you don’t have it go do it, you’ll thank me later.

If you have any question as to how to update anything ask me and I will be glad to help. And remember, always check for updates.

Welcome everyone

Hello! And welcome to this new part of my blogs, in them I will be talking about different  aspects about security regarding the internet, computers, technology in general. If you were looking for something about self defense or that kind of security this won’t be of much help.

I’ll try to post regularly, hope you enjoy the ride with me! Feel free to leave any comment,  I’ll make sure to read them.

PD: I’ll bring back all the GIFs.