Comments on: 10 Ways To Suck At Programming http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/ So says Donnie Garvich Sat, 11 Feb 2012 09:58:46 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: em http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-965 em Thu, 17 Nov 2011 06:03:20 +0000 http://www.finalint.com/?p=133#comment-965 Yeah, make sure you do a side project for an important client. Do not check your code into source program. Get mad at the mgt, give your two weeks and neglect to tell the other programmer what you were doing, why you were doing it, and where the f***** source code is. You should add insult to injury and leave about 20 folders that have no naming relation to the actual project with various file dates that sometimes align when the stars are right so the next guy working on your sh*t has to build all 20-30 folders looking to find the gold standard you dropped on the clients machine... Yeah, make sure you do a side project for an important client. Do not check your code into source program. Get mad at the mgt, give your two weeks and neglect to tell the other programmer what you were doing, why you were doing it, and where the f***** source code is. You should add insult to injury and leave about 20 folders that have no naming relation to the actual project with various file dates that sometimes align when the stars are right so the next guy working on your sh*t has to build all 20-30 folders looking to find the gold standard you dropped on the clients machine…

]]> By: Bookmark Service http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-952 Bookmark Service Fri, 26 Aug 2011 19:42:38 +0000 http://www.finalint.com/?p=133#comment-952 <strong>Bookmark Service...</strong> 10 Ways To Suck At Programming | Finalint... Bookmark Service…

10 Ways To Suck At Programming | Finalint…

]]> By: The Open Source U » 10 way… http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-891 The Open Source U » 10 way… Fri, 10 Dec 2010 20:39:15 +0000 http://www.finalint.com/?p=133#comment-891 [...] http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/ [...] [...] http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/ [...]

]]> By: philip http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-876 philip Tue, 17 Aug 2010 16:20:21 +0000 http://www.finalint.com/?p=133#comment-876 html isn't programming. html isn’t programming.

]]> By: Donnie http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-865 Donnie Fri, 16 Jul 2010 16:31:24 +0000 http://www.finalint.com/?p=133#comment-865 Ouch... you're right. I've run into that plenty of times. "Why won't this STOP BEING BOLD!" hahaha... good one. :) Ouch… you’re right. I’ve run into that plenty of times. “Why won’t this STOP BEING BOLD!” hahaha… good one. :)

]]> By: Jeff Dickey http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-864 Jeff Dickey Fri, 16 Jul 2010 16:05:14 +0000 http://www.finalint.com/?p=133#comment-864 What's even scarier is that the company that shipped that app is still in business and working on a new version. What’s even scarier is that the company that shipped that app is still in business and working on a new version.

]]> By: flashmac http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-863 flashmac Fri, 16 Jul 2010 15:47:15 +0000 http://www.finalint.com/?p=133#comment-863 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. 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.

]]> By: Mad Max http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-1/#comment-856 Mad Max Tue, 15 Jun 2010 16:35:04 +0000 http://www.finalint.com/?p=133#comment-856 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... 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…

]]> By: Mad Max http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-855 Mad Max Tue, 15 Jun 2010 14:50:05 +0000 http://www.finalint.com/?p=133#comment-855 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... 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…

]]> By: Phil http://www.finalint.com/2010/05/04/10-ways-to-suck-at-programming/comment-page-2/#comment-852 Phil Sun, 13 Jun 2010 18:22:36 +0000 http://www.finalint.com/?p=133#comment-852 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. 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.

]]>