Security and STATS (not security stats)

I know this is not the way to start a blogpost, but this post is going to be a long one, and yes, you’ll get a potato. You may or may not know what I mean when saying STATS, for those wondering, STATS is a project where I’ve been working for the last 15 weeks,…

One rule to rule them a… wait… there are three?? (Short talk about Morris’s golden rules and the STATS project )

I know it’s early in the morning, but I felt like writting a little bit, I had this topic as an assignment in university, and I thought about adding some salt and pepper to it, Bob and Alice always like their food with salt and pepper *wink*. Obviously I’m not as safe as one could…

Business + Code of Ethics = Organizational Progress (a guide about what a code of ethics is, and what should it include)

What is a code of ethics? This is probably the reason why you are here. A code of ethics is a document where an organization shows their mission and  values, so other people can see the alignment the organization will take when problems arise, and how is the organization going to approach those problems. This…

CIA (the triad, not the Central Intelligence Agency)

Modern organizations have big amounts of information, information that must be kept safe. There is where the CIA triad comes into play, but, what does CIA stand for, CIA means Confidentiality, Integrity and Availability, and this three concepts are the guidelines for having good information security policies. I think that if you came to this…

Don’t blame your cat, talk to your duck (includes chapter 1 The Pragmatic Programmer | from journeyman to master)

To be a pragmatic programmer you need to approach problems keeping an eye on the big picture, we don’t always have to create the best software, but sometimes we have to, also, sometimes we need to adapt to the changes, but that’s not always the case, the point that I’m trying to get here is…

How pragmatic are you?, introduction

This post is an introduction for “The Pragmatic Programmer” from Andrew Hunt and David Thomas, and the authors said it’s intended for people who want to become more effective and productive programmers. For people who want to do, they stated that this isn’t a theoretical book, but a practical one, a way to gain experience…

Found it (includes chapter 15 Software Project | Survival Guide)

System testing goes almost along construction, as you should make a system test before and after you are trying to integrate new code into the project. But, how can you test your project? If you have been following the guides from chapter to chapter, you should have a user interface and a user manual by…

Build it guys (includes chapter 14 Software Project | Survival Guide)

Construction is the stage where software comes to life. If previous stages have been done well, this will go smoothly, as features are added incrementally, the team should be able to test them and track the progress of the project. The team should keep the focus on simplifying the software. Constructing can either be fun…

Just as a checklist (includes chapter 13 Software Project | Survival Guide)

On this chapter, detailed design was discussed, it can affect the whole project and it extends design work done during the architecture stage. During stage 1, detailed design  requires verifying the quality of the architecture, if it has bad quality, it’s time to correct it. Detailed design also uses a staged approach, at each stage…

Stage by stage (includes chapter 12 Software Project | Survival Guide)

Staged planning is something that is done at the start of every staged delivery cycle, where the project team creates an individual stage plan for each stage. It describes how to conduct detailed design, coding, technical reviews, tests, integration, and other activities. When doing the plan for a stage, use mini milestones, they help you track progress…