Hi

First thoughts about 70-536

I have been more than 3 years after school in software development, major in web development. Most of the time dealing with business logic. And i have been reading lots of articles, books about TDD, DDD, Design Pattern and other programming methodologies.

It has been good as it has since nowadays we are dealing with solving the business needs and logic.

And one day, i decided to start training kits from MS to get MCTS certificate. Getting into the book designed for foundation knowledge i was so surprised: Too many things i really do not know, or aware of.

Here are some thoughts about reading it:

Firstly, reading that book is quite interesting and useful. However to remember them is not an easy task. It reminds me the time of being at high school 🙂 And, of course, there are some chapters i am not interested in like: Graphics, Installing and Configuring Applications, … Why? How often will i use them?

Secondly, It makes me confuse of what i should focus on. Not exactly that but quite pretty much. The thing is that i am lacking of real practical reason of remembering them. Whereas i can google for it.

Btw, i am going to finish the very first exam. So, any advices please let me know.

Do we need code review?

What is the code review? Simple as its name: Do the review after coding done of a project, feature or just a task. At my company, Catglobe Vietnam, we usually do that, and it is a MUST. PM or TL will do that job.

I was surprised once i asked my friends: How was that going in your company? Got the same answer: No we did not do that stuffs. The first thought came up in my head was that the company is an outsourcing and they do not care much about the quality of code, just passing test is enough to hand over to the client. However, not only that kind of company; company owned the code, call code base, also does the same thing.

How can they build up a good software without reviewing the quality of code, coding style,… ? Being asked that question, they said that: out of resource.

I wonder how many companies really take  care of code review while developing???

Maybe an idea of a code review company ….

Just Finish It: JFI

I really like this term.

Why??

Watching some movies, especially about soldier, they usually take responsibility for what the upper asks them to do. They try to finish it, get it done no matter what happen, sometime they risk their life.

Going into Agile world, in development software, i have seen the “DONE”, pretty much the same meaning of JFI.

It makes me think of my life and others, what they have done, they said: I finish it, it is done, but in fact it does not.

Example???

Going down the street, how many constructions say they’re done? A lot, and nearly all. But look at the street, how does it look like after that?? Terrible.

Going into software development, given a task, how many things left after you said it is done? -> This one was from my experience.

So, what all those things mean? is it better if we develop a habit of getting something, a given task, things we are responsible for, done: JFI

OMMM preview

It has been more than 9 months since the last OMMM ( One Minute Manager Management) meeting. It is quite a long time for a meeting period since we have many things to do in that, delay of release, economic recession, …

Forget all of them, i come into the meeting, just a few worlds after that. The result is not bad, can be called: accepted however, there are something left with the feeling.

The good news were that i have had some new good goals. The bad news is when will the next OMMM meeting be?