I started a brand new project in CDT where I was using MOOS and I could not get my simple program to link. While everything looked fine on the surface I just could not get the IDE to link to the MOOS libraries. I know the OS and MOOS itself was not a problem as I had other projects in the same workspace which did link correctly. The only difference between those and this was that I setup this project from scratch, whilst the others I had not. It took me a while to figure it out, but in the end I had to resort to explicitly add the locations for the libs in the C++ project properties in CDT as shown in the screenshot below.
To get this this, you right click on the Project name in Project Explorer in CDT. In the C++ Linker section then explicitly add the two paths shown in the screenshot. I of course had MOOS installed in the default location (binaries are in /usr/local/bin and libraries in /usr/local/lib). So even if you have added paths to CDT and still getting linking issues, I suggest you add it explicitly to the C++ properties.
If you are newish to Linux (like me) from Windows, then some of the simple things which come quite naturally to you on Windows is a little embarrassing and challenging.
For example, I got a new WHS and wanted to mount the music drive and wanted to create a new host file entry to point to the new WHS. Now on Windows this is quite simple and can be found in YOUR-OS-DRIVE\Windows\system32\drivers\etc\hosts. But on Linux you will find this in \etc\hosts. If you want to edit it you will need to type something like this a shell:
sudo gedit /etc/hosts
sudo is required as you need admin privileges to modify the file. gedit is the graphical editor; you can replace that with another editor of your choice.
Understand and accept that you will make mistakes. The point is to find them early, before they make it into production. Fortunately, except for the few of us developing rocket guidance software at JPL, mistakes are rarely fatal in our industry, so we can, and should, learn, laugh, and move on.
You are not your code. Remember that the entire point of a review is to find problems, and problems will be found. Don’t take it personally when one is uncovered.
No matter how much “karate” you know, someone else will always know more. Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it’s not needed.
Don’t rewrite code without consultation. There’s a fine line between “fixing code” and “rewriting code.” Know the difference, and pursue stylistic changes within the framework of a code review, not as a lone enforcer.
Treat people who know less than you with respect, deference, and patience. Nontechnical people who deal with developers on a regular basis almost universally hold the opinion that we are prima donnas at best and crybabies at worst. Don’t reinforce this stereotype with anger and impatience.
The only constant in the world is change. Be open to it and accept it with a smile. Look at each change to your requirements, platform, or tool as a new challenge, not as some serious inconvenience to be fought.
The only true authority stems from knowledge, not from position. Knowledge engenders authority, and authority engenders respect—so if you want respect in an egoless environment, cultivate knowledge.
Fight for what you believe, but gracefully accept defeat. Understand that sometimes your ideas will be overruled. Even if you do turn out to be right, don’t take revenge or say, “I told you so” more than a few times at most, and don’t make your dearly departed idea a martyr or rallying cry.
Don’t be “the guy in the room.” Don’t be the guy coding in the dark office emerging only to buy cola. The guy in the room is out of touch, out of sight, and out of control and has no place in an open, collaborative environment.
Critique code instead of people—be kind to the coder, not to the code.As much as possible, make all of your comments positive and oriented to improving the code. Relate comments to local standards, program specs, increased performance, etc.
Now, I don’t know if this is true and how much of this is true; but if I was working for Facebook then all of this is quite logical and makes sense. And, technically all the things talked about is very feasible and not too challenging (of course am over simplifying here).
I do have to admit that the perf and scalability challenges are quite interesting and would love to sink my teeth in it – I guess I need to look at PHP first. 🙂
Wow it has been a while since I posted an Interesting find and instead of the usual list I though I will keep this especially for timers. Timers Galore!
So I was looking for a simple countdown timer that I can run on my laptop to keep tracking of a few things and I found a few very interesting things.
If you prefer to download an app and run it from your desktop (Windows) then check out Timer from Orzeszek. There are a few other interesting dev projects there such as transferring large files over http.
If Windows is not your flavour of the day, or you don’t want to (or can’t) install an application and want to use a timer in a browser you can of course use something like online stop watch, but I suggest you check out e.ggtimer.com which is way cooler.
If you are like me and when running meetings or presenting tend to get too excited and run over, then maybe NextUp is the thing for you.
And if coffee is your not cup of tea (groan! :)) then check out Steep.It which is claims to be the simplest internet tea timer ever – telling you how long to steep your tea to get your perfect cuppa.
And if you are old school and prefer .ini files (whoa! programs still use that?) then check out eggtimer.