Comments for Finalint

Comment on How To Get Empathy To Connect To Google Apps Chat by Ash

Ash — Mon, 30 Aug 2010 07:30:57 +0000

Hey,

Thanks for the info. This is what I was looking for, and I’m now connected. :) Cheers

Comment on Google Calendar .NET API – HTTP 417 Error by umar

umar — Wed, 25 Aug 2010 11:48:14 +0000

WOW thats gr8…………. thanks for sharing

Comment on 10 Ways To Suck At Programming by philip

philip — Tue, 17 Aug 2010 16:20:21 +0000

html isn’t programming.

Comment on 10 Ways To Suck At Programming by Donnie

Donnie — Fri, 16 Jul 2010 16:31:24 +0000

Ouch… you’re right. I’ve run into that plenty of times. “Why won’t this STOP BEING BOLD!” hahaha… good one. :)

Comment on 10 Ways To Suck At Programming by Jeff Dickey

Jeff Dickey — Fri, 16 Jul 2010 16:05:14 +0000

What’s even scarier is that the company that shipped that app is still in business and working on a new version.

Comment on 10 Ways To Suck At Programming by flashmac

flashmac — Fri, 16 Jul 2010 15:47:15 +0000

You forgot ‘use tables whereever possible’!

Nested tables are in every front room and they should be in your webcode too. If your feeling really hard core, you can use inline styles too. Nothing beats working on a site with 17 nested tables all with inline styles. They will thank you for ever.

Comment on 10 Ways To Suck At Programming by Mad Max

Mad Max — Tue, 15 Jun 2010 16:35:04 +0000

You’d be surprised, but they tend to cling to their jobs–and often survive while more competent people are let go.

I remember a project at a major software company which had never generated any revenue, and it had been around for 20 years. Every year, their manager was the first to run to his pals in higher management and ensure the project would survive one more year; other projects–like the one I was working on, with a large client base–were frozen instead…

Comment on 10 Ways To Suck At Programming by Mad Max

Mad Max — Tue, 15 Jun 2010 14:50:05 +0000

I’ve actually worked for a company where comments in code were discouraged by the project lead… We took over the application, then started to modify it–and were the *first* to introduce both source control and code comments. The trouble was that the original code was unreadable–and we were expressly told that “if it ain’t broke, don’t fix it…”

To make a long story short, we ended up rewriting almost ALL of the code–after trying to follow company policy and modify unreadable code, and wasting untold hours in the process…

Comment on 10 Ways To NOT Suck At Programming by квадроцикл

квадроцикл — Tue, 15 Jun 2010 13:22:11 +0000

Why is it that humans can move their eyes in opposite directions toward the nose, but not away from the nose?

Comment on 10 Ways To Suck At Programming by Phil

Phil — Sun, 13 Jun 2010 18:22:36 +0000

Be sure to locate a client that does not deal regularly with software (possibly a hardware company that just needs some demos and SDKs for their new hardware/chipsets), then when it comes time to deliver just completely ignore that clause in your contract that requires source code and send them a DLL that presents only the methods used by your GUI. Now you’ve completely removed the ability for the client to bring someone in to fix your code… because it is not there. Additionally, you can reduce your documentation tasks because you just have to document how each method gets wired up to your buttons and textboxes. On the plus side, the next developer will love you, because they can immediately set the expectation that everything must be rewritten from scratch because the last contractor they hired didn’t deliver on their contract. If everything goes according to plan you will be paid before the next developer shows up and writes 25 pages of documentation stating everything that is wrong about your 10 page documentation, and a critisizm about how a compiled binary doesn’t qualify as source. But none of this matters because you’ve already been paid so you can completely ignore the client :) Life is good.