4 ms·

Lots of people in the industry are in a race against time to make as much money as possible before they have to understand how things work.

lliamander 5y ago
The implications for the future of this industry, if what you say is true, are profound.
- makeitdouble 5y ago
  Isn't it true for a lot of newish industries ? For instance we have the EV boom, and visibly a lot of companies are rushing in to try to make as much as they can without planning for what they would do if they become the next Toyota. But surely, some are planning a bit more ahead (or have a more long term viable approach, even if by accident), and time will tell who they are. My glass half full view would be that we don't need most companies to succeed, as long as the well isn't poisoned.
  - zer0tonin 5y ago
    The issue is that we're not that new anymore, people have been doing software engineering for at least half a century.
- 29athrowaway 5y ago
  In the beginning, if you wanted a computer, you had to design and build it yourself. You had to be an expert in electronics and computer science to do it. And back then, there were no computer parts. You had to manufacture everything yourself from vacuum tubes. Once you were done, you would have a tiny amount of memory and processing power to work with, meaning that you had to be an expert programmer to take advantage of that tiny processing power. And, there were no stored programs. Your program was implemented as an arrangement of cables on a plugboard, something that was error prone and time consuming. There were no compilers or interpreters for your code therefore no compiler errors, no runtime errors, no debugger, no anything. If things didn't work, they just didn't work and some types of mistakes would have disastrous effects on the hardware. Now, you don't need any of that. Yet, you can call yourself "full stack". No one truly full stack anymore.
  - w4ffl35 5y ago
    no one is saying to take it back to assembly, but at least maybe try to understand how asynchronous code works if you're going to try to program professional applications in Javascript.
w4ffl35 5y ago
I am self-taught and cringe when i think back to my early days because I knew so little and didn't realize it. I've never attended any CS courses and learned everything I know from putting in almost constant work on the side (I mean this literally, I almost only work on creative projects with all of my spare time) -- but I can't overstate how much I learned from people on the job as well, they propelled me to new heights. All this is to say: I don't begrudge newcomers and have always tried to give back more than what I got from others when I was Jr... But good lord bootcamps do not produce much in the way of talent in my experience. I'm sure there are some shining stars that benefited, but I have yet to meet one of them. One guy I worked with fully admitted to me in private that he plagiarized his "final" for bootcamp which was a rather difficult algorithm. He just used some open source code he found on github and only slightly modified it. The code he wrote that I had to support was some of the worst spaghetti I've had to pick apart and fix and he was the lead engineer for the company. These companies would make more money with proper talent. Code camps need to go away.
- brundolf 5y ago
  I've worked with many bootcampers and all but one have been fantastic. And the one wasn't bad because of arrogance or deception; they were a super nice person with plenty of integrity. They were bad at their job because they simply had no feel for programming, and would have been just as bad if they'd had a CS degree. Bootcamps are like anything: you get out what you put in. They are a(n often effective!) way of learning a skill. If there's a problem, it's with tech hiring and its ability to accurately evaluate candidates. But that's an intrinsically hard task, and I don't know if there's a real solution (and the inaccuracy cuts both ways, and affects everyone, regardless of where they learned to code). Stop inflating your own narrow experience and projecting it onto a huge swath of people. Pushing stereotypes is harmful.
  - w4ffl35 5y ago
    I gave an anecdote mentioning one shitty individual who would likely do shitty things even as a proper CS student yes. Beyond that I'm dissing the form of education, not the individual human. Maybe they're "nice" people but if they are leading a team of engineers right out of bootcamp, you're gonna have a bad time (and I've seen this happen in at least one occasion as I mentioned).
dragonly 5y ago
You are so right. People now in the industry know the mechanism of money and capital much better than software. But as a software engineer who loves the technology and products that we can build from it, I would really appreciate real DBAs with in-depth skills. After all, databases are essential, and we need experts.
- no-s 5y ago
  > I would really appreciate real DBAs with in-depth skills. heheh, I hear that all the time, but show me the money...

lliamander 5y ago

The implications for the future of this industry, if what you say is true, are profound.

makeitdouble 5y ago
Isn't it true for a lot of newish industries ? For instance we have the EV boom, and visibly a lot of companies are rushing in to try to make as much as they can without planning for what they would do if they become the next Toyota. But surely, some are planning a bit more ahead (or have a more long term viable approach, even if by accident), and time will tell who they are. My glass half full view would be that we don't need most companies to succeed, as long as the well isn't poisoned.
- zer0tonin 5y ago
  The issue is that we're not that new anymore, people have been doing software engineering for at least half a century.
29athrowaway 5y ago
In the beginning, if you wanted a computer, you had to design and build it yourself. You had to be an expert in electronics and computer science to do it. And back then, there were no computer parts. You had to manufacture everything yourself from vacuum tubes. Once you were done, you would have a tiny amount of memory and processing power to work with, meaning that you had to be an expert programmer to take advantage of that tiny processing power. And, there were no stored programs. Your program was implemented as an arrangement of cables on a plugboard, something that was error prone and time consuming. There were no compilers or interpreters for your code therefore no compiler errors, no runtime errors, no debugger, no anything. If things didn't work, they just didn't work and some types of mistakes would have disastrous effects on the hardware. Now, you don't need any of that. Yet, you can call yourself "full stack". No one truly full stack anymore.
- w4ffl35 5y ago
  no one is saying to take it back to assembly, but at least maybe try to understand how asynchronous code works if you're going to try to program professional applications in Javascript.

w4ffl35 5y ago

I am self-taught and cringe when i think back to my early days because I knew so little and didn't realize it. I've never attended any CS courses and learned everything I know from putting in almost constant work on the side (I mean this literally, I almost only work on creative projects with all of my spare time) -- but I can't overstate how much I learned from people on the job as well, they propelled me to new heights. All this is to say: I don't begrudge newcomers and have always tried to give back more than what I got from others when I was Jr... But good lord bootcamps do not produce much in the way of talent in my experience. I'm sure there are some shining stars that benefited, but I have yet to meet one of them. One guy I worked with fully admitted to me in private that he plagiarized his "final" for bootcamp which was a rather difficult algorithm. He just used some open source code he found on github and only slightly modified it. The code he wrote that I had to support was some of the worst spaghetti I've had to pick apart and fix and he was the lead engineer for the company. These companies would make more money with proper talent. Code camps need to go away.

brundolf 5y ago
I've worked with many bootcampers and all but one have been fantastic. And the one wasn't bad because of arrogance or deception; they were a super nice person with plenty of integrity. They were bad at their job because they simply had no feel for programming, and would have been just as bad if they'd had a CS degree. Bootcamps are like anything: you get out what you put in. They are a(n often effective!) way of learning a skill. If there's a problem, it's with tech hiring and its ability to accurately evaluate candidates. But that's an intrinsically hard task, and I don't know if there's a real solution (and the inaccuracy cuts both ways, and affects everyone, regardless of where they learned to code). Stop inflating your own narrow experience and projecting it onto a huge swath of people. Pushing stereotypes is harmful.
- w4ffl35 5y ago
  I gave an anecdote mentioning one shitty individual who would likely do shitty things even as a proper CS student yes. Beyond that I'm dissing the form of education, not the individual human. Maybe they're "nice" people but if they are leading a team of engineers right out of bootcamp, you're gonna have a bad time (and I've seen this happen in at least one occasion as I mentioned).

dragonly 5y ago

You are so right. People now in the industry know the mechanism of money and capital much better than software. But as a software engineer who loves the technology and products that we can build from it, I would really appreciate real DBAs with in-depth skills. After all, databases are essential, and we need experts.

no-s 5y ago
> I would really appreciate real DBAs with in-depth skills. heheh, I hear that all the time, but show me the money...