In the last 3 days, I have started learning and exploring Python. Many of the webpages said that it is easy to code in Python and the code talks back to the developer when he/she visits it even after a long time in way where the gist is understood within no time.

Below is the link to my git-hub code where i wrote a program that holds an arrays of 4 words and the user has to guess the randomly generated word using the banked-spaces clue. The code is in Python 3.3.4

https://github.com/eshwaryaddanapudi/Python-WordGuess

In the last 2 days, I have got my hands dirty on how to use HTML5, CSS3 and JQuery to do a simple, i mean it, very simple TODO-List using the LocalStorage of the browser.

here is what i have achieved after 2+4 hours of effort in the last 2 days. I will upload the code to Github and share the same with you folks.

trust me, JQuery is awesome with HTML5.

Before we start talking about Agile, I had an interesting talk with my friend about the posts of my blog here. He says that a lot has been talked about code, clean code, best practices, C#, Agile and what not there are too many people with an experience more than my age!!! So he concludes that i was trying to re-invent the wheel.

My answer was simple and straight forward - I understand and I know there are many of them here. Yet, probably I have the ability to put things very simple. I believe that my posts can reach to those who are looking for things that are told in a little easy way.

If we do things which are for a better than the existing one, its always good and its always new. This only means telling the story more cleanly and clearly with a new additions.

See you next week with Agile Methodology :: Episode 5

As part of the agile practice assessment, we group of friends, the other day they had a talk about how we feel and what we feel are good and bad about agile. what we feel are okay and what we feel are awesome about agile in comparison with waterfall model which we practiced previosuly.


So, lets get into the topic.

What I like with agile:

1. As a team, we can pick and choose which tasks to complete first.
2. I have the freedom of talking and sharing with my teammates more.
3. With more talking, we felt it was the ideas of the complete team than just a two or three that counted.
4. We have the best oppurtunity of 2-3 brains thinking on a problem, if we are stuck than a single head hitting on the wall for a solution.
5. Estimation is done based on ME and MY TEAM members abilities and skill sets than just picking up few use cases.
6. Minimum documentation to the level of making the new entrants understand the project.

What I hate/dislike/disagree about Agile:

1. Too much freedom or too much of work as tasks are divided for everyday core working hours.
2. Sometimes, it so happens that everyone is busy with the sprint work that I don't get a dedicated helping team member to solve my problem.
3. Too lengthy retrospective and sprint planning meetings.
4. Continuous work allocated. So taking a leave might turn my next day a nightmare.

Points of conflict.

1. Less scope and more scope for INNOVATION
2. Less documetation is a down side and at the same time an advantage
3. Team talk an advantage as well as a disadvantage.
4. Product owner giving tasks based on sprint length makes us lag on the complete knowledge of the project and the work to be done.


We will talk on some points in depth and touch upon few more in the next episode.

Stay tuned! Stay curious!! Stay Healthy!!!

I think it’s not just right to talk about code and the software practices alone. There is more to this what makes the earlier two things go on and succeed. They are skills of different kind. I know that you guys would have guessed it by now – the behavior skills.

Behavior skills in its own is a very vast subject and more importantly it cannot be taught with a chapter in the book for every situation. However, we can make ourselves go through few leanings and stitch them with our previous experience and make ourselves ready for the best and the worst. And every time, it’s the act as per the situation that makes us more convenient and others in the situation more comfortable. So, let’s jump in, but where shall we start? I have the answer!!! Trust me and follow me here.

The first and the foremost of the Behavior skills (BS) is conversing. I somehow don’t want to take the word communication right away and right here, because it’s again a big topic on its own. When we are at a comfortable place, we will start using the word communication. Conversing is between two or more people and in general on a specific topic. So as far as the subject is concerned it’s easy for everyone in the group. However, for the subject to take a route where it realizes (I dislike the word ends-up, because it’s like a narrow mind thought)to become a fruitful discussion is when everyone puts in their thoughts on the subject matter.

But what it takes to make everyone their thought? It’s all about a simple practice of listening to the one who is talking/speaking and the rest giving the full levels of dedication to the one talking. This makes the complete circle of conversing. Yes, A complete life cycle of conversation (sounds pretty similar to SDLC?).

So, we shall put a full stop for this point here and come back with a new line in the next post. Thus, it’s very important that we listen to someone who is talking in the group while we are in discussing, because you might never know that a person who hasn’t spoke at all has a better idea than the rest of the team. See you soon!

Hi guys,
Wish you and your dear one's a wonderful new year- 2014 ahead.

Continuing our abilities in trying to bring the best of us using our code, we are in the 3rd episode of this. This time around, we will discuss how we can make our code get rid of the red lines.
Red lines? Yes, the hard coded text in C# is in general in red color and so we call it the Red-Color-Phobia.

Red-Color-Phobia.

Many developers have this tendency of hard coding few values, during the process of assigning things, comparing things or while retrieving things.

Example 1:
Say, there is a requirement for an online shopping portal where in, based on the current location of the active customer, a surprise discount percentage has to be offered during the Thanks Giving time.

The developer/ programmer has written this to achieve the requirement.

Var cutomerSurpriseDiscountPercentage=0; Var customerLocation = string.Empty; If(customerLocation == “New York”) {        cutomerSurpriseDiscountPercentage = 10; }

How can we better this code?

Define an ENUM that holds the names of the locations to which the surprise discount s available

enum ValidSurpriseDiscountLocations{ NewYork = “New York”, Detroit, NewJersy = “New Jersy” }

Thus, our code is little modified for a better quality

Var cutomerSurpriseDiscountPercentage=0; Var customerLocation = string.Empty; If(customerLocation == ValidSurpriseDiscountLocations. NewYork) {        cutomerSurpriseDiscountPercentage = 10; }

See you again.

All right, the name says it all. Magic by a programmer? It's all about magic a programmer can do in his/her day-to-day activities.

Here on this page, we together will talk, share, discuss, learn and gain knowledge on how we can better ourselves as a developer and as a programmer.

We shall start our journey with a little sweet talk on "how we can make our code talk more"

So, stay tuned.