My Thoughts & Views

Archive for the ‘how to’ Category

Here is the list of tips & insights compiled from StackOverFlow.


1. Never be afraid to say I don’t know.Manage expectations, learn to say “no”.But always give it a try before you say that.
2. Never stop learning.Accept your mistakes and take that just as a new learning opportunity
3. Ask for help sooner rather than later,know that you can’t do everything by yourself.Don’t take all the responsibility for a problem. Sometimes you can be furiously trying to solve a problem alone and carrying the problem on your back. Get other people involved, escalate, get other folks involved.
4. Learn to take backup
5. Assumption is the mother of all screw-ups. So never assume something which you are not sure of.
6. Estimates are always off by at least 50% either way.
7. First make it work, then make it better.
8. Always negotiate deadlines/deliverables.
9. Don’t hesitate to do overtime IF the situation requires it
10.Underpromise and over deliver
11.Find the balance between being realistic and being positive.
12.Be confident in your skills
13.Listern patiently to others opinion. Especially when you talk to a client.
14.Share your skills – Help others and the community with the knowledge you’ve got.
15.Make sure you get proper recognition and appraisal for your good work.
16.Manage your time effectively
17.Don’t give people what they ask for, give them what they need.
18.No matter where you are on the pecking order of a team or project, you CAN make a difference.
19.It’s more important to manage people’s perception of the problem than it is to fix it.
20.Never trust the data. Validate your inputs.
21.”It works on my machine” doesn’t cut it. It HAS to work for them, too.
22.Show your code to other people – and listen to their comments.& Look at other peoples code and talk to them about it.
23.If you can’t figure out a problem then take a break and come back to it in 10 or 20 minutes – makes finding a solution so much easier.
24.Realize that specifications are going to change.
25.Never implement new features unless you have a written request ( mail is just fine )
26.Be prepared to reinvent yourself every five years.
27.Before you roll anything out TEST TEST TEST
28.Use Source Control
29.Communicate, communicate, communicate
30.You can never have enough clarification and detail with project requirements

Advertisements

I came across this wonderful site called Forvo where you can find the pronunciation of certain words and also you can add a word (your native language) and pronounce it.

Here is the list of tips & insights compiled from StackOverFlow.


1. Never be afraid to say I don’t know.Manage expectations, learn to say “no”.But always give it a try before you say that.
2. Never stop learning.Accept your mistakes and take that just as a new learning opportunity
3. Ask for help sooner rather than later,know that you can’t do everything by yourself.Don’t take all the responsibility for a problem. Sometimes you can be furiously trying to solve a problem alone and carrying the problem on your back. Get other people involved, escalate, get other folks involved.
4. Learn to take backup
5. Assumption is the mother of all screw-ups. So never assume something which you are not sure of.
6. Estimates are always off by at least 50% either way.
7. First make it work, then make it better.
8. Always negotiate deadlines/deliverables.
9. Don’t hesitate to do overtime IF the situation requires it
10.Underpromise and over deliver
11.Find the balance between being realistic and being positive.
12.Be confident in your skills
13.Listern patiently to others opinion. Especially when you talk to a client.
14.Share your skills – Help others and the community with the knowledge you’ve got.
15.Make sure you get proper recognition and appraisal for your good work.
16.Manage your time effectively
17.Don’t give people what they ask for, give them what they need.
18.No matter where you are on the pecking order of a team or project, you CAN make a difference.
19.It’s more important to manage people’s perception of the problem than it is to fix it.
20.Never trust the data. Validate your inputs.
21.”It works on my machine” doesn’t cut it. It HAS to work for them, too.
22.Show your code to other people – and listen to their comments.& Look at other peoples code and talk to them about it.
23.If you can’t figure out a problem then take a break and come back to it in 10 or 20 minutes – makes finding a solution so much easier.
24.Realize that specifications are going to change.
25.Never implement new features unless you have a written request ( mail is just fine )
26.Be prepared to reinvent yourself every five years.
27.Before you roll anything out TEST TEST TEST
28.Use Source Control
29.Communicate, communicate, communicate
30.You can never have enough clarification and detail with project requirements

1. Open Visual Studio
2. Go to Tools > Options
3. Check Show all setting check box
4. Select Projects and Solutions from the tree
5. Check “Always Show solution” checkbox

6. Click Ok
7. Now Select Create New Project
8. From tree List select Other Project Types
9. Then Visual Studi Soultions, You will see Blank Solution in Templates section.


Problem

1. You download a file through some Torrent Client like BitComet, it shows 100% but you can’t open the file.

2. There is .BC! file in your system after Torrent download, which you can’t open simply by renaming.

Reason : Because of missing/corrupt file pieces ( technically IP packet corrupt/missing) you can’t open the downloaded file even after it says 100%.

Solution : All the Torrent files are signed with a Hash key, which helps in identifying the integrity of the file. Also you can go to “piecegraph” the file is 100% finished but still green and red dots instead of all blue. This indicates the pieces are missing or corrupt.

Below steps apply to BitComet, but the same concept can be applied with other Torrrent Clients as well.

1. Once the Client shows 100% Right click on the Torrent Task 
2. Select Manual Hash Check
3. Torrent Client checks the hash again with the original Hash key 
4. If it finds Hash Key mismatch it will again Requests the missing pieces
5. After missing/corrupt file download the Client shows 100%
6. Now you can open it.

Hope this helps.

Following are the tutorials i hope are good to learn ASP.NET.

1. http://msconline.maconstate.edu/tutorials/ASPNET20/default.htm
2. http://www.asp.net/learn/

Will keep posting such useful stuff whenever i find.