3 ms·

In this scenario he'd just be told exactly which nails to pound and his work would be inspected. This is a very good example actually, construction work is a re

In this scenario he'd just be told exactly which nails to pound and his work would be inspected. This is a very good example actually, construction work is a really popular summer gig for students in my country (Poland). They know nothing and don't care about the domain (building houses), they just follow supervisors and the designs. You can't give them an entire house to build, but they are very useful and cheap members of the crew. They'll never be architects (they don't want to), but they'll earn enough to buy whatever students want and they'll always find some work no matter what is being built and where.

AuthorizedCust 4y ago
In other words, the supervisor holds the vision of the output, and that person assures that the people interested in the craft are acting towards creating the desired output.
- baremetal 4y ago
  1. A supervisor will demonstrate what is expected. 2. Then the worker tries it while the supervisor watches. 3. Feedback is given 4. Repeat 2-4 until satisfactory work is achieved. Depending on the task this may be as little as 5 minutes for something simple or much longer for more complicated things.[1] [1] I own a rough framing business
aynyc 4y ago
I worked construction in high school and college in the US. This is not how it generally works. If you are a high school kid, your summer construction gig is usually slave labor, meaning carrying ton of stuff up and down, cleaning stuff as you go and be a general gopher. You don't do anything remotely close to the construction of the house. The only exception is being a roofer, which you just tar stuff with other crew members.
- amonith 4y ago
  I think that's a bit outside of the topic, because we're now discussing a case of "only passion, 0 knowledge" which was not the point. The author of the article thinks that not looking at the bigger picture (or the upper "decision level" if you will) is inherently wrong. My point is that enjoying the process and not caring about the product is more than enough realistically. So assume a worker that perfectly knows and likes their job, but doesn't care about the process "above" him. If you enjoy the process of tiling and you have some experience with tiling, you don't have to care about what kind of building/room you are working on. Somebody designed the room, somebody picked the right materials, somebody probably bought them and it's in the spec/design. You can just "tile away" and make a career out of it. Similarly in software, if you care only about programming and languages and whatnot and not the product - it's all you need with the right team/org. You won't be a product owner and you wont advance to "decision-making" levels in the company, but if you don't want to why would you need to.
  - aynyc 4y ago
    I can't really agree to what you are describing, despite the fact that certain parts of my career, I fit your description perfectly. The issue I have with is the statement of "make a career out of it". I don't think you can, at least not in the software industry, a lot of folks are perfectly competent developers but can't move forward and eventually get replaced by younger/cheaper developers because they are basically doing the same thing for the past 10 years. I agree with having passions for something, but making a career out of it is a lot harder if you don't do the "extra".
    - amonith 4y ago
      > a lot of folks are perfectly competent developers but can't move forward and eventually get replaced by younger/cheaper developers because they are basically doing the same thing for the past 10 years I'd argue that they are replaced (if they are, because I'm not sure, there are not a lot of old folk because IT industry is pretty young, I already worked with a few 50+ mid devs and the pay is kinda reverse, because old folk already have homes and don't need to pay off huge mortgages) not because they didn't get promoted (mid dev -> product owner / domain expert) but because they stopped upgrading the skills relevant to their current job. So in terms of the example presented by the author it would be developers that are no longer even hyped about languages/tools. And in our imaginary "tiling specialist" it would be a guy that didn't care that the current fad is some kind of funky pattern + new material of tiles and still wanted to lay old ceramic square tiles for his entire life. I'm still not convinced that there is a scenario where you __have to__ care about "the domain" / "the problem being solved" / "the bigger picture" that much. You can, it will improve some aspects of your career, but you don't have to and it would degrade other aspects of said career (we all have about 16h max productive hours daily, and I'm being generous).
- moremetadata 4y ago
  There isnt anything stopping you from asking questions like why is something done this way. You might see it as slave labour, but if you laid bricks for example, you cant lay bricks in temperatures below 3 or 4 degrees C, and you can only lay so many rows of bricks high as the mortar has to set. Where most people are failed by those around them, like parents and school's is pointing out when you leave education, you wont stop learning, and its always good to ask questions and plan ahead what you want to do with your life. Arguably have a bucket list which will change as you age in order to have something to aim for, and dont get caught in the trap of settling for second best or end up being used by people who think might be your friends but only knew you because of what you could do for them on the cheap. Now you might have called your summer job slave labour, I look at it as being paid to exercise as well as learning new skills and make new contacts. On the subject of aimless excited programmers, there's lots of ways to look at programming before learning a language. If one wants to earn a lot of money, then consider database related programming, everything is data, even spreadsheets can be considered flat files of sorts. And whilst you probably wouldnt use javascript to write a database app in, even though you could stuff data into a cookie and run it client side, there are better general purpose languages suited to database work, besides the obvious sql languages. If chasing the money, consider looking at what's involved in high frequency trading where you'll be writing your own OS to maintain the super high speeds required for algorithmic trading. Co-locating data centres as close as possible to trading exchanges is just one part of the problem. [1] IF you want to do apps for smart phones, again look at the languages that deliver the most for you, but also consider whether you should go with a popular language like dotnet or java thats portable across platforms, or whether you want to go with a niche language that might become less popular over time especially when considering there are thousands of languages that exist, with many having fallen by the wayside. [1] https://www.ted.com/talks/kevin_slavin_how_algorithms_shape_our_world/transcript https://www.ted.com/talks/kevin_slavin_how_algorithms_shape_...

AuthorizedCust 4y ago

In other words, the supervisor holds the vision of the output, and that person assures that the people interested in the craft are acting towards creating the desired output.

baremetal 4y ago
1. A supervisor will demonstrate what is expected. 2. Then the worker tries it while the supervisor watches. 3. Feedback is given 4. Repeat 2-4 until satisfactory work is achieved. Depending on the task this may be as little as 5 minutes for something simple or much longer for more complicated things.[1] [1] I own a rough framing business

aynyc 4y ago

I worked construction in high school and college in the US. This is not how it generally works. If you are a high school kid, your summer construction gig is usually slave labor, meaning carrying ton of stuff up and down, cleaning stuff as you go and be a general gopher. You don't do anything remotely close to the construction of the house. The only exception is being a roofer, which you just tar stuff with other crew members.

amonith 4y ago
I think that's a bit outside of the topic, because we're now discussing a case of "only passion, 0 knowledge" which was not the point. The author of the article thinks that not looking at the bigger picture (or the upper "decision level" if you will) is inherently wrong. My point is that enjoying the process and not caring about the product is more than enough realistically. So assume a worker that perfectly knows and likes their job, but doesn't care about the process "above" him. If you enjoy the process of tiling and you have some experience with tiling, you don't have to care about what kind of building/room you are working on. Somebody designed the room, somebody picked the right materials, somebody probably bought them and it's in the spec/design. You can just "tile away" and make a career out of it. Similarly in software, if you care only about programming and languages and whatnot and not the product - it's all you need with the right team/org. You won't be a product owner and you wont advance to "decision-making" levels in the company, but if you don't want to why would you need to.
- aynyc 4y ago
  I can't really agree to what you are describing, despite the fact that certain parts of my career, I fit your description perfectly. The issue I have with is the statement of "make a career out of it". I don't think you can, at least not in the software industry, a lot of folks are perfectly competent developers but can't move forward and eventually get replaced by younger/cheaper developers because they are basically doing the same thing for the past 10 years. I agree with having passions for something, but making a career out of it is a lot harder if you don't do the "extra".
  - amonith 4y ago
    > a lot of folks are perfectly competent developers but can't move forward and eventually get replaced by younger/cheaper developers because they are basically doing the same thing for the past 10 years I'd argue that they are replaced (if they are, because I'm not sure, there are not a lot of old folk because IT industry is pretty young, I already worked with a few 50+ mid devs and the pay is kinda reverse, because old folk already have homes and don't need to pay off huge mortgages) not because they didn't get promoted (mid dev -> product owner / domain expert) but because they stopped upgrading the skills relevant to their current job. So in terms of the example presented by the author it would be developers that are no longer even hyped about languages/tools. And in our imaginary "tiling specialist" it would be a guy that didn't care that the current fad is some kind of funky pattern + new material of tiles and still wanted to lay old ceramic square tiles for his entire life. I'm still not convinced that there is a scenario where you __have to__ care about "the domain" / "the problem being solved" / "the bigger picture" that much. You can, it will improve some aspects of your career, but you don't have to and it would degrade other aspects of said career (we all have about 16h max productive hours daily, and I'm being generous).
moremetadata 4y ago
There isnt anything stopping you from asking questions like why is something done this way. You might see it as slave labour, but if you laid bricks for example, you cant lay bricks in temperatures below 3 or 4 degrees C, and you can only lay so many rows of bricks high as the mortar has to set. Where most people are failed by those around them, like parents and school's is pointing out when you leave education, you wont stop learning, and its always good to ask questions and plan ahead what you want to do with your life. Arguably have a bucket list which will change as you age in order to have something to aim for, and dont get caught in the trap of settling for second best or end up being used by people who think might be your friends but only knew you because of what you could do for them on the cheap. Now you might have called your summer job slave labour, I look at it as being paid to exercise as well as learning new skills and make new contacts. On the subject of aimless excited programmers, there's lots of ways to look at programming before learning a language. If one wants to earn a lot of money, then consider database related programming, everything is data, even spreadsheets can be considered flat files of sorts. And whilst you probably wouldnt use javascript to write a database app in, even though you could stuff data into a cookie and run it client side, there are better general purpose languages suited to database work, besides the obvious sql languages. If chasing the money, consider looking at what's involved in high frequency trading where you'll be writing your own OS to maintain the super high speeds required for algorithmic trading. Co-locating data centres as close as possible to trading exchanges is just one part of the problem. [1] IF you want to do apps for smart phones, again look at the languages that deliver the most for you, but also consider whether you should go with a popular language like dotnet or java thats portable across platforms, or whether you want to go with a niche language that might become less popular over time especially when considering there are thousands of languages that exist, with many having fallen by the wayside. [1] https://www.ted.com/talks/kevin_slavin_how_algorithms_shape_our_world/transcript https://www.ted.com/talks/kevin_slavin_how_algorithms_shape_...