5 ms·
The Hacker Ethic - Harming Developers?
- rbanffy 17y agoThere are programmers and there are hackers. To use an interesting quote, it's a privilege, not a right.
- jimfl 17y ago"There are programmers and there are hackers." Then there are software developers. Software developers are sometimes called upon to program, sometimes hack. A lot of what a software developer spends time doing is neither, working closely with all the other roles in a development shop to deliver software. Working with business owners, architects, junior devs, documentation, QA, operations, support, and the users requires a lot of time spent not programming and not hacking.
- omouse 17y agoBut remember not to fall into the trap of thinking of yourself as an engineer. Two different fields entirely and what may work in one field, may not work in the other field. Engineers deal with physical products and fully-specified tech specs and all sorts of extra business stuff that is just a hindrance to a software developer (or are impossible to implement, like a full tech spec, all software has a creative component that's hard to control).
- jimfl 17y agoIndeed. I avoided the term engineer purposely.
- rjurney 17y agoYes, having machine intuition, mad skills and a deep understanding of how to build things makes it hard on Indian typists that have to keep up. Boo Hoo.
- tsally 17y agoWell written code is approchable without constructs like UML. The problem with most 'programmers' is that they don't think they should be doing hard programming each day, every day. Yes, experienced hackers make it look easy, but it took them a lot of work to get there. Also, just because hackers are a scare resource doesn't mean we should accept a lower quality in the end product. What if we did that with the engineers that worked on airplanes? Software is used in many similarly critical situations. It's time to accept that the things that adults use like UML and overly complex IDEs don't increase the number of good programmers. Ironically, they actually mask the true ability of a programmer. To actually accomplish that, you need to start with the programming curriculum in high school and early college education.
- edw519 17y ago"Yes, experienced hackers make it look easy, but it took them a lot of work to get there." My manager just asked why it took 2 weeks just to promote 1000 lines of code into production. Today's 1000 lines of code was 5000 lines of code a week ago. I suppose that if I had promoted 5000 lines of code a week ago, I would have looked better. But we know better...
- tsally 17y agoI hear that. At my current job (large defense contractor-- team of 50+ programmers), programmer productivity is measured by lines of code committed per day. There was a day where I actually removed 100 lines of code and rewrote it in 50. The result was a much more efficient algorithm, but according to the metrics used to evaluate performance, I did negetive work. At least I'm only expected to average +12 lines of code committed per day. :-)
- mahmud 17y ago<rant> Well written code is approchable without constructs like UML. ANY code is approachable without constructs like UML. Compare the Addison Wesley "Professional Programming" series (the ones that published APUE, UNP, Pthreads books, etc; the white text with a splash of blue) to the yellow/khaki "Object Series", the ones that published Booch's books and the french dude who was pushing Eiffel, etc.) The difference between the two series of books is essentially UML and "object technology". The first is readable bliss, the later is an abomination cast at us from the bowels of hell. UML is wankery. It's what liars and crooks push when they lack the sufficient bullshit to make it to high executive positions, and the talent, dedication and honesty necessary to be an engineer. Everytime I met a "software architect" that used that garbage, the person was always nearly clueless and a pain to be with. </rant>
- edw519 17y ago"The India shops love methodologies like UML and the like, specifically because the problems have been reduced to a simplistic enough granularity that they can be doled out to junior-level staff, who may have only been onboard a few weeks because of the massive churn over there." Let's tell it like it really is... The India shops (and many U.S. shops, too) love methodologies like UML because they make someone who does not know what he is doing appear as if he did. This is especially important for maintaining margins above 50%.
- erlanger 17y agoThis is the most recent comment from the article that started this little discussion: > Hi All, > I am just another IT Engineer from India working for the one of the largest IT companies in India. And I know that what Indian IT companies like HCL work for, only money (through offshoring). They do not want people who use brain because they don't have such work to do. All they want is a duffer who sits on a desk and can work like a donkey for 12 hours a day. There are no excuses such as work life balance etc, because client is the boss. You can not say no to anything. They fake the resumes of employees, make them achieve impossible target by making them work like a dog. The estimation is the beginning of a big mess to happen. Moreover an IT engineer must be prepared to be fired, because they have a reason of recession. They can handout dividend to shareholders by cutting the variable pays. > As per what Veenit says is Indian people learn to following processes etc, but when you look inside a IT company, you can rest assured everything can be managed. There is not advantage in following processes, because what I have seen is 90% time of my PL goes in following these processes. The project leader has no time for his team. > I believe that IT companies like HCL wont take up innovative work at all, so creative minds in US should not bother about his comments. Although lots of work is getting outsourced. The core work is going to remain in countries like US, because most of the people working in huge companies like HCL, Infy, TCS ,Wipro and Satyam become incompetent because of the quality of work they get most of the time. > Moreover a person wont work on a specific business or technical domain, which leaves makes you loose confidence. > There are many people like me who once get stuck in such companies, its really hard to come out. > So Americans, better dont go to such sh companies. Its better for your own future. Interesting.
- pingswept 17y agoI hereby resolve continue to learn less of "business processes" and "best practices." If I'm lucky, I will entirely disqualify myself for jobs as a "programmer."
- lallysingh 17y agoNo no no, just remember where to look. HN's ideas of business processes and best practices are quite different from what you see in body shops like that.
- CodeMage 17y agoNayar is actually right, in a way. Hackers should be considered unemployable by companies like HCL. From what I know of shops like that -- and I've interacted with various over the years -- a hacker would be profoundly unhappy working there.
- jasongullickson 17y agoSpot on: "This entire debacle is representative of a problem I think is endemic in the industry these days, the inability or unwillingness to engage in rapid prototyping. Every successful project I've ever worked on (and I've worked on some fairly large enterprise-sized projects), we started by designing and coding a quick "throw-away" skeleton of the application, that let us look at how the thing worked, where the unseen warts were, and where the vendors had lied about their APIs, etc." I don't have the perfect solution (yet) but there is a definite difference, a sort of "feeling of entitlement" present in many coders who came along after the microcomputer wars of the 1980's. They expect things to "work as advertised"...and a heartbroken when their project ships late due to unexpected difficulties with the environment/ide/framework/etc.
- edw519 17y ago"Every successful project I've ever worked on (and I've worked on some fairly large enterprise-sized projects), we started by designing and coding a quick "throw-away" skeleton of the application..." Me too. But for another reason... I almost never get real specs. But once a user sees a prototype, they are suddenly no longer bashful. They'll tell you how it really should be.
- omouse 17y agoSomeone on Slashdot commented and said that they're company has 2 phases for developing software. The initial prototype phase where the hackers get to use whatever tools they need to write the software, just to get something out there. The point is to figure out the specs based on that and then once they do that, once they have the scope of the software determined, then they can just write a spec and feature list out and hand it over to the engineers who turn the prototype into an actual product (with documentation, full-scale test suites, etc.)
- jasongullickson 17y agoAbsolutely, and I don't think this is bad, just a frame of mind. Let's face it, it's just easier to know what you want once you have something in your hands to play with. I think instead of resisting this we should adopt tools and processes which make it easier. When I've had the ability to facilitate a project in this way, the result has always been of superior Quality compared to other methods.
- gaius 17y agoIt doesn't help that the link to "stupid hacker tricks" in the referenced article is about script kiddies.