Skip to main content

Tips & insights for programmers

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


Comments

Popular posts from this blog

How to Install Hadoop (2.7.3) on Ubuntu (16.04 LTS)

As I am planning to learn Hadoop, I wanted to install Hadoop (2.7.3) on my Ubuntu (16.04 LTS) and I followed the steps mentioned in the documentation on the Apache Hadoop website. I encountered few problems which are mentioned below, spent some time finding solution to them.

Below are the steps I followed and the description of the error is at the end of this post and also I have mentioned what I missed and what caused these errors.


Step 1. Download Hadoop installation file. For Hadoop 2.7.3 version I used the following link 

http://www.apache.org/dyn/closer.cgi/hadoop/common/hadoop-2.7.3/hadoop-2.7.3-src.tar.gzStep 2. (Assuming you have downloaded the file into /home/<username>/Downloads folder

$ tar zxf hadoop-2.7.3-src.tar.gz
This will extract the files into a folder  "hadoop-2.7.3" .

Step 3. I moved the file to /home/<username> folder (many suggest to move it into /usr/local but I prefer to keep it here, may be once I learn more about linux I might get into tha…

Installing Adobe Reader on Ubuntu 16.04 LTS

Adobe stopped Adobe Reader support for Linux so it is bit of a challenge to find and install the Adobe Reader for Linux. Here I describe how to install it on Ubuntu 16.04 LTS.

Step 1. First install gdebi

sudo apt-get install gdebi
Step 2. Install required libraries

sudo apt-get install libgtk2.0-0:i386
sudo apt-get install libnss3-1d:i386
sudo apt-get install libnspr4-0d:i386
sudo apt-get install libxml2:i386
sudo apt-get install libxslt1.1:i386

Step 3. Download the Adobe Reader DEB package

Adobe Reader 9.5.5 enu

Javascript KeyCode Reference table for Event Handling

The post explains Keyboard event handling using javascript.Javascript events are used to capture user keystrokes. Below is a table of key codes for the keys on a multimedia keyboard. If this table is inconsistent with your own findings, please let me know.

Java Script Code to Find Key code

<script language="JavaScript">
document.onkeydown = checkKeycode
function checkKeycode(e) {
var keycode;
if (window.event) keycode = window.event.keyCode;
else if (e) keycode = e.which;
alert("keycode: " + keycode);
}
</script>


Key Code Reference Table
Key PressedJavascript Key Codebackspace8tab9enter13shift16ctrl17alt18pause/break19caps lock20escape27page up33page down34end35home36left arrow37up arrow38right arrow39down arrow40insert45delete46048149250351452553654755856957a65b66c67d68