News for hackers. Stuff that matters.
Re:The shittiest project I ever worked on by redact207 on Wednesday September 25, 2013 @12:02AM (#6442549)
Although it's a fun read, it's a classic example of diving into coding without giving a project it's due diligence. There's nothing that's derailed my projects more consistently when I started out as not understanding the user's needs. They'll never tell you what they want, only what they don't want after you deliver something.

I think that's the key difference to an experienced dev/BA. One who can actually sit with the stakeholders and build the system on paper and go through each of the problems as the diagrams connect. What you end up with is the stated requirements (tip) and the unstated assumptions (iceberg).

These types of projects are easily spotted as they're often called "quick" or "easy", which in layman's means no one's really thought about it yet.

Re:The shittiest project I ever worked on by shailesh on Wednesday September 25, 2013 @03:20AM (#6443135)
Kind of agree with you and OP, so let me add to the discussion with the caveat that YMMV etc. Some of these points may overlap with comments by fellow HNers in these threads.

In any organization as a prospective customer, there are three forces at work that matter to a consultant: users, decision makers and finance folks. Ideally, the decision makers appoint a dedicated person (or team) who mediates users and finance guys to create a coherent road map for the system to be built. What tends to happen in practice is a combination of chance, human errors and conflicts in priorities.

To survive, we must understand ourselves as consultants, the terrain and the opposing forces (anything that prevents money getting deposited in the bank).

Consulting is a business => the individual consultant must shoulder quite a lot on himself:

* Advertising himself

* Finding work

* Meeting prospective customers

* Writing proposals

* Closing the deal

* Writing a contract

* Defining the scope of work

* Nailing what is to be done and what is to be avoided

* Constructing components of software

* (In worst cases) baby-sitting customer's devs / ops

* Testing his modules

* Getting money in his account

So, when we talk with customers, there is inherent pressure in closing the deal versus precisely defining everything. Icing on the cake: back of the mind, you might worry about milkman's bills and the birthday gifts to be brought for your kid's friends. Always have a good runway: six months seems optimum. Technically, even three months should suffice, but it is insufficient for the edge case when these three things hold true simultaneously:

* You've to walk away from a customer in the middle of a project, and

* Dry sales pipeline, and

* Unexpected crisis at the personal front: very close friend in need of money for surgery etc.

God be with you.

Now, back to the main track. The key is to first understand the priorities of stakeholders. The contradictions are easier to grasp once we put ourselves in the individual's shoes:

* [Convenience] The users want everything including the kitchen sink,

* [Accountability for the risk] They want it yesterday but won't commit to it on paper since you're in early sales stage,

* [Cost] The finance folks want stability and the most economical price,

* [Availability] The decision maker prefers to spend the least of her time to be spent on this activity, except when it's her pet project.

These roles may be played by different people or the same person.

Again, we don't have to agree, but acknowledge that things are meant to be imperfect. Most people are actually decent and rational. Now, somehow, the consultant must figure out a good path. To begin, he should have a good handle on:

* The industry in which the customer operates, e.g. BFSI, Energy, online marketplaces, food, fashion etc.

* The nature of the market: oligopoly, crowded, emerging et al.

* The level of Govt. regulation: HIPAA? PCI?

* The customer's position: among top tier, mid-size, small firms.

* Customer's customers: helps to track the wind.

* Standard pain areas in the market.

* How customer's competition and partners survive the pain, specifically the differences among the customer's approach and the competitor's ones.

* The financial health of the customer: if possible, try to talk with their existing suppliers in other arenas (e.g. the guy who supplies printer cartridges, the cleaning lady etc.).

Based on that, assuming we've landed a hot lead, say that we want to convert it to money. There will be a lot of conversations over the phone, e-mail, chats, face to face; what is to be left out of those conversations is really context sensitive. The important parts are:

* What problem we're going to solve for all stakeholders?

* How we're going to solve it?

* Communicating our approach and progress on a timely basis.

* Improving Vulcan skills: like money, expression of anger is a great servant but a terrible master.

I leave out the details on the development process, since it depends on the individual.

Here are a few things which worked for me marvellously in certain contexts and doomed in others:

* Setting expectations by explaining the cone of uncertainty in the estimation process. Always be prepared for some customers, who deliberately mislead you that they don't understand the mumbo-jumbo, projecting ignorance as a shield so that they can ruin you on payments. Mostly you should refuse such customers, unless you're in an extreme crisis on multiple fronts.

* Writing use cases for the modules / systems I was supposed to work. Most customers say that they don't want any time spent on "documentation," to which I reply that writing a document is not "typing" but "nailing the thoughts to deliver higher quality work."

* Creating mock ups using sketching tools (even Excel/LibreOffice can be good enough, if one is pressed too much for time) in the absence of UX designers on the team.

* Writing test cases before writing my code. Helps to ease the integration.

* Optimizing lazily: progressively refining the artefact (document / mock up / test / code).

* Knowing the expected value of each task: (amount of money * satisfaction * improvement in reputation) / (e-mail tennis * stakeholder's understanding of requirements * payment latency * time spent)

Finally, reducing it to just one sentence: be nice, believe in yourself and humanity, be multi-dimensional and please heed Guy Kawasaki's advice about reading voraciously and omnivorously.

Edit: formatting.

Re:The shittiest project I ever worked on by zenshade on Wednesday September 25, 2013 @11:41AM (#6445226)
I rarely comment here, but your excellent post deserves to be recognized. I'm someone who has thought a good deal about starting a consulting company but never managed to convince myself the risk/reward numbers would work for my life situation. Your richly detailed and honest perspective is much appreciated. Thank you.
Re:The shittiest project I ever worked on by shailesh on Wednesday September 25, 2013 @11:13PM (#6448724)
Your words widened the smile on my face. I agree with you about the risk/reward numbers.

Should you be comfortable, I'll be very glad to keep in touch with you. My e-mail is on the GitHub profile.

Re:The shittiest project I ever worked on by ryan-allen on Wednesday September 25, 2013 @04:38PM (#6447138)
Awesome post! One thing I find is really important is to charge 'properly', which at first seems like exurberant fees. My friends think I'm rolling in cash because of my 'rate' but when you outline all of this stuff up here, you can see where it all goes. I don't do much better than when I worked full time, but I have the potential to work harder and make more money. But the extra super hard work doesn't' seem worth losing the life balance (and well, the nice parts of contracting, i.e. TWO WEEK HOLIDAY, even though it really isn't).
Re:The shittiest project I ever worked on by shailesh on Wednesday September 25, 2013 @11:29PM (#6448780)
Happy to learn that the post resonated with you. I appreciate it.

Once a VP at a customer told me that a diamond is just a piece of coal that shines under pressure.

The quest to become a jewel in the market can be a powerful initial thrust to work as a consultant. Combined with the opportunity to work in a diverse set of technologies and business domains turns to be a pretty compelling force.

Re: compensation, tptacek and patio11 have shared some great thoughts in the past.

Re:The shittiest project I ever worked on by rexreed on Wednesday September 25, 2013 @05:14AM (#6443438)
Awesome list - deserves a nice little blog post of its own that I can bookmark.
Re:The shittiest project I ever worked on by shailesh on Wednesday September 25, 2013 @05:28AM (#6443478)
Thanks for the kind words.
Re:The shittiest project I ever worked on by ollysb on Wednesday September 25, 2013 @06:27AM (#6443651)
Really great advice, would you mind if I put it up on pastie (obviously with attribution to you) so people can bookmark it?
Re:The shittiest project I ever worked on by shailesh on Wednesday September 25, 2013 @06:58AM (#6443740)
Thank you and everyone for the words of encouragement. I've posted it on Medium: https://medium.com/p/23a07cb0d5ea
Re:The shittiest project I ever worked on by Lewton on Wednesday September 25, 2013 @07:17AM (#6443797)
What stops you from bookmarking it on hn?

https://news.ycombinator.com/item?id=6443135

Re:The shittiest project I ever worked on by hef19898 on Wednesday September 25, 2013 @05:33AM (#6443501)
Great list! Mostly works for projects in general, too! Agree that there needs to be a blog post of its own for that.
Re:The shittiest project I ever worked on by binarysolo on Wednesday September 25, 2013 @04:00AM (#6443233)
Commenting to save this for myself (fellow consultant) -- thanks for the detailed list. :)
Re:The shittiest project I ever worked on by shailesh on Wednesday September 25, 2013 @05:15AM (#6443441)
You're the most welcome, :)

I'm curious about any differences in conulsting approach to data science compared to software products: estimation strategies, what works etc.

Re:The shittiest project I ever worked on by jrs235 on Wednesday September 25, 2013 @07:07AM (#6443765)
Ditto to the first part, commenting to save or myself.
Re:The shittiest project I ever worked on by greenyoda on Wednesday September 25, 2013 @01:00AM (#6442735)
"One who can actually sit with the stakeholders and build the system on paper and go through each of the problems as the diagrams connect."

Reminds me of an old saying: "If you don't know how to do it, you don't know how to do it on a computer."

Re:The shittiest project I ever worked on by huherto on Wednesday September 25, 2013 @04:17PM (#6447030)
Paraphrasing: "You don't know how to do something until you can write a program to do it"
Re:The shittiest project I ever worked on by chii on Wednesday September 25, 2013 @03:56AM (#6443223)
heh true, but what about if you were going to use a neural network to do some sort of pattern recognition? You dont know how its done, but the computer does! :D
Re:The shittiest project I ever worked on by tripzilch on Wednesday September 25, 2013 @07:04AM (#6443758)
That's not actually how artificial neural networks in pattern recognition tasks really work.

Once you learn and understand the learning algorithms, you will experience this Wizard of Oz moment, you see how the trick's done and it's not quite as impressive as you hoped. This is confirmed by the fact that it exactly matches the limitations of a typical neural net you've established experimentally.

The tasks that are within these limitations, they perform quite well at, but it's not that hard at all to understand how they are performed. In most cases you can basically run the algorithmic equivalent of a trace debugger on the system. In as far as you can compare it with a brain (but don't do that, it's the wrong analogy--compare it with statistical regression instead), it's one you can take apart entirely, reassemble, run partial components of, tweak, and understand exactly how it works to the instruction level. Plus you can do these things automatically for the most common cases.

In short, there is nothing "magic" about neural networks, or any pattern recognition algorithms.

And to get back on the subject, if you intend to work with machine learning algorithms in a professional/consulting/project setting, probably best to first check the scientific literature to see if anything like this has been done, and what the accuracy/false positives/negatives/ROC curve is that you can expect. Don't expect to beat them, either (you may, but planning to do so by any significant amount is asking for trouble--especially if it turns out it just can't be done). Then, I think it would be clever to first build a "fake" system/interface, without the ML component, limited to just the labeled training examples (if you can't acquire these, give up now[0]), see if the system is actually useful from a software engineering, application and usability perspective, before you actually begin (the fun part) tweaking an ML algorithm, only to later turn out, even if it did its job perfectly, it wouldn't be all that useful in the operating environment in the first place.

This is different if you work for a corporation with a huge research budget, of course. Like Microsoft or Google. But even then, I think that for their ML-enabled end products, similar reasoning like I sketched above is used. Of course the same goes for every type of project that depends on an unknown to-be-researched technology.

[0] yeah yeah unsupervised learning. but if you know what you're doing that well, why are you listening to my advice? :)

Re:The shittiest project I ever worked on by floobynewb on Wednesday September 25, 2013 @08:32AM (#6444106)
I think this is wrong. Take for instance the task of classifying images. You can train a RBN with backprop (after contrastive divergence alg) to correctly classify images. In the process it has automagically determined properties of the image which allow it to perform the classification. These properties are combinations of pixel elements. So it has in effect determined how to solve a problem without your input. In a similar way, solving a set of simultaneous equations using any of a huge array of mechanical mathematical techniques is also solving a problem which you do not personally know how to solve. you could even consider using a Library of code as solving a problem you do not know how to solve...
Re:The shittiest project I ever worked on by jerf on Wednesday September 25, 2013 @10:43AM (#6444856)
"In the process it has automagically determined properties of the image which allow it to perform the classification."

(Emphasis mine.) But that's the point; it may be "auto", but if you understand how NNs work it's not magic. It's not even all that hard to understand (considered broadly), and once you understand how they work it is, for instance, easy to construct cases they fall flat on....

"So it has in effect determined how to solve a problem without your input."

... and it's less "auto" than you think. It figured out how to solve a problem based on your input of sample cases. And there's a certain amount of art involved in selecting and herding your sample cases, so regrettably you can't discard this part, either. Just flinging everything you've got at the NN is not going to produce good results.

If you don't understand NNs, you are unlikely to get good results by just flinging data at them; if you do get good results, it's probably because you have a problem that could have equally well been solved by even simpler techniques. They're really not magic.

Re:The shittiest project I ever worked on by kbenson on Wednesday September 25, 2013 @12:08PM (#6445399)
It's classic emergent behavior. While you may understand how the algorithm works, and even be able to step through and see how each neuron affects the whole, that doesn't mean you know why the answer is correctly achieved through all of them combined.

The classic example is facial recognition. Training a neural network for facial recognition will result in lots of neurons contributing a very small part of the whole, and only when all (or most) are involved is the answer correct.

To most people, this (emergent behavior) is "magic".

Re:The shittiest project I ever worked on by tripzilch on Thursday September 26, 2013 @11:20AM (#6451363)
But it's not emergence. Using Gaussian elimination to solve a gigantic system of equations isn't emergence either, even if the numbers are a bit too many to carry in your head at once. (as a matter of fact, solving systems of linear equations is part of the RBM training algo)

And even then, if it was emergence, doesn't automatically imply we don't understand it or that it's "magic". The famous Boids flocking simulation is a classic example of emergence. It's not very mysterious. Yes large-scale behaviour emerges from simple rules, this is amazing that it happens, but it doesn't hold up a barrier for us to understand, analyze and model this large-scale behaviour. Crystallisation is emergence, again we model it with a bunch of very hard combinatorial math.

But in this case, neural networks are not an example of emergence. They are really built in a fairly straight-forward manner from components that we understand, and the whole performs as the sum of the components, like gears in a big machine.

Re:The shittiest project I ever worked on by boomlinde on Wednesday September 25, 2013 @11:44AM (#6445258)
Understanding NNs is not the same as understanding "how they do it". You may have a good understanding of how the algorithms work, but after training your moderately sized network to do what it does, it's not very easy to know what _exactly_ it does to solve your problem.

I think that's what chii was trying to point out; not to say that devising them and training them is incomprehensible.

Re:The shittiest project I ever worked on by didyousaymeow on Wednesday September 25, 2013 @08:11AM (#6444018)
I have an upcoming project where we'll be implementing a pattern recognition algorithm - think smart flash cards. I've read up some on timed-repetition and a small amount on how neural networks work.

With your experiences, do you have any recommended reading that would help me with the neural network learning curve?

Re:The shittiest project I ever worked on by pgeorgi on Wednesday September 25, 2013 @04:10AM (#6443263)
now you have two problems... (because the NN will probably fail at the most inopportune moment and you have no idea to fix either the NN or your actual project)
Re:The shittiest project I ever worked on by rwallace on Wednesday September 25, 2013 @04:44AM (#6443354)
Then well and good, but alas situations where that will work and deliver business value are rare enough you can easily spend a lifetime as a professional programmer without encountering one.
Re:The shittiest project I ever worked on by willvarfar on Wednesday September 25, 2013 @05:52AM (#6443558)
Test-Driven Sudoku? :)
Re:The shittiest project I ever worked on by eitally on Wednesday September 25, 2013 @06:39AM (#6443686)
The flip side of this is that when stakeholders/customers don't know what they really want or need, you can labor in the "requirements phase" for months. My team spent 900 hours last year just getting a functional spec and high level SRS together for a project that hasn't happened yet. Why hasn't it happened? Because at the end of the 900 hours, we presented our estimate (about 1100hrs) to the customer and he balked at the cost & time. Then my boss bitched at us for spending so much time on requirements in the first place.

<8 months pass>

Now we're looking at commercial solutions in an attempt to not have to build this thing and deal with this department anymore.

I agree with you 100%, but the number of people astute and experienced enough to quickly and deeply understand the problem to be solved (and the quirks of the customer) are few and far between. In my experience, perhaps 5-10% of any large IT organization fall into this category -- everyone knows who the superstars are and their time is always at a premium. Drives me bonkers.

Re:The shittiest project I ever worked on by hef19898 on Wednesday September 25, 2013 @07:41AM (#6443892)
Try to keep your spirit up despite all this, especially your team. Things like that were part of the reason why I quit my last job.

Completely true is the thing with the superstars. I knew one myself, a genius in warehouse management systems. If I had him on a project, it went smoothly as anything. if I didn't I stayed in development hell for months. But seeing this guys workload, he wasn't off any better.

But in retrospect, the general direction the organisation took at my last employer wasn't that bad. Execution lacked, so.

Re:The shittiest project I ever worked on by cygwin98 on Wednesday September 25, 2013 @09:25AM (#6444390)
If you billed those 900 hours for doing RFP for the customer, it doesn't sound too bad.
Re:The shittiest project I ever worked on by eitally on Wednesday September 25, 2013 @02:06PM (#6446227)
We couldn't bill them -- it was another SG&A department and we (IT) don't bill them for our work.
Re:The shittiest project I ever worked on by roel_v on Wednesday September 25, 2013 @04:09PM (#6446970)
How can you spend 900 hours without someone taking responsibility for it? After 4, you say 'give me a project nr or talk to my boss.' I'd be pissed too if my staff spend 900 hours on a dud without approval or accountability.
Re:The shittiest project I ever worked on by misterjangles on Wednesday September 25, 2013 @02:01AM (#6442902)
The tricky part is often convincing a client that pre-planning is a necessary part if the process and, though it is billable time, will ultimately save money. Many client don't appreciate that programming is not just writing code.

Also you can wind up meeting and planning yourself right out of a gig sometimes - which is fine if the gig wasn't truly necessary. But can be bad for your business if you spend hundreds of hours doing this for no compensation. This is a real situation that happens - you get a client that wants a big project and after many meeting and calls you determine that a Wordpress install will suit them perfectly. Their network guy does the install and for all the money you saved them your reward is that you don't get the gig!

Re:The shittiest project I ever worked on by nostrademons on Wednesday September 25, 2013 @02:15AM (#6442943)
If you're billing time & materials (which might be a good idea for a contract of indefinite scope), you'd still get paid for the time spent doing due diligence. You might even be able to sell a time & materials contract on the basis that it gives you an incentive to point out simpler solutions that require less maintenance even if they involve using competing off-the-shelf products.
Re:The shittiest project I ever worked on by misterjangles on Wednesday September 25, 2013 @02:25AM (#6442978)
Exactly. Good clients will understand "hey, this guy just saved us $150k". Bad clients will think "I just paid a programmer to do nothing!"

Learning to recognize and get rid of those bad clients (or convert them into good clients) is a skill that can take a while to learn.

Re:The shittiest project I ever worked on by hackula1 on Wednesday September 25, 2013 @12:13PM (#6445429)
Along the lines of: "I paid my attorney $10k and I didn't even get to court!"
Re:The shittiest project I ever worked on by brianmcconnell on Wednesday September 25, 2013 @04:24AM (#6443296)
The trick then is to get clients who know they just want to "have it taken care of", and have much higher billing suppliers (IP lawyers, pharma experts, etc). In that case, they don't really think twice about paying for process in advance of coding. Pharma is a good example.

Being a contract resource for a software company, where management tends to think everything related to software/IT is "easy", is a guaranteed shitty project. They'll second guess and micromanage everything you do. And then when they burn through their OPM, they'll screw you.

Re:The shittiest project I ever worked on by jakejake on Wednesday September 25, 2013 @02:10PM (#6446252)
I ran a small software consulting business for about 5 years and I agree 100% with you. Business was stressful for the first few years until I narrowed down my client base to only those in the first category. I never did land a huge, corporate client, but I did have several smaller sized companies with a never-ending list of things to do and around X number of dollars budgeted each month.
Re:The shittiest project I ever worked on by grumps on Wednesday September 25, 2013 @12:34AM (#6442652)
Oh yes the "easy" project... we just need...

The real issue is sales...you make the sale because you have to. Then you stick the project on some poor PM/Ba/Dev who will fight with them forever over this stuff.

Maybe I'm just bitter about the situation that I continually get stuck in.

Re:The shittiest project I ever worked on by hef19898 on Wednesday September 25, 2013 @02:04AM (#6442908)
Boy, do I feel with you. But look on the bright side of it, we are not alone, are we? ;-)
Re:The shittiest project I ever worked on by grumps on Wednesday September 25, 2013 @08:34AM (#6444123)
Yea there are times when I think gee "I'm so happy to be above the ground and vertical." Then I get an irritating email and well that thought flees.
Re:The shittiest project I ever worked on by n1ghtmare_ on Wednesday September 25, 2013 @02:10AM (#6442923)
Amen, brother :) !
Re:The shittiest project I ever worked on by Agathos on Wednesday September 25, 2013 @09:17AM (#6444333)
> Although it's a fun read, it's a classic example of diving into coding without giving a project it's due diligence.

The formation of this sentence seems odd to me. Why can't we say it's a fun read because it's a classic example etc.?

Re:The shittiest project I ever worked on by perfunctory on Wednesday September 25, 2013 @03:12AM (#6443110)
> Although it's a fun read, it's a classic example of diving into coding without giving a project it's due diligence.

If everybody was so picky the size of the IT industry would diminish by 90%.

Re:The shittiest project I ever worked on by lifeisstillgood on Wednesday September 25, 2013 @04:29AM (#6443316)
and the success rate? and value delivered?
Re:The shittiest project I ever worked on by weland on Wednesday September 25, 2013 @06:04AM (#6443592)
How dare you bring technical excellence as an argument? Don't you know this is about money, not performance? Jeez, get an MBA.
Re:The shittiest project I ever worked on by lifeisstillgood on Wednesday September 25, 2013 @02:53PM (#6446515)
that took a minute to process !

cheers