Is the Daily Stand-Up meeting important?

I would like to share my thoughts about Daily Stand-up meetings in agile development.  I am going to touch on advantages/disadvantages without going into detail.

If you're familiar with Scrum, you probably heard 'Daily Stand-up Meeting' before. Even though I have a bit more than 1 year of experience as an Intern Student at startups, I can say that these daily magical meetings bring you adequate work environment. Let's look at why is it good for companies? Basically, meetings mean communication that means the key to the progression so then the company can go forward. Taking action is always an important matter in life as well as while developing a project. Making these meetings are important because this a time that the whole team is together so the team can argue what was the outcome and where we are now in terms of product. The result can give the best possible output. Actually, this is one of the cycles of the agile methodology. It can carry you to the next level.

Basically following lines are important:

- What did you do yesterday?
- Have you done something or do you still continue to work?
- Did you encounter any problem while you were doing it?
- What are you gonna do today?

When your turn comes up, just say basic things. Force yourself to be up and tell them your speech. Don't say very complex sentences because this is not a competition and time is valuable. If you have trouble with something, tell them and maybe they know the solution. You should also say if you comment something or rename a function name.

Let me know if it makes sense to you, leave a comment.

Read More

Software: Naming requires creativity

In this first blog post, I am going to focus on naming variables/functions in software development. Why I want to talk about this is I was listening podcast and there were lots of ideas that make me think deeply about naming. You can check it out the podcast from this link: http://www.se-radio.net/2016/12/se-radio-episode-278-peter-hilton-on-naming/ I highly recommend listening to this podcast.

Let's go ahead through the important bits that run into as I was listening podcast.

Peter Hilton is a writer, and British mathematician he wrote 'Play for Scala' book which is very famous when it comes to web development on PlayFramework/Java.

It was fun to listen because the first question asked by the interviewer is that why naming is so hard? It must be quite straightforward because this is just naming something and the answer was also surprising given by Peter Hilton. Naming is one of the hardest things in software development like validation and caching.

He was saying that naming is an important subject and one of the most challenging thing that you might come across when you build the software systems. It requires creativity. When you create a variable you have to think a bit about the words. The code is for human communication as well as machine communication.

For instance, when you name a function it must be summary of the function. You shouldn't use popular words like Get something or DoSomething because function aims to make something actually. I wanna get the data from somewhere FetchWeatherData, Calculate/Divide are better options instead of using GetSomething. You should avoid using data as well because basically everything can be a data and it is not clear what you mean. Reasonable naming does your code seems like a poem in terms of readability.

Another thing that he was saying that it's better to name in time. Renaming might be harder than name something, in that case, we should think about naming as much as we can do. I think

The idea that sums up the entire text is that you need to think twice when we name something.

So, what do you think?  Any idea is welcome.

Suggested book:

https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882 / Clean Code from Uncle Bob. It has a chapter named Naming for further information.

Read More