6 ms·

Hire great people with a passion for the trade and most employers won’t have to suffer through crap like this.

bdcravens 9y ago
I believe we're seeing a generation of developers with passions for things like client-side development and the "disruption" of cryptocurrency, who don't see the server-side as the true gold in the vault that it is.
- brailsafe 9y ago
  While I don't necessarily disagree, wouldn't this be more of an example of naive server-side development? One of the first things you learn—as an educated—front-end developer is that you don't trust the client.
  - bdcravens 9y ago
    True, except that in a lot of small teams, you see the same developers handling both.
    - bpicolo 9y ago
      It's not impossible (or even unusual) to do both competently. Helps that frontend is a smaller surface area.
      - bdcravens 9y ago
        I completely agree. I just think that we're seeing a category of developers that consider the front-end to be of higher priority, with everything that goes with that mindset.
        brailsafe 9y ago
        Do you feel as though there can be an objectively higher priority end of development? If so, why?
        bpicolo 9y ago
        Very business dependent, but typically speaking the brunt of development effort (for tech businesses) is going to be on the backend in terms of man hours. In some orgs it's like 100:1 backend:frontend (or more?).
        brailsafe 9y ago
        You certainly may be right about the ratio, but I think that this factor and the degree of importance are not mutually exclusive. At my last employer, this ratio was certainly present, and resulted in a sinful front-end implementation. The front-end was very important for customer experience (resulting in sales) but by the time management realized this, it was a massively arduous process to iterate on. Since server-side development was highly prioritized for a very long time, the two couldn't grow together, resulting in off the shelf solutions cobbled together with java server rendered static pages.
        bdcravens 9y ago
        Absolutely. Performance on the server costs money. Data breaches cost money. I'm sure someone can quantify whether using a jQuery plugin instead of a React component has a cost associated with it, but I'd venture to say it's on a magnitude of order less than server-side concerns. I don't know that I'd say priority should be 100:1, but at least 10:1.
  - dictum 9y ago
    MITM proxies are like port scanners - open secrets, trees full of low hanging fruit. Every developer should play with one. It's eye-opening.
    - brailsafe 9y ago
      Agreed.

I believe we're seeing a generation of developers with passions for things like client-side development and the "disruption" of cryptocurrency, who don't see the server-side as the true gold in the vault that it is.

brailsafe 9y ago
While I don't necessarily disagree, wouldn't this be more of an example of naive server-side development? One of the first things you learn—as an educated—front-end developer is that you don't trust the client.
- bdcravens 9y ago
  True, except that in a lot of small teams, you see the same developers handling both.
  - bpicolo 9y ago
    It's not impossible (or even unusual) to do both competently. Helps that frontend is a smaller surface area.
    - bdcravens 9y ago
      I completely agree. I just think that we're seeing a category of developers that consider the front-end to be of higher priority, with everything that goes with that mindset.
      - brailsafe 9y ago
        Do you feel as though there can be an objectively higher priority end of development? If so, why?
        bpicolo 9y ago
        Very business dependent, but typically speaking the brunt of development effort (for tech businesses) is going to be on the backend in terms of man hours. In some orgs it's like 100:1 backend:frontend (or more?).
        brailsafe 9y ago
        You certainly may be right about the ratio, but I think that this factor and the degree of importance are not mutually exclusive. At my last employer, this ratio was certainly present, and resulted in a sinful front-end implementation. The front-end was very important for customer experience (resulting in sales) but by the time management realized this, it was a massively arduous process to iterate on. Since server-side development was highly prioritized for a very long time, the two couldn't grow together, resulting in off the shelf solutions cobbled together with java server rendered static pages.
        bdcravens 9y ago
        Absolutely. Performance on the server costs money. Data breaches cost money. I'm sure someone can quantify whether using a jQuery plugin instead of a React component has a cost associated with it, but I'd venture to say it's on a magnitude of order less than server-side concerns. I don't know that I'd say priority should be 100:1, but at least 10:1.
- dictum 9y ago
  MITM proxies are like port scanners - open secrets, trees full of low hanging fruit. Every developer should play with one. It's eye-opening.
  - brailsafe 9y ago
    Agreed.