4 ms·

Why even bother with a fake language when so often the industry has devolved into some sick level of honest negligence? For example: rarely do candidates need

Why even bother with a fake language when so often the industry has devolved into some sick level of honest negligence? For example: rarely do candidates need to know JavaScript anymore or even some unnecessary framework. Now people trade in experience of some tool that says nothing of anything: React Flux Capacitor (or some other bullshit like they want to go back in time to make lots of money without any real skills). Now if you ask these candidates some junior developer question outside of React Flux Capacitor bullshit they are not only hopelessly lost, but expect to be treated as a senior principal.

that_guy_iain 6y ago
Honestly, the thing I hate the most about IT is how bad it is while no one admits to it. These are problems I've encountered at several companies: * No budget for tooling. Be that software outside the ide or be it for hardware. * Cargo cult is so much bigger than anyone will ever admit. * The lack of caring about other departments. We're a team and we need to work as a team so the company can make money to pay our salaries. I've seen it to the point where one guy was willing to cause two departments weeks worth of work to avoid doing two days worth of work. * The amount of stuff that is just broken, people keep complaining about it being broken and it causes a pile of hassle for other people but just stays broken. Or it's point out it's broken and a big meeting is called to deal with it and then nothing is really done. * The amount of people who don't know what they're doing. So many people seem to have 1-year * x experience. They reach a certain level and they just stop. * The amount of people who don't even know what they're talking about - https://toggl.com/track/developer-methods-infographic/ https://toggl.com/track/developer-methods-infographic/ a prime example, kanban is literally how they make cars it's we work on one bit and the next area deals with the next part. The image should have a car manufactoring factory as is. But instead they have nonsense. * The amount of patting themselves on the back saying we're doing a great job while the system sucks and nothing is getting better and employee churn is sky high. Honestly, I think if people from other industries worked in IT for a year they would be completely shocked at how crap it is. I don't even think the hiring part is wrong, I think the entire management process of IT is wrong and causes more chaos so you end up with people who are heavily specilised in tools who are considered expert engineers but can't read UML.
- arethuza 6y ago
  In my experience proficiency in UML almost always indicates that someone is not what I would regard as an "expert engineer".
  - that_guy_iain 6y ago
    In my experience if someone can't read UML and know how to write a decorator pattern something is up. Honestly, I've never used it in depth but for design patterns I expect people who are "seniors" to understand it. And I expect any expert to be able to look at UML and get the gist of it. On a side note about design patterns, once as a junior I was at a digital agency and they were doing an in-house tech talk where one of the leads was giving an explaination and he was showing the singleton pattern but what they had allowed for two instances and when I tried to make it clearer to the intern that normally there is only one instance per singleton. The two leads were "Yea but it's still a valid singleton" - it was not but I wasn't point that out directly but continued to make it clear that most people would expect a single instance when talking about a Singleton.
    - arethuza 6y ago
      What about all the different types of diagrams? Use cases, activity diagrams, deployment diagrams etc. Yeah - 'informal' UML use a lot of people are happy with but some things like exactly what some of the features of activity diagrams mean is amazingly badly understood by a lot of people. I'm ok with the 'UML as sketch' approach, but 'UML as blueprint' is a nightmare that I've never seen work: https://martinfowler.com/bliki/UmlAsSketch.html https://martinfowler.com/bliki/UmlAsSketch.html
      - that_guy_iain 6y ago
        Honestly, most of the time I use these diagrams just to give people the gist of what I'm talking about. And my diagrams are super low effort. Think low effort whiteboard diagrams during a meeting style. > Yeah - 'informal' UML use a lot of people are happy with but some things like exactly what some of the features of activity diagrams mean is amazingly badly understood by a lot of people. I'm talking super basic stuff like https://en.wikipedia.org/wiki/Decorator_pattern#/media/File:Decorator_UML_class_diagram.svg https://en.wikipedia.org/wiki/Decorator_pattern#/media/File:... > I'm ok with the 'UML as sketch' approach, but 'UML as blueprint' is a nightmare that I've never seen work: I agree, I would hate that.

that_guy_iain 6y ago

Honestly, the thing I hate the most about IT is how bad it is while no one admits to it. These are problems I've encountered at several companies: * No budget for tooling. Be that software outside the ide or be it for hardware. * Cargo cult is so much bigger than anyone will ever admit. * The lack of caring about other departments. We're a team and we need to work as a team so the company can make money to pay our salaries. I've seen it to the point where one guy was willing to cause two departments weeks worth of work to avoid doing two days worth of work. * The amount of stuff that is just broken, people keep complaining about it being broken and it causes a pile of hassle for other people but just stays broken. Or it's point out it's broken and a big meeting is called to deal with it and then nothing is really done. * The amount of people who don't know what they're doing. So many people seem to have 1-year * x experience. They reach a certain level and they just stop. * The amount of people who don't even know what they're talking about - https://toggl.com/track/developer-methods-infographic/ https://toggl.com/track/developer-methods-infographic/ a prime example, kanban is literally how they make cars it's we work on one bit and the next area deals with the next part. The image should have a car manufactoring factory as is. But instead they have nonsense. * The amount of patting themselves on the back saying we're doing a great job while the system sucks and nothing is getting better and employee churn is sky high. Honestly, I think if people from other industries worked in IT for a year they would be completely shocked at how crap it is. I don't even think the hiring part is wrong, I think the entire management process of IT is wrong and causes more chaos so you end up with people who are heavily specilised in tools who are considered expert engineers but can't read UML.

arethuza 6y ago
In my experience proficiency in UML almost always indicates that someone is not what I would regard as an "expert engineer".
- that_guy_iain 6y ago
  In my experience if someone can't read UML and know how to write a decorator pattern something is up. Honestly, I've never used it in depth but for design patterns I expect people who are "seniors" to understand it. And I expect any expert to be able to look at UML and get the gist of it. On a side note about design patterns, once as a junior I was at a digital agency and they were doing an in-house tech talk where one of the leads was giving an explaination and he was showing the singleton pattern but what they had allowed for two instances and when I tried to make it clearer to the intern that normally there is only one instance per singleton. The two leads were "Yea but it's still a valid singleton" - it was not but I wasn't point that out directly but continued to make it clear that most people would expect a single instance when talking about a Singleton.
  - arethuza 6y ago
    What about all the different types of diagrams? Use cases, activity diagrams, deployment diagrams etc. Yeah - 'informal' UML use a lot of people are happy with but some things like exactly what some of the features of activity diagrams mean is amazingly badly understood by a lot of people. I'm ok with the 'UML as sketch' approach, but 'UML as blueprint' is a nightmare that I've never seen work: https://martinfowler.com/bliki/UmlAsSketch.html https://martinfowler.com/bliki/UmlAsSketch.html
    - that_guy_iain 6y ago
      Honestly, most of the time I use these diagrams just to give people the gist of what I'm talking about. And my diagrams are super low effort. Think low effort whiteboard diagrams during a meeting style. > Yeah - 'informal' UML use a lot of people are happy with but some things like exactly what some of the features of activity diagrams mean is amazingly badly understood by a lot of people. I'm talking super basic stuff like https://en.wikipedia.org/wiki/Decorator_pattern#/media/File:Decorator_UML_class_diagram.svg https://en.wikipedia.org/wiki/Decorator_pattern#/media/File:... > I'm ok with the 'UML as sketch' approach, but 'UML as blueprint' is a nightmare that I've never seen work: I agree, I would hate that.