13 ms·

I've never seen a dev stack in docker actually work. What I see is the poor new guy spending several hours trying to get docker working and configuring private

by wrldos 4y ago

I've never seen a dev stack in docker actually work. What I see is the poor new guy spending several hours trying to get docker working and configuring private repositories that don't work, then nothing works when they finally get it up which results in the dude spending at least 2 more days trying to reverse engineer the shit show or consult little pockets of knowledge hiding in out of date confluence documents and other people's heads who are on holiday.

dopidopHN 4y ago
I’ve been in mostly dis functional software company. And … that’s not my experience. I least not lately. 10 years ago : absolutely. But nowadays it’s a docker command or a git pull then yarn/gradle/whatever … and if that does not work something is wrong and a ticket is raised.
- Akronymus 4y ago
  "What is a git pull" "what is a yarn? Gradle?" Theres already a lotnof complexity in those "simple" parts
  - xboxnolifes 4y ago
    You're reaching really fucking hard here.
    - wrldos 4y ago
      They're really not. I have two guys unfucking a yarn and NPM shit show at the moment.
    - Akronymus 4y ago
      How so? Is it really that inconceivable that someone has never experienced those before? From personal experience, I used to use TFS for version control for a few years before using git at my newer job. I also never once had to deal with yarn or gradle. And I also know from experience, that you can make a unmaintainable mess in every build system. Also, who is gonna teach the juniors how to use the tools, if everyone sets that knowledge as mandatory? Or do you expect everyone to learn it in their free time before starting any tech job?
      - dopidopHN 4y ago
        Don’t you have automated builds? The step in those builds should works on developer machines. Is that too much to ask? If the step in the build do not work? How did that get merged in the first place ?
        Akronymus 4y ago
        > Don’t you have automated builds? Ideally, you would > The step in those builds should works on developer machines. Is that too much to ask? Quite often, yes. (Secrets that are only on the build server/shared database you cna't connect to without a barely working VPN and such) > If the step in the build do not work? How did that get merged in the first place ? Because there is no CI/CD pipeline to stop you? There are tons of reasons why it can be extremely hard to get into a legacy project as a new person. And that's just setting it up. Ideally, this wouldn't be the case. But sadly, the real world sucks
        dopidopHN 4y ago
        Man, you’re bringing me back a long long while ago. Last time I worked without reproducible builds was 2005-ish ? My experience : once someone in the C-suite vicinity enforce a lock-down, things fall in place rather quickly. Ex : nothing get deploy manually. I don’t care if we miss the next prod push, we will catch the next one. > the real world sucks My work is as grounded in the real world as well. And I spend year contracting for bottom feeders company. Hard to do more real crap. At some point is valuable to define priorities. > Because there is no CI/CD pipeline to stop you? There are tons of reasons why it can be extremely hard to get into a legacy project as a new person Fine. But lack of validation should not be a reason. If no pipeline checks and no humans checks as well. Then you are deploying un-vetted software.
  - dopidopHN 4y ago
    Ok, then something is wrong in the hiring process. I assume familiarity with standards tools of the tech stack.

by wrldos 4y ago

dopidopHN 4y ago

I’ve been in mostly dis functional software company. And … that’s not my experience. I least not lately. 10 years ago : absolutely. But nowadays it’s a docker command or a git pull then yarn/gradle/whatever … and if that does not work something is wrong and a ticket is raised.

Akronymus 4y ago
"What is a git pull" "what is a yarn? Gradle?" Theres already a lotnof complexity in those "simple" parts
- xboxnolifes 4y ago
  You're reaching really fucking hard here.
  - wrldos 4y ago
    They're really not. I have two guys unfucking a yarn and NPM shit show at the moment.
  - Akronymus 4y ago
    How so? Is it really that inconceivable that someone has never experienced those before? From personal experience, I used to use TFS for version control for a few years before using git at my newer job. I also never once had to deal with yarn or gradle. And I also know from experience, that you can make a unmaintainable mess in every build system. Also, who is gonna teach the juniors how to use the tools, if everyone sets that knowledge as mandatory? Or do you expect everyone to learn it in their free time before starting any tech job?
    - dopidopHN 4y ago
      Don’t you have automated builds? The step in those builds should works on developer machines. Is that too much to ask? If the step in the build do not work? How did that get merged in the first place ?
      - Akronymus 4y ago
        > Don’t you have automated builds? Ideally, you would > The step in those builds should works on developer machines. Is that too much to ask? Quite often, yes. (Secrets that are only on the build server/shared database you cna't connect to without a barely working VPN and such) > If the step in the build do not work? How did that get merged in the first place ? Because there is no CI/CD pipeline to stop you? There are tons of reasons why it can be extremely hard to get into a legacy project as a new person. And that's just setting it up. Ideally, this wouldn't be the case. But sadly, the real world sucks
        dopidopHN 4y ago
        Man, you’re bringing me back a long long while ago. Last time I worked without reproducible builds was 2005-ish ? My experience : once someone in the C-suite vicinity enforce a lock-down, things fall in place rather quickly. Ex : nothing get deploy manually. I don’t care if we miss the next prod push, we will catch the next one. > the real world sucks My work is as grounded in the real world as well. And I spend year contracting for bottom feeders company. Hard to do more real crap. At some point is valuable to define priorities. > Because there is no CI/CD pipeline to stop you? There are tons of reasons why it can be extremely hard to get into a legacy project as a new person Fine. But lack of validation should not be a reason. If no pipeline checks and no humans checks as well. Then you are deploying un-vetted software.
- dopidopHN 4y ago
  Ok, then something is wrong in the hiring process. I assume familiarity with standards tools of the tech stack.