2 ms·

The best part about being SE are: 1) Iteration: We get to practice our stuff on real entities (language, OS, databases, etc). Do architects get to "practice" a

by sudeepj 10y ago

The best part about being SE are: 1) Iteration: We get to practice our stuff on real entities (language, OS, databases, etc). Do architects get to "practice" actual work at their home? Do new doctors get to try experimental surgeries? Do amateur civil engineers get to build those iconic bridges? They can do computer simulation ... but it is actually a software. 2) Hackathon: Can't imagine this happening in say medical field, mechanical engineering, law etc. Software Industry is one of few industries where this can be done. 3) Changing the world quietly: Many in my relatives are not programmers. It is hard to explain to them in what ways software is changing the world. 4) Open source: Imagine Coca Cola sharing its secret recipe. It won't but we as SE get to learn from open source projects. Now there is a cultural aspect to this but the point is that we as SE can experience it more than other professions.

saiya-jin 10y ago
adding to 1) - no real responsibility for bugs :) apart from few very specialized areas, you can do harm with bug but not harm/kill anybody. and we all do bugs, don't we
- majewsky 10y ago
  > apart from few very specialized areas, you can do harm with bug but not harm/kill anybody I'd still say that more bugs can kill people than you would expect. Many seemingly harmless bugs can be used (maybe chained together) to extract personal information out of systems, which is then used to prosecute people, or to justify putting them on a death list. > and we all do bugs, don't we Yes, sadly.
zootar 10y ago
1) Civil engineers and architects can design any bridge they want (though not build it). True, SEs can actually "build" any software they want, but without users it can be hard to tell how good it is. 2) What's the medical / engineering / legal equivalent of a hackathon that those professions aren't doing? Doctors and lawyers can always choose an interesting or deserving client (possibly pro bono), or do a research project. 3) If it's hard to explain, is it possible software isn't changing the world all that much? 4) Imagine Google sharing its Search code. It won't, but as lawyers get to learn from the best lawyers in any area of the law by reading their briefs and watching their trials (all public).

by sudeepj 10y ago

saiya-jin 10y ago

adding to 1) - no real responsibility for bugs :) apart from few very specialized areas, you can do harm with bug but not harm/kill anybody. and we all do bugs, don't we

majewsky 10y ago
> apart from few very specialized areas, you can do harm with bug but not harm/kill anybody I'd still say that more bugs can kill people than you would expect. Many seemingly harmless bugs can be used (maybe chained together) to extract personal information out of systems, which is then used to prosecute people, or to justify putting them on a death list. > and we all do bugs, don't we Yes, sadly.

zootar 10y ago

1) Civil engineers and architects can design any bridge they want (though not build it). True, SEs can actually "build" any software they want, but without users it can be hard to tell how good it is. 2) What's the medical / engineering / legal equivalent of a hackathon that those professions aren't doing? Doctors and lawyers can always choose an interesting or deserving client (possibly pro bono), or do a research project. 3) If it's hard to explain, is it possible software isn't changing the world all that much? 4) Imagine Google sharing its Search code. It won't, but as lawyers get to learn from the best lawyers in any area of the law by reading their briefs and watching their trials (all public).