So I caught the last few minutes of the Phoenix/San Antonio game last night. That was a big time statement game for the Suns. They had every reason to fold down the stretch; but they didn’t. They were down by 10 in the 4th qtr @ San Antonio; but still ended up winning the game. That game could change the whole momentum of the series. If they had lost last night and gone down 3-1; it would have been very tough to beat the Spurs 3 times in a row. But now; they have a very good chance.. and homecourt advantage. And who knew Robert Horry was such a dirty player. That was very surprising to see what he did to Nash.
May 15th, 2007
(Read that Title once again). Statisfied is one of the coolest new web services to hit the internet this week. It is such a cool/simple concept; yet it is very useful and not to mention addicting. Basically it allows you to see the visitors to your site visually on a Google Map. I just set it up this morning. All I have to do was insert 2 lines of javascript into my website. Check out the global reach of SaddeGeet
May 2nd, 2007
Last night I added a new feature on SaddeGeet. I had always wanted to add a way to see how many people are on the site right now. Last night; I found a really good tutorial on how to do that. It was very very simple. Now when you go to SaddeGeet.com; look in the navigation bar on the left hand side. It should show you how many people are on any page in SaddeGeet.com domain right now. There is room for improvement; because I can technically do it per page. So you can see how many people are viewing newest videos, how many are viewing popular videos etc. I will save that for another day.
LinkToTutorial
March 17th, 2007
According to CNN; the best job in America is a ‘Software Engineer’. I, being one myself, have to agree. The only thing that sucks about it is the ‘occasional’ long hours and the stress that comes around release time. Other than that; its the best job. You get to make your own schedule, you can work from anywhere, and you are given a licencse to really unleash your creative skills while desiging the new software.
For me, there is a big difference between a Software Engineer, and a ‘coder’. A ‘coder’ is someone who is given a task, and has to write the code to implement that task. A Software engineer, I think, is someone who is in charge of developing frameworks, APIs that help these coders do their job more efficienctly. A real Software Engineer would spend more time analyzing the requirments, analyzing the business needs, doing forward thinking than writing code. The best example I can give is the ‘Microsoft ADO.net framework’. In my mind, the real Software Engineer are the ones who wrote that framework; not the ones that use that framework in their application. If you think of it in those terms; you see the prestige that comes along with being a Software Engineer.
From CNN
Why it’s great Software engineers are needed in virtually every part of the economy, making this one of the fastest-growing job titles in the U.S. Even so, it’s not for everybody.
Designing, developing and testing computer programs requires some pretty advanced math skills and creative problem-solving ability. If you’ve got them, though, you can work and live where you want: Telecommuting is quickly becoming widespread.
The profession skews young — the up-all-night-coding thing gets tired — but consulting and management positions aren’t hard to come by once you’re experienced.
What’s cool Cutting-edge projects, like designing a new video game or tweaking that military laser. Extra cash from freelance gigs. Plus, nothing says cool like great prospects.
What’s not Jobs at the biggest companies tend to be less creative (think Neo, pre-Matrix). Outsourcing is a worry. Eyestrain and back, hand and wrist problems are common.
Top-paying job Release engineers, who are responsible for the final version of any software product, earn six figures.
Education Bachelor’s degree, but moving up the ladder often requires a master’s.
April 12th, 2006
I am a software engineer by profession; so its natural that I post about some programming topics every now and then. In this particular one; I discuss an approach to hide your implementation details from the end users of your C++ objects.
Continue Reading April 5th, 2006
We are going to be starting a new project at work this quarter. This is going to be a huge project with 4 developers working on it (2 of them full time). One thing we are trying to do is to come up with some coding guidelines so that the final product is consistent. I am in charge of putting together a list of these coding standards so that we can all agree on them. Here is the initial list that I came up for C++ Include files .
Guidelines
-
The name of the include file must match the name of the class.
-
Make an attempt to hide all private member variables and functions inside the d ptr. Your include file should only public interface.
-
The include file must not contain any implementation details of the d ptr of a class.
The only mention of the ‘d ptr’ should be as a private variable of the class and as a forward declaration.
-
Do not include any more files than you absolutely need. Make use of forward declarations as much as you can.
-
For access functions; use the ‘get()’ and ’set()’ naming notation.
-
getBalance, setBalance, getName, setName etc.
-
Name of include guards should be all caps.
- The class hierarchy should be defined in terms of most accessible and least accessible functions.
So this is the 1st draft that I have put together. What do you guys think? Are there any that you disagree with? agree with? What are some that you use in your projects?
April 4th, 2006