Hacker News Reader

Comment by wanderingmarker | Hacker News Reader

Ah yes, the tragedy of studying computing to the exclusion of everything else. Graduates with computer science degrees have an in-depth understanding of... text editors. And maybe compilers, databases, and operating systems — all items of zero value until they are applied to solving some real problems in some other field. Problems which the computer science graduate knows nothing about.

Then these graduates go into the working world, and they typically can't help solve problems in economics, physics, applied mathematics, or medicine except by coding up some system to someone else's specs. The more dedicated ones make an effort to understand what they're doing. They exceedingly rare, gifted, and motivated ones might learn enough about an industry to make real contributions.

I hope that our field eventually evolves to the point that programming skill becomes an accessory. People will then learn to program just like they learn to write, and use the craft to help them solve their actual problems. The profession of programmers who only know how to program should disappear like the profession of scribes who only know how to write.

View on HN

Yes

And some are almost proud to not know anything beyond their field.

Newsflash: You can be the best writer in the world, but what are you going to write about then if you know nothing besides writing?

Programmers often complain about managers knowing nothing about the field. But it's the same thing when the programmer doesn't know anything.

There is a lot of money in doing specialist applications. Most of these are made by people who know a lot about their field but only a little bit of programming.

This. The same programmers that complain about clueless micromanagement are usually also the ones with the "I don't want to know all this business shit" attitude.

Guess what? You're being micromanaged by MBA's because otherwise, despite all your l33t coding skills, you're f-ing useless.

I'm a junior in an Information Systems program right now. I have to admit, when I first started school, and I looked at my curriculum, It was pretty disappointing to find out that I'd be taking more business and economics classes than actual computer-related courses.

Now that I'm over 80 credit hours in, I have to say that my Micro and Macroeconomics classes were two of the most interesting courses in my entire program.

> usually also the ones with the "I don't want to know all this business shit" attitude

Very easily identified early in school as the ones who say "I don't want to know all this history shit" or "I don't want to know all this writing shit"

Two of the most painful experiences in my life (ok- slight exaggeration) came in engineering school. One was watching the first time we were asked to make powerpoint presentations (they were transparencies, actually, but same diff). The other was reading the first papers we wrote in our "writing for engineers" class.

In both cases, sitting there and watching was excruciating in that "holy crap this is awful, just make it stop for the sake of the poor guy" kind of way.

But you know what? Some of us got better at it - the ones who made an effort. This made me realize that we do not force enough liberal arts on engineers in school. In fact, I was prohibited from taking many art classes - I got no credit towards my degree for them because they were perceived as "soft". That is crazy.

I ended up realizing in my junior year of high school that liberal arts were enjoyable. Graduated with a degree in CS and a minor in creative writing and I'm very glad I did it.

I also think that reading and posting on places with high quality discussion like HN and reddit circa 2008 can really improve your communication skills.

A liberal arts education gives you an advantage over other engineers. "You mean this guy can actually read and write?"

Especially true if the business ever needs to write a technical proposal to win a contract. Very important to have engineers who can read and write then.

Most liberal arts educations are a quite inefficient way to teach people to write. Many who leave such educations are not that much better off than when they started.

A liberal arts education gives you an advantage over other engineers. "You mean this guy can actually read and write?"

There are a couple of questionable assumptions baked into that statement, IMO. First, that a "liberal arts education" (by which I assume you mean earning a 4 year degree from a liberal arts university) definitely means you will come out able to read and write to a superior degree. Maybe if you major in English or Philosophy, otherwise, I wouldn't take that as a given.

Also, there seems to be an implicit assumption that the only way to gain a solid grasp of reading and writing well is through a liberal arts education (again, I'm assuming you mean a formal liberal arts education). I'm not sure I buy that. The best way to learn to write, IMO, is to write a lot, read a lot, and solicit feedback on your writing. None of that requires a formal liberal arts education.

Now if you aren't necessarily referring to formal / university education, then we probably don't disagree. I certainly agree with the point that having solid reading and writing skills is a valuable thing!

This. The same programmers that complain about clueless micromanagement are usually also the ones with the "I don't want to know all this business shit" attitude.

Ridiculous. I know this stereotype exists, but I don't know many programmers who actually hold that attitude. The "business shit" is intellectually easier and not at all uninteresting. The payoff in learning it is quite high: in a functional organization, you get more respect and money for a relatively small investment. There might be some clueless 23-year-olds out there who reflexively dislike "business" because of Marxist-academic indoctrination, but that's a rare and transient state.

If anything, the MBA micromanagers try to encourage this attitude by taking the "I will handle all of this" approach with the business side and the "big picture". They make it their turf by assertion, then wonder why the engineers under them seem not to give a shit.

Engineers tune out when they don't have any power or control. It's a survival mechanism. If you can't do anything about it, don't waste cycles on it.

I work with at least one guy who just straight-up isn't interested in managing, ever. As the team has expanded, he's moved two tiers down the org chart, but he isn't interested in learning the administrative portion at all. It's not about control, some people just seem to be allergic to meetings, dealing with stakeholders, etc. It's a perfectly valid viewpoint to have: some people just want to write code.

The guy you mention likely is a solitary worker (I'm one as well).

We tend to prefer not working in teams, other people slow us down and cause confusion in our work.

But America's insistence on a "team" based work culture really hampers those like me. We can get 10x the amount of work done individually as we can as part of a team if left to our devices - but this is frowned upon, indeed looked at as a social "problem".

I * sincerely* blame MBA culture for this detrimental attitude.

It's kind of an interesting viewpoint; how do you handle being 'crowded out' of a project? For example, if you started as the sole worker on something internal, but then it became customer-facing, and the team necessarily had to expand to get the work done. I can appreciate saying that you only get 10% of the work done if you're on a team, but you don't honestly think you can achieve as much as a ten man team? What about when more than 10 people are required?

I guess my question is, as a self-identified 'solitary worker', would you take it upon yourself to leave a project if it reached a point where team expansion was necessary? Is there any good way to manage someone like you to get you to contribute to a larger project, or if it a lost cause?

There is a difference between working on a team where everyone works on the same bits and you have to work around their projects and their timelines, and being part of a team where each 'member' works in a semi-siloed, semi-independant capacity.

I much prefer the latter to the former since I don't have to work about anyone else makes changes to stuff without my knowledge but I'm still on the team, still met with the others to discuss what we are working on and how it impacts X or Y.

I can see the siloed approach working to a point, but there are two big drawbacks:

- no exposure to new skills and techniques. This particular employee is pretty fond of cut-and-paste, and we've been refactoring to fix a lot of that. As we refactor, the ground is sort of shrinking beneath his feet, because he isn't willing to work on other people's code. If you aren't willing to learn new techniques and read other people's code, your portion of the codebase is going to accumulate technical debt while the rest moves forward.

- no big-picture perspective. I love to stick my nose into every architectural discussion, and I think it's beneficial for us to plan big decisions as a team, to try and find the best solution. From experience, a siloed employee won't be interested in getting involved in these large-scale discussions, because they haven't kept up with the rest of the codebase, and they don't have an interest in it.

Essentially, having all your team hived off from each other, doing their own thing:

- gives you a very low bus factor. If one guy moves on, dies, whatever, suddenly you've got a dark area of your codebase with built up debt and no knowledge.

- reduces the cohesiveness of your design. At the best, the high level plan will be dictated by management or a single architecture, and each employee builds their part according to spec. This seems to reduce autonomy and job satisfaction, and it presumes none of the coders have any good ideas about architecture (wrong).

If you have techniques or suggestions for getting around these issues, I'd be glad to hear them. It is a big problem that some very good technical people aren't necessarily very social.

@alanctgardner2 Agreed, there are limitations. If that guy is a fan of cut-n-paste then there are bigger issues at hand than just social interaction.

Working in a siloed environment doesn't mean not learning new skills or techniques. And I don't mean that you are only working on the same project/chunk of code the entire time. We would often switch projects so that what I'm working on today is completely different that last week and has been touched/edited/tweaked by just about everyone on the team at some point.

Having a Big Picture perspective is vital be being able to work individually. You have to know how your work will ultimately impact everyone else and how their will impact you.

I don't mean that everyone is working on completely separate projects but that Employee 1 might be working on a feature enhancement on version 4.5.3 while Employee 2 is working on a refactor of the back end code and I might be working on implementing a change control request on version 4.5.4.

Perhaps this is a better way to explain: everyone is working on the same Project but on individual and separate Tasks

That just seems like every team ever, except for pairs programming I can't imagine having two people in the same part of the codebase at the same time. Is there an alternative you can think of that isn't just poor management, or ambiguous descriptions leading to conflicts?

Also, you can reply even during the cooling-off period by hitting the 'link' link.

Majors bugs that involve both the front and back end developers.

Major feature enhancements in which multiple devs touch the same set of files.

There are probably ways around these issues, just some instances where I've had to sit next to someone and work out a bug/problem.

" would you take it upon yourself to leave a project if it reached a point where team expansion was necessary?"

Not every project requires team expansion and teams vary in strength and productivity. But in general, yes I would leave if I were required to stand in front of 9 "team members" every morning and tell them my deeds and troubles. At this point, the challenges have been solved and the single hardest problem in the project is coordinating everyone. I get bored and frustrated at this point causing me to seek a more interesting project.

Software is fundamentally a creative discipline - creativity rarely occurs in a committee.

A 10 man team can certainly do more work then I can (in general). But if I'm unable to work properly in a 10 man team, I SHOULDN'T be on that team. Not all of us are effective in the traditional agile environment - give us a nook somewhere and let us solve problems independently. You'll get far more value out of us that way then adding us as the 11th member of that team.

I just want to point out that there are different aspects of "managing". There's tactical, command and control, administrivia type stuff, and there's "solving problems, acquiring resources and providing high level coordination" and then there's "strategic decision making" kind of management. One can certainly lack interest in one of those, but might find the others interesting if exposed to that part of things.

Personally, I consider most of what most managers do, to be "administrivia" which is of very low value, and I'd have no interest in ever doing that. But when a manager it tasked with actually identifying and solving problems, making strategic decisions, etc., that part can actually be as intellectually challenging as programming and can actually be fun in it's way.

It's not about control, some people just seem to be allergic to meetings, dealing with stakeholders, etc. It's a perfectly valid viewpoint to have: some people just want to write code.

That's absolutely true as well. I was largely that way when I was younger, but over time I've grown more interested in the other aspects of things.

If you can't do anything about it, don't waste cycles on it.

I think the point is that you can do something about it - it just requires stepping out of the engineering midset for moment now and then. I've seen this fatalistic attitude frequently, both in software developers and "real" engineers (mechanical, electrical, etc). It's not healthy for the engineer or the organization, and I can't quite figure out where the attitude comes from.

Engineers are culturally unusual in being very tolerant of criticism (from other engineers). That's because our compilers, nominally subordinate, yell at us on a daily basis about minor syntactic errors.

With managers, you can't take the same approach. You cannot simply tell your boss that his managerial style is nukular buttfail. That gets you fired.

I've known a few programmers who really just were not interested in the business side of things. And I've known a few who were really interested in it. On balance, I think this stereotype exist for a reason, but - as with all stereotypes - it is flawed when treated as a general truth.

Engineers tune out when they don't have any power or control. It's a survival mechanism. If you can't do anything about it, don't waste cycles on it.

Yeah, I've definitely seen this. But, on the flip side, I've seen manager types who want the technical people to get move involved in understanding the business issues and develop more of an ability to contribute at that boundary (to the extent that such a thing actually exists) between the "business world" and the "IT world".

If you folks will indulge me a bit of (related) self-promotion, I've written two recent blog posts[1][2], touching on a specific technique and methodology that I see gaining some steam, which deals with operating at that "chasm" between the worlds. In the first part, I argue that, in the future to come, developers are going to need to learn more about the business world AND that managers are going to have to learn more about technology.

[1]: http://fogbeam.blogspot.com/2013/02/so-what-is-capability-ca...

[2]: http://fogbeam.blogspot.com/2013/01/why-capability-cases-are...

I use to hold that attitude as did a lot of the people I worked with. Just said 'tell me what you want the thing to do and I'll make it happen', didn't really care about the business side of things.

That changed a few years ago (can't remember the exact reason why) when I started learning about the industry I was working in (because it was something I wanted to know about) and saw my work getting better and coming back with fewer and fewer change requests and a couple of Oh, that was a great way of doing X. You get it!

Made a world of difference.

Your point about writers is a real problem. Way too many literary novels where the main character is a writer.

Too many people, especially worker bees like engineers and janitors, tend to focus only on their part of the job and not how it fits into the big picture.

> The profession of programmers who only know how to program should disappear like the profession of scribes who only know how to write.

Everybody "knows" how to write.

There's a difference between literacy and mastery.

Without fluency in the solution domain, the problem domain will simply remain that: a problem without a solution.

The Other Jacques's point was that as developers we often see lots of problem domains and that learning about them is useful.

I tell my customers that part of my job is becoming an "instant expert" in the part of the world they've called me in to help with.

The only subject I can think of with similar professional requirements would be law, where deep knowledge of the solution domain is required and quick acquisition of the problem domain is a predictor of success.

I hope we'll have specialized careers someday (Medical CS, Economics CS, etc...).

In many careers, it's the other way round - most physics I know taught themselves how to program, for example, but they're lacking some tools that would probably help them a lot (and physics are very close to CS). I've seen accountants do a lot of programming in Excel macros and Access too.

Doctors and Economists might have less interest in learning, but academy-minded ones will really appreciate the modeling they can do with the use of computers (I think I saw a medical paper where they reinvented some basic CS concept :) ).

Some of the domain training comes from practical experience - I started out working for the credit report sector, and then moved on to the insurance sector, so I've picked along some domain knowledge in those areas. Other colleagues have worked in logistics, and now know about their problems, etc...

> (I think I saw a medical paper where they reinvented some basic CS concept :)

Perhaps more shocking:

https://fliptomato.wordpress.com/2007/03/19/medical-research...

Yes, reading HN it often seems like programming skill is the only game in town. It is obviously important, but it's nice to see something on the importance of domain knowledge as well.

So coding skill is one dimension along which you have to be good. Domain knowledge is another dimension.

A third dimension is knowing the code base you're working in (which takes time, since most production systems tend to be big). To be a really effective developer, you need to be good along all these dimensions.

> Yes, reading HN it often seems like programming skill is the only game in town

I always felt most of us on HN were well rounded individuals--interested in most areas of knowledge. Looking at the random articles that get upvoted along with ones on programming, it seems to coincide with that premise. Sure, we talk quite a bit about programming, but it's a just a tool for automating the repetitive work we do and to make ours and other's lifes easier. It's a means to an end and also something that happens to interest us at the same time.

Programmers are not like scribes, they are like authors and writers - which are still here. Programming is a creative discipline, it's not just formatting one written format (specs) into another (code). Of course, the bad ones might make it seem like it...

"the bad ones might make it seem like it..."

Or the ones with highly uncreative managers who lack sufficient domain knowledge themselves.

If I were to get all novice programmers to learn something else, it would be some practical anthropology. How to observe. How to interview. How to see and record behaviors, triggers, social interactions, power dynamics. How to discover motivations, attitudes, and they way people understand the world. The one thing all of our software has in common is that it is supposed to make a difference in somebody's life.

If I could demand a second thing, it would be the basics of business. A large portion of software is directly about business, and almost all of it is somehow shaped by how business works. E.g., I'm volunteering at a non-profit this month, but the developer I sit next to is hip deep in a risk management problem.

"Ah yes, the tragedy of studying computing to the exclusion of everything else. Graduates with computer science degrees have an in-depth understanding of... text editors."

That makes a lot of sense. To me is that because we are using "languages". With a language you write. And your problems are writing problems: syntax, commas, naming, verbs, etc etc.

What if we just get rid of "languages" ? We actually do not "write a skyscraper". We make a project for a skyscraper. Or we "draw" a skyscraper.

Are languages the best tool of choice to solve the problem in connection with the information (and its calculation)?

(not that I have a definite answer, just a question).

Languages exist to convey complex information, nothing else comes close to them in that ability.

As an exercise, try to convey the idea "I'm diabetic and I need some insulin" via !language. Charades? Interpretive dance? Drawing?

And yes, we do "write a skyscraper". That's what blueprints are for.

You can draw a skyscraper because at it's core a skyscraper is an object that exists strictly in a 3 dimensional world. Therefor you can convey a lot of important information about the skyscraper by showing it's shape and dimensions in an autocad drawing.

In reality however I expect that most skyscraper projects involve many many pages of writing and formulas in addition to the drawings.

OTOH a computer at it's core is a machine that sequentially follows instructions. So any description of a computer program must be able to reduce to this.

Since around the dawn of computer (or at least in the 10+ years I have been involved) there have been attempts to remove the requirement for computer programming, but in reality nobody has come close to anything as powerful as a programming language.

The most effective progress has been made via abstraction, where you allow one instruction to be used to imply many. For example making a REST API call with 1 line implies a lot of operations on a lower level (TCP/IP etc).

I think this is fundamentally because any system that you propose to replace a programming language will either be:

1) Turing complete, in which case it could be classified as a programming language itself and will require knowledge of algorithms/abstractions etc to operate effectively. This is where you end up with flowchart driven development tools where the flowchart ends up literally resembling a plate of spaghetti for any reasonably complex system.

2) Not Turing complete, in which case you lose a lot of power as there are things the system will not allow you to express and thus lose the ability to deal with many edge cases. Since you are developing software and not just using it, the reason for the development activity in the first place is probably to deal with some edge case than an off the shelf program does not.

When I was younger I used to play with various "code free" game development tools and ran into the same fundamental problem.

For example, I have a shooting game and when the player is hit with some projectile he takes some amount of damage based on the projectile he was hit with. This was usually very easy to do.

BUT then say I want to add an "armour" powerup to the game. If a player with the armour powerup is hit then he takes damage but at a reduced rate that is proportional to his armour value. The armour value is also reduced based on itself and the armour piercing value of the projectile which hits. However if the armour piercing value of the projectile is below some value proportional to the armour and health values combined then no damage is taken at all. Oh and the armour powerup cannot stack with certain other powerups except under some specific circumstances.

That type of logic was impossible to express with these tools, or required finding creative ways to abuse the tooling in ways not intended which would in turn make other functionality more difficult/impossible.

> The profession of programmers who only know how to program should disappear like the profession of scribes who only know how to write.

I think it would be better to say that the new programmers would replace the old as writers replaced scribes. Because we do have people who only write, it's just not quite the same.

Writers are not merely new scribes. Writers are people who use the written word for some specific purpose. Very coarsely, I claim that novelists are storytellers, poets are artists (who use words as the medium, like sculptors use marble or bronze), biographers are historians, textbook authors are teachers, journalists are investigators. For all these subtypes of "writer," the process of getting words on paper (or into a Word document, or an Emacs buffer!) is simply a means to an end. They certainly don't "only write" — at least not the ones who produce anything remotely worth reading.

> Writers are not merely new scribes.

Indeed, that's why I made the comparison :) The new and old programmers he describes are not the same either.

I guess it all depends on the student in question. Me, I majored in Computer Science, but I love all areas of science and study them on my own. Same with History, Art, Philosophy, Music (played violin & clarinet) and Literature. I was probably one of the few odd students in Computer Science at my school that actually loved the creative writing and art courses he took. I am not a great artist, but I can talk to someone who knows way more about art than me and relate to what interests them to a point. Such things lead to forming connections with people and exchanging great ideas across knowledge gaps between them. It also helps you to form better analogies and metaphors for explaining difficult, technical concepts.

I would have actually gone into teaching History if the United States school system was not as limited as it is these days in what one can teach students. I probably read and study history as much as I do about software development. However, I love Computer Science and have no regrets about going into it instead.

Any student that does not strive to be well-rounded in as many areas of knowledge as they can outside of their field is really missing out on life. Entrepreneurship in general is all about knowing what will make life better and it's hard to know what needs improving if one does not have experience in areas outside of their field.

A person does a great disservice to themselves when they choose to isolate their realm of knowledge to a narrow field, no matter which field it is.

One of the big detractors that made programming very difficult for me was the fact that I couldn't find any practical application to what I was learning. As a result I felt unmotivated and dragged my feet for a very long time. Double clicking on Eclipse and following book instructions on how to make an array in Java for a class wasn't particularly interesting or fun to me. I always chucked it up as not bothering because I wasn't a 'math person', and this was probably something that only people who liked math would do. (I know I know)

It was only years later after I began delving into Linux and found a need to make something a bit more powerful than a bash script that I began developing an interest in programming again.

I'm sure there are many other capable and willing folks out there right now who feel the same way that I did. They want to learn but they don't see the point of it. Most courses at least don't really teach any real world applicability to what is being studied.

Exactly. Programming is a means to an end. One of the great joys of programming is making something that is useful, especially if it is useful to somebody else (points 1 and 2 here: http://henrikwarne.com/2012/06/02/why-i-love-coding/)

I had a similar experience, but from a slightly different perspective. I always found programming for the sake of programming to be sufficient motivation to spend time writing code. But when it comes to learning math, I have a really hard time caring about math in the abstract. Sitting me in a math class and having me memorize equations and formulas and operations, and solve a few word problems here and there (two boats leave point A, one going west, one going east, after one hour, blah, blah, blah) leaves me bored shitless for the most part. But if I have an application that matters to me, for the math I'm learning, I'm FAR more interested and willing to put in the time to learn the stuff.

Now that I'm trying to get deeper into Machine Learning stuff, I find myself motivated to go pick up books on Statistics and Linear Algebra and dig in, when I had very little interest in that stuff before.

I found cryptography, for example RSA, a great application of math and a neat example to see how math has real world applications.

Scribing was easy from the onset. But programming as it is today is not easy. Unless it evolved into plug-and-play-the-building-blocks, the profession of programming is going to stay.

And yet another cheap stab at many people reading HN. HN is filled with negativity --if not downright hatred-- towards nerds lately.

Items of zero value? A certain sci-fi author would beg to differ with you. Even someone that would have zero knowledge of anything else but would be mastering programming is still a technopriest. Even with zero knowledge about anything else but computers one still understand more about today's world than most people out there.

I'm not advocating refusing to learn other domains (I'm the kind of person who, when writing a book, decides to learn typography and typesetting software so I can typeset the book myself) but your cheap stab at young programmers (I'm 40) is uncalled for.

The world is going to shift to even more 0's and 1's. Many things are going to disappear and be replaced by 0's and 1's.

If there's one thing common to every single profession out there is that people need to read, write and communicate. And you know what? The tools allowing to read, write and communicate are written by the technopriests.

It's even more "scary" than that: the very infrastructure in place allowing people to communicate (like electricity and Internet) are, themselves, run using software. Not to mention very basic need like the entire infrastructure providing clean water to fullfill one of the most basic Maslow need.

There's no need for someone taking care of a network to understand what's inside the packets of information running through the network. All they need to know is that if there's no more Internet packets travelling worldwide, then there's no western civilization anymore.

The very foundation the entire society now relies on is software. If a worlwide EMP blast would render all computers useless tomorrow the world would probably turn to a mad max horror scenario in a few hours. No more water. No more electricity. No more food. Our logistics would be so screwed that "advanced" countries would fall into chaos. It's probable that in some places people would die after a few days because of the lack of drinkable water and it's very probable that in a few weeks many would die due to lack of food. Not to mention the nuclear facilities which would leak radioactivity left and right and break havoc.

Doctors aren't forced to understand how computers works to do their job. Most doctors are utterly clueless when it comes to technology: they're bound to live in fear of being hacked and not understanding what's going on when they connect to their online banking account and not understand why this or that mainstream article tell them to disable Java in their Mac. I've got doctor friends: they simply don't understand the world they're living in. We're already in the technopriest age. And they're asking me questions, lots of them.

The most computer-wise knowledgable doctor I know was thinking that the latest state of the art way to diagnose using computers was still to use an "expert system", filled by doctors. That's not how it works. These "experts" aren't able to process the amount of information a computer can process and can't find the correlation a computer software can find. Which is why now machines are trained with gigantic amount of information and suggesting exams and deceases to look for that are way more relevant than what doctors would suggest.

I think you got it totally backwards: it's a lot of the other professions that are going to disappear. Replaced by robots, machine learning algorithms, software and... The technopriests.

The ones still able to somehow understand the world they're living in and still able to write the world they're living in.

P.S: regarding mainstream economics I'd like to point out that Krugman, Nobel Prize winner, recently said that it wasn't a bad idea to mint a one trillion coin to deal with the U.S. debt SNAFU. Sure. Why not mint 26 of them and be done with the U.S. public debt!? That is the kind of economics most economics and most universities do teach worldwide: Keynesian economics. I happen to think Keynes was all wrong and keynesians have never been able to predict the consequences of their interventions more than a few months/years forward. There are economists from other schools who predicted 15 years before it happened, before the first euro was even circulating, that the euro would lead to: too many houses in spain, too many public servants in France, too many industries in Germany and who explained by which mechanism Greece and Spain would eventually default. Not a single Keynesian has ever been able to do a prediction that precise. That's all I need to know about "economics": that the mainstream is all wrong.

I do also think you put way too much faith in doctors: these people really aren't nearly half as expert as you think in their field. And they are the ones getting replaced today by sofware and robots. There's simply no way a surgeon can be as precise and have as many axis of rotation compared to today robotic arms (explained to me by a surgeon friend). There's also simply no way a doctor can read blood samples and other exams results and be able to correlate that with hundreds of thousands of other results and hence make more correct deduction as to what's going on.

If we eventually end up one day with true AI then everybody becomes meaningless because that day there ain't going to be doctors nor economists anymore.

Until that day programmers (even the one knowing nothing besides 0s and 1s and how 0s and 1s move around) are going to be more and more like the technopriests.

I think you two are coming two extreme ends of the spectrum. He's coming from the "clueless one-dimensional engineers" end of the scale, and you're coming from the "we are digital gods" end.

The truth lies somewhere down the middle, though I think you're a bit more extreme on your end of the scale than he is.

It's hard to take your views seriously when you describe your kind as "technopriests", and claim that people understanding nothing but computers "understand more about today's world than most people out there". This is a laughable claim.

I'm sorry, I can't get over this. Technopriest? This is the real world, not Snow Crash.

> "Many things are going to disappear and be replaced by 0's and 1's."

Yes, and they are being replaced by 0's and 1's in specific spaces where those doing the replacing must understand non-computer things about the space. Want to automate the entire traffic control system (LA just finished doing this)? Sorry, you have to know a great deal about transportation.

Want to automate food production? Sorry, you must know a great deal about both manufacturing and food. You can know all you want about computers, but unless you know these other topics you're useless. Well, you could be coding to a spec from someone who actually has a broad base of knowledge - a cog in the machine at that point.

The future belongs to people who have a deep understanding of computers and [insert relevant field]. Those who understand just computers have only a future pounding keyboards and not making decisions.

You know what, you're right - there will be "technopriests" in the future - but they will be the ones with a broad base of knowledge on top of technological mastery. They will not be the ones who understand tech and nothing else - those will be the digital equivalent of janitors.

Though they might fancy themselves technopriests while the world passes them by.

Is an incoherent rant like this an uncharacteristic indulgence for a technopriest? Or are you just a fan of technopriests, not being one yourself?

Everyone in our increasingly automated gift economy lives in fear of being cut off from the support of the layers of technology they rely upon for all their needs, all the way up your vaunted Maslow hierarchy.

You shouldn't romanticize this state of affairs, and you should not crow about the special role of the priestly class. In my opinion you should think soberly between now and your 50th birthday about how you can contribute to a global society that is both more stable and more technologically advanced, and try to forget about the futurism that was peddled to you ( and all of us) by Wired magazine in 1994.

I didn't read it as a stab at nerds or young programmers but more like an advice that domain knowledge still is important beyond pure programming skills. Maybe the comment was formulated a littel bit over tthe top, but well, I'm doing that quite regularly.

I completely agree that the world is running on software right now, but the world isn't software ITSELF (well, not yet).

On the other hand, people being cracks in there field claiming that there field is the only one that counts are just arrogant. No mater if they a programmers, accountants, mech. engineers, doctors, car mechanics or what not. And yes, software written by people without the slightest idea of the purpose of said software tends to be not so good.

> without the slightest idea of the purpose of said software

In the OPs specific example, the purpose of the network is to carry packets, and your job is to make sure packets are delivered. Whether they carry orders to launch nukes, or donations to charity isn't the purpose.

The point is that you need to be well acquainted with the problem that you're trying to solve. If you're developing a new network protocol then yes, you don't need to know what kind of information is going to flow through the network, you need to know about network protocols. On the other hand, if you're developing a business application then you better know how that business works.

I love the "takedown" of Keynesian/mainstream economics in the middle of this rant.

Any other centuries-old disciplines your knowledge of Big-O notation and compilers qualifies you to discredit? Oh, modern medicine? Good for you.

This guy takes the "hubris" as a virtue line way too seriously.

The trillion dollar coin wasn't supposed to deal with US debt, it was a trick to get around the debt cap rule that Congress imposed on the government.

If they actually spent the trillion dollar coin, that would likely cause devaluation of the dollar; as long as the coin remains locked up in the treasury it's just an accounting trick to get around their own arbitrary rule and wouldn't cause devaluation, because everyone buying dollars knows it's just a stupid accounting trick and not actual money.

Reply on news.ycombinator.com