News for hackers. Stuff that matters.
Re:Beware of Developers Who Do Negative Work by bad_user on Monday December 19, 2016 @02:30AM (#13210023)
Even though CS fundamentals and contributing in teams are somewhat different skills, in my experience the terrible developers that contribute negatively to the project tend to be those that do not have a good grasp of CS fundamentals.

I mean, some problems we are faced with are very, very challenging and if somebody can't figure out how to reverse a binary tree or do a FizzBuzz, then what can he do?

Also I'm hearing this advice to hire engineers recommended by other engineers quite often, however speaking as somebody constantly engaged in hiring decisions at our company, I must say that recommendations don't scale.

You see, outside the SF bubble of course, our friends are mostly not into software development and we engineers are kind of introverts, goes with the territory, so we don't have that many friends or acquaintances anyway, except for people that we meet on the Internet, which usually live in another city or country. If an employee can produce one good recommendation, that's way, way above the average. It's such a rare event actually that such employees need reward.

This advice also misses the point. The problem is that our industry is constantly growing and there aren't enough good people to go around. Which means we have to take the plunge and hire beginners as well. Investing in the education of beginners is the only way a company can scale in talent. But even then you need a filter. You can't hire anybody that walks through that door, as firing people is a serious drag on morale and a net loss for the company.

So what filter can you apply to beginners? CS education of course, or in other words what people should have learned in school.

Re:Beware of Developers Who Do Negative Work by guitarbill on Monday December 19, 2016 @05:23AM (#13210569)
It's hilarious, because our best hires are people who had no CS education. Meanwhile, some of the worst hires were CS grads.

Things that are hard to teach: Can you work in a team, especially if some of them are remote workers? Can you leave your ego behind? Can you deal with the corporate BS that gets in the way of programming? Can you think of the user, use-cases, business value, etc of the feature/product you're developing? Can you digest technical information?

Things that are not hard to teach: CS fundamentals, programming (given a basic understanding of logic).

I won't go as far as to say a CS education is harmful, but it isn't a good indicator, either. Personally, I find CS, in trying to validate itself as a "science" (which it is not, no scientific method, just like maths isn't science, but still valuable), makes stuff over-complicated and relies on terminology far too much.

And by focussing on it, you lose a huge pool of potential applicants.

Re:Beware of Developers Who Do Negative Work by bad_user on Monday December 19, 2016 @06:03AM (#13210692)
That CS fundamentals and programming are easy to teach is a myth that keeps being perpetuated and I don't understand why.

I'm also involved in an education program for children and as a matter of fact computer science is among the most difficult subjects to teach, right up there with math. Yes, you can increase interest and engagement by better teaching methods (e.g. playing and building games), but that CS is hard is indisputable.

> Can you work in a team, especially if some of them are remote workers? Can you leave your ego behind?

In our line of work, working as an individual on your own piece is actually what happens in 90% of cases. The other 10% you have to cooperate with your team to make decisions and to reach compromises on points of intersection, on protocols, on best practices, etc.

But if we are honest with ourselves, collaboration in our industry means having contention / concurrency in the development process and that doesn't scale and minimizing contention leads to better productivity. This is why we hate open spaces, why we ended up with micro-services, or why we split big teams in smaller teams. It's all about achieving parallelism by reducing the needed collaboration.

Don't take offense in me saying this, but team work is a soft skill that isn't hard to teach or learn at all. So lets be blunt. You're talking about assholes and having assholes really depends on your company's culture and what gets tolerated. If you don't tolerate assholes, some people will change their attitude, some will leave and the rare few will have to be fired, but such cases are rare.

Re:Beware of Developers Who Do Negative Work by lmm on Monday December 19, 2016 @07:11AM (#13210917)
> I'm also involved in an education program for children and as a matter of fact computer science is among the most difficult subjects to teach, right up there with math. Yes, you can increase interest and engagement by better teaching methods (e.g. playing and building games), but that CS is hard is indisputable.

I'll dispute it. I did a year of a split maths/computer science degree, found the computer science easy, and so shifted into the maths degree (on the grounds that I was confident I could teach myself the computer science degree if need be, whereas I wouldn't be able to learn the maths without teaching). Now I work as a programmer.

Most of the best programmers I've worked with have had non-CS degrees - mostly mathematics/physics, but a few from chemistry/biology/engineering, even one historian. I would sooner trust a straight IQ test than CS exercises like reversing a binary tree - the first selects for general intelligence, the second selects for general intelligence plus having sat in a CS class and/or read some CS books, and is no more relevant to day-to-day programming work.

Re:Beware of Developers Who Do Negative Work by aninhumer on Monday December 19, 2016 @08:24AM (#13211197)
As I happen to know which course you're talking about, I would point out that the module of CS you took was the far easier half of the first year material, which was open to people from a variety of other subjects, and designed with that in mind. (And indeed, the Maths dept recognises this and doesn't reduce the workload to compensate for Maths students who choose it.)

While I wouldn't say the rest of the course pushed me exceptionally hard, and I do wonder if Mathematics might have been more useful overall, I don't think that module is particularly representative of the difficulty of the CS course.

Re:Beware of Developers Who Do Negative Work by lmm on Monday December 19, 2016 @08:55AM (#13211359)
> As I happen to know which course you're talking about, I would point out that the module of CS you took was the far easier half of the first year material, which was open to people from a variety of other subjects, and designed with that in mind. (And indeed, the Maths dept recognises this and doesn't reduce the workload to compensate for Maths students who choose it.)

I did everything other than the hardware module (digital electronics) AIUI? (Which was maybe the hardest part for some people, but doesn't really correspond to the kind of thing that's asked in interviews).

Re:Beware of Developers Who Do Negative Work by aninhumer on Monday December 19, 2016 @09:17AM (#13211488)
My understanding is that your course sits one of the two CS Papers? They tend to move modules around a lot, but based on a quick look through past years' material, I'm fairly sure Paper 2 would have covered significantly more than Digital Electronics in your year.
Re:Beware of Developers Who Do Negative Work by lmm on Monday December 19, 2016 @09:44AM (#13211662)
I don't remember which paper was which. I think my year ended up doing more courses than they'd originally planned because of a miscommunication between the departments about what was going to be covered where? I did an ML course, a Java course, Operating Systems, and part of Data Structures & Algorithms before I looked through the notes and decided I knew it all (and I think I also glanced over notes for a discrete maths course earlier in the year?). Certainly when comparing notes with full ("50%") compsci friends I remember Digital Electronics was the only obvious thing I was missing.

Come to think about it I do remember talking about a friend's question on sorting algorithms in an exam that I hadn't done myself. So possibly Data Structures & Algorithms wasn't on the exam for me? Afraid it was too long ago to remember exactly.

Re:Beware of Developers Who Do Negative Work by guitarbill on Monday December 19, 2016 @06:25AM (#13210761)
* Big-O. It's basically enough to know when an algo is going to perform horribly - e.g. O(n^3) - and even then you might choose it because it's simple or your n is currently small. Anyway, senior dev or architect can make this call way better than any grad could, CS or not.

* Data structures. Many high-level languages now have better basic data-structures than many devs could write, even if they know the theory.

I could continue, but most people do fine without these CS 101 basics. Besides, good/interested people will ask questions about the code base and will read up on these concepts when mentioned. Doesn't take a genius.

> but team work is a soft skill that isn't hard to teach or learn at all

Let me get this straight. You're saying that behaviours you might have established in your teens, and so held unconsciously for almost 10 years by the end of your degree, those are easier to change than something you just learned? Something that people can teach themselves as a hobby, and often do?

But, if soft skills are really that easy to teach, I have several, lucrative opportunities for you. Meanwhile, CS courses online are a dollar a dozen or free. Honestly, if you could write up some stuff about this, I'm sure several people on HN would appreciate truly actionable advice on how not to accidentally be an asshole. Even better, if you can somehow make great devs into great managers, that's also worth gold.

I will admit that good teachers really help with both maths and CS, and good teachers are rare. Luckily, I had a good mentor by accident when I was 14. This year, our team has been to twelve local schools to help teachers make it more fun. And yeah, some kids struggle, just like any subject, but most actually have no issue at all picking this stuff up. Not worried in the slightest about the next generation's programming skills.

Re:Beware of Developers Who Do Negative Work by lmm on Monday December 19, 2016 @07:18AM (#13210928)
> But, if soft skills are really that easy to teach, I have several, lucrative opportunities for you. Meanwhile, CS courses online are a dollar a dozen or free. Honestly, if you could write up some stuff about this, I'm sure several people on HN would appreciate truly actionable advice on how not to accidentally be an asshole. Even better, if you can somehow make great devs into great managers, that's also worth gold.

To be fair a lot of people seem to have their personal identity invested in poor communication abilities, or see it as somehow "fake" to work on them. E.g. I see How to Win Friend and Influence People recommended here, but you'll see a lot of people who refuse to read it on principle.

Re:Beware of Developers Who Do Negative Work by guitarbill on Monday December 19, 2016 @07:55AM (#13211093)
"How to Win Friend and Influence People" is a bit dated, but has some good, actionable advice. I find when people hear about negotiations/promotions/job offers they've missed because of poor communication abilities, and change their tune quickly.

But once you're into adulthood, it's rare to get constructive feedback about social skills (even from friends). So it can be catch-22, especially if you aren't very attuned to the reactions of others. It isn't that they don't want to change, but if you aren't charismatic or confident, you're going to have different outcomes in the same situation, so it's self-reenforcing. And infuriatingly, the intrinsically high-charisma people don't know what's needed.

A book I can recommend is Keith Ferrazzi's Never Eat Alone. I find the name-dropping cringe-worthy, but it made business relationships click for me, which got me to do more social stuff, etc.

Re:Beware of Developers Who Do Negative Work by BatFastard on Monday December 19, 2016 @08:13AM (#13211142)
>Data structures. Many high-level languages now have better basic data-structures than many devs could write, even if they know the theory.

I would say that ALL high level languages have basic data structures, and that those data-structures are better then 99% of the data-structures that users would/could write. Just because to be included in the language the coding level is very very high.

Re:Beware of Developers Who Do Negative Work by pathtracer on Monday December 19, 2016 @10:51AM (#13212117)
> Personally, I find CS, in trying to validate itself as a "science" (which it is not, no scientific method, just like maths isn't science, but still valuable)

Science can mean different things to different people. While in the english speaking world it is often equated to "natural science" this not the case for all languages.

Take the famous Gauss quote for example: "Mathematica regina scientiarum est et theoria numerorum regina mathematicae est."

In german, CS (Informatik) is widely regarded as a "structural science".

https://de.wikipedia.org/wiki/Strukturwissenschaft

Re:Beware of Developers Who Do Negative Work by guitarbill on Monday December 19, 2016 @12:29PM (#13213101)
I'm weary of people throwing out Latin quotes, or trying to apply Latin or Greek to English. It's difficult, as words change meaning (my favourite example being "techne"). Gauss' quote translated is "mathematics is the queen of the sciences", but without context obvious worthless. He could have been joking, I for one haven't read his whole letter.

It's a bit disingenuous to bring German into this, luckily I speak it also. I would dispute that "science" == "Wissenschaft". Literally translated, "Wissenschaft" is "creating/establishing/managing/develop knowledge". In the strictest sense, "science" must be translated as "Naturwissenschaft". There simply isn't a direct mapping. Interestingly, "structural science" in English means something different than "Strukturwissenschaft", so even the example you gave undermines that "science" == "Wissenschaft". Wissenshaft encompasses more than science.

I find a useful test if something might be a science is check it doesn't have "science" in the name :)

But let's be clear, just because a field isn't a "science" doesn't diminish importance or value. I am sick of seeing this argument. But it is extremely important in the way you approach teaching that field.

I actually think it gives you far more flexibility and interesting ways to approach a field. Scientific method is very rigid, for good reason. But fields that don't employ the scientific method need not adopt this rigidity, especially if they have solid formalism behind them. Just don't try and dress it up like a science. E.g. I hate Big-O, or the almost religious importance CS puts in it. It's good formalism that can't be directly applied to reality. It isn't a scientific result. But that's a rant for another day.

Re:Beware of Developers Who Do Negative Work by user5994461 on Monday December 19, 2016 @11:12AM (#13212306)
> It's hilarious, because our best hires are people who had no CS education. Meanwhile, some of the worst hires were CS grads.

Just an idea: Try increasing salary. Good CS grads already have people hiring them and they have a ton of debt to repay.

Re:Beware of Developers Who Do Negative Work by walrus1066 on Monday December 19, 2016 @04:00AM (#13210330)
I find a lot of CS education is not applicable to most SE roles, as they operate at a higher level of abstraction.

I've never had to implement a binary tree, if I did, I would be reinventing the wheel.

A lot of the necessary skills are hard, if not impossible, to teach in higher education. Mainly because there, you tend to be given an exact, unambiguous specification. Whereas in the commercial world, I've never seen that to be the case, the developers role is to collaborate with the business to nail down the specifics of a high-level business goal. Implementing the code is the easy bit :)

Re:Beware of Developers Who Do Negative Work by bad_user on Monday December 19, 2016 @06:30AM (#13210781)
> Implementing the code is the easy bit :)

For web forms that replace an Excel spreadsheet, the kind that usually gets passed around over email or in a Dropbox, yes, the business requirements are usually the ones that are problematic, as you are expected to grok a lot of domain specific details in only a couple of days.

But then again IMO, your experience is biased by the problems you've been working on.

> I've never had to implement a binary tree, if I did, I would be reinventing the wheel.

If you actually had problems involving trees, you'd know that besides the usual data-structures we all know and love, problems involving trees and graphs rarely have prepackaged solutions and the available solutions are leaky abstractions for which you have to know how they work in order to fine tune them or to make a choice between the available solutions. Consider that problems involving graphs many times involve NP solutions that are unacceptable, but that admit solutions producing approximate results, which may or may not be acceptable for your problem.

And sure, maybe the problems that you're solving don't involve trees or graphs. That's fine, I think it's been 2 years since I saw a graph problem myself, but then again, medics learn a lot more than they need to treat the common cold, in order for them to be prepared. I wouldn't want to be treated by a doctor that doesn't have the proper education, since my life is on the line. And yet we are the industry that accepts people without a college degree, but given that we also have a lot of responsibility on our shoulders, how accepting can we get? Consider that we build software that controls buildings, that drive cars, that process the confidential data of people.

And we as software developers, when we meet, what are we going to talk about anyway? Sure, you might have some personal projects we can talk about, but lets circle back to beginners. What are you going to talk about with somebody fresh out of college or high-school? And even with seniors, not everybody has an interesting project to talk about, so how are you going to assess their worth? Sure, you can always do a trial, but the reality is that firing people is hard and expensive, that's just the way things are and most companies prefer false negatives.

Re:Beware of Developers Who Do Negative Work by matt_wulfeck on Monday December 19, 2016 @12:15PM (#13212973)
> If you actually had problems involving trees, you'd know that besides the usual data-structures we all know and love, problems involving trees and graphs rarely have prepackaged solutions...

You seem to argue that having deep understandings of these types of issues makes you a better employee in the long term because eventually you will come across a hard problem that requires these skills. I would argue that an engineer who doesn't have a great grasp on the internals of fundamental CS data structures, but knows how to priotize time, will work on somebody else's mess or deal with corporate BS without complaining is more valuable both in the short and long term.

These types of engineers are just simply better and more productive to work with.

Re:Beware of Developers Who Do Negative Work by walrus1066 on Monday December 19, 2016 @04:39PM (#13215206)
I think the best (though not prefect) method to test new devs is with a take-home exercise, no time limit, that is representative of your domain. The key things I look for are:

- did they understand the requirements? If not, did they ask for clarification?

- did they choose appropriate abstractions?

- is the code easy to read? Is it overengineered? Are they trying to show off by overcomplicating things, or optimising prematurely?

- the simpler the solution, the better

- are the tests good, readable, not too brittle

I then ask them how would they extend the code to fit new/changed requirements, they don't necessarily need to write any extra code in my presence, whatever they're most comfortable with.

Re:Beware of Developers Who Do Negative Work by borplk on Monday December 19, 2016 @08:40AM (#13211278)
Junior people who are very good at CS often struggle with "real-world software".

I had to explain to such a developer once why it was a bad idea to store multiple values into a single database column.

It was a simple task of adding a few integer columns to a table but he couldn't let go of the "optimizations" in his mind about how he could use binary bits to represent what we wanted to represent and all that...

A person with good CS fundamentals need to go through some tough times for a few years at dev shops where the rubber meets the road and then they'll develop a technical taste.

Re:Beware of Developers Who Do Negative Work by bigato on Monday December 19, 2016 @11:17AM (#13212354)
If a guy does not understand the DB theory related to data normalization, I wouldn't call him good at CS. At least not DB related CS.
Re:Beware of Developers Who Do Negative Work by matt_wulfeck on Monday December 19, 2016 @12:19PM (#13213021)
The problem is he/she might be right in a vacuum. Denormalizing the data might be "100x faster!", but they're naive to every other technical non-technical burden that comes along with that decision. Part of our interview process is selecting for people who can come up with the most efficient answer, but efficiency is a squishy thing when you're a member of a team.
Re:Beware of Developers Who Do Negative Work by lkitching on Monday December 19, 2016 @11:22AM (#13212409)
I wouldn't say someone who's never heard of first normal form has 'good CS fundamentals'.
Re:Beware of Developers Who Do Negative Work by borplk on Tuesday December 20, 2016 @08:02AM (#13219423)
I'm talking about multiple values in a single CELL, not a single table. He wanted to use binary bits to encode multiple things into a single cell.
Re:Beware of Developers Who Do Negative Work by lkitching on Wednesday December 21, 2016 @10:33AM (#13229853)
So am I - storing multiple values in a cell violates first normal form.
Re:Beware of Developers Who Do Negative Work by nradov on Monday December 19, 2016 @10:43AM (#13212065)
Most CS education has only limited applicability to real-world software product development. It's like hiring a BS Physics graduate to do mechanical engineering work. Sure a smart person can eventually learn to do the practical engineering stuff but it will take a lot of training and mistakes along the way.
Re:Beware of Developers Who Do Negative Work by pjc50 on Monday December 19, 2016 @04:56AM (#13210486)
Also if you restrict hiring to recommendations it's going to be even worse for your diversity. We can at least try to have a recruitment system that doesn't place too much weight on what people's faces look like or nebulous "cultural fit".
Re:Beware of Developers Who Do Negative Work by adrianN on Monday December 19, 2016 @05:41AM (#13210625)
Other than warm-fuzzies, what are the benefits of a diverse workforce for a company? If you could eliminate the problem of bad hires by only hiring jewish black transwomen to the exclusion of anybody else, shouldn't you do it?
Re:Beware of Developers Who Do Negative Work by matt_wulfeck on Monday December 19, 2016 @12:21PM (#13213039)
The benefit is that you satisfy unspoken but strongly enforced diversity requirements. I'm not being cheeky, this is very important when someone starts to take a critical eye towards your company.