4 ms·

How old are you?

by diminoten 8y ago

How old are you?

toomuchtodo 8y ago
Almost 40, 20+ years of tech experience.
- diminoten 8y ago
  Are you concerned that you're taking a stance here that's more reflective of your years of experience than of the changing trends in tech? Experience can be a crutch too, especially in a field that gets upended by new concepts every 3-5 years. I hope you're cognizant of that. What worked 5 years ago is a joke today, in many cases.
  - toomuchtodo 8y ago
    Not concerned at all. I get paid to de-risk, not to ride the hype train. > What worked 5 years ago is a joke today, in many cases. Postgresql was first released in 1997. Lots of the web still runs on PHP, Python 2, and large amounts of Java. What you call a joke, I call a sustainable business and an amortized cost. No one is paying you to use shiny tools, they're paying you to solve business problems.
    - diminoten 8y ago
      Refusing to adopt innovation because it doesn't match with what you knew when you were a technical contributor is risky, too. Sticking to Python2 is risky. Using a version of Postgres released 5 years ago (9.3) is risky, using legacy PHP is risky, relying on the JVM and Java developers to solve problems that other tech stacks solve faster/better is risky. What you call a sustainable business with amortized costs I call an un-turnable ship that wastes money dealing with problems that were solved years ago.
      - toomuchtodo 8y ago
        I think you misunderstand. I am not refusing to adopt innovation. I'm refusing to be underpaid to "innovate". If you want to spend sleepless nights troubleshooting beta software in production, it is not my place to stop you. It is my place to not recommend said software to businesses, and this is extremely easy to demonstrate to decision makers. If you do recommend software to a business that isn't proven (and Kubernetes is still very much unproven, it's first release was only 3 years ago), and it fails, you should be accountable for your poor judgement.
        diminoten 8y ago
        The only misunderstanding that's taking place here is how unproven you think the tech being discussed is. No one is suggesting you spend sleepless nights troubleshooting beta software in production. K8s is not beta software, and the fact that you have to misrepresent my position as such is a pretty good indicator that you don't find my actual position (use solid software even if it's new, as long as it's solid, which k8s is) to be objectionable. I wish you'd start there...
        toomuchtodo 8y ago
        We disagree k8s is solid, so no further discussion is necessary. You questioned the maturity of an IRC client that was only 3 years old [1]. But that's enough time for Kubernetes to be a mature orchestration framework, to be relied upon as critical infrastructure? Yes, more development resources have been committed to Kubernetes, but that does not make it solid. [1] https://news.ycombinator.com/item?id=18408813 https://news.ycombinator.com/item?id=18408813
        diminoten 8y ago
        For the people reading this who might be on the fence about k8s and its "solidness", keep in mind that hostility like what's being shown here is exactly the kind of thing that holds good tech back. Don't fall for this evidence-less claim, look at what people are accomplishing and the issues they're running into. Find the positivity about the tech, and see what those people have trouble with. Tons of case studies to demonstrate, resoundingly, that k8s is "solid": https://kubernetes.io/case-studies/ https://kubernetes.io/case-studies/ . See what these people struggled with, and that'll give you a better idea of who's right here.
    - anarazel 8y ago
      Postgres maintains 5 years worth of major releases, not more. After that no more fixes for data corruption, security issues etc. IOW, using that old a version of postgres is careless, and might even bring legal liability after an intrusion (or just data loss). https://www.postgresql.org/support/versioning/ https://www.postgresql.org/support/versioning/

How old are you?

toomuchtodo 8y ago

Almost 40, 20+ years of tech experience.

diminoten 8y ago
Are you concerned that you're taking a stance here that's more reflective of your years of experience than of the changing trends in tech? Experience can be a crutch too, especially in a field that gets upended by new concepts every 3-5 years. I hope you're cognizant of that. What worked 5 years ago is a joke today, in many cases.
- toomuchtodo 8y ago
  Not concerned at all. I get paid to de-risk, not to ride the hype train. > What worked 5 years ago is a joke today, in many cases. Postgresql was first released in 1997. Lots of the web still runs on PHP, Python 2, and large amounts of Java. What you call a joke, I call a sustainable business and an amortized cost. No one is paying you to use shiny tools, they're paying you to solve business problems.
  - diminoten 8y ago
    Refusing to adopt innovation because it doesn't match with what you knew when you were a technical contributor is risky, too. Sticking to Python2 is risky. Using a version of Postgres released 5 years ago (9.3) is risky, using legacy PHP is risky, relying on the JVM and Java developers to solve problems that other tech stacks solve faster/better is risky. What you call a sustainable business with amortized costs I call an un-turnable ship that wastes money dealing with problems that were solved years ago.
    - toomuchtodo 8y ago
      I think you misunderstand. I am not refusing to adopt innovation. I'm refusing to be underpaid to "innovate". If you want to spend sleepless nights troubleshooting beta software in production, it is not my place to stop you. It is my place to not recommend said software to businesses, and this is extremely easy to demonstrate to decision makers. If you do recommend software to a business that isn't proven (and Kubernetes is still very much unproven, it's first release was only 3 years ago), and it fails, you should be accountable for your poor judgement.
      - diminoten 8y ago
        The only misunderstanding that's taking place here is how unproven you think the tech being discussed is. No one is suggesting you spend sleepless nights troubleshooting beta software in production. K8s is not beta software, and the fact that you have to misrepresent my position as such is a pretty good indicator that you don't find my actual position (use solid software even if it's new, as long as it's solid, which k8s is) to be objectionable. I wish you'd start there...
        toomuchtodo 8y ago
        We disagree k8s is solid, so no further discussion is necessary. You questioned the maturity of an IRC client that was only 3 years old [1]. But that's enough time for Kubernetes to be a mature orchestration framework, to be relied upon as critical infrastructure? Yes, more development resources have been committed to Kubernetes, but that does not make it solid. [1] https://news.ycombinator.com/item?id=18408813 https://news.ycombinator.com/item?id=18408813
        diminoten 8y ago
        For the people reading this who might be on the fence about k8s and its "solidness", keep in mind that hostility like what's being shown here is exactly the kind of thing that holds good tech back. Don't fall for this evidence-less claim, look at what people are accomplishing and the issues they're running into. Find the positivity about the tech, and see what those people have trouble with. Tons of case studies to demonstrate, resoundingly, that k8s is "solid": https://kubernetes.io/case-studies/ https://kubernetes.io/case-studies/ . See what these people struggled with, and that'll give you a better idea of who's right here.
  - anarazel 8y ago
    Postgres maintains 5 years worth of major releases, not more. After that no more fixes for data corruption, security issues etc. IOW, using that old a version of postgres is careless, and might even bring legal liability after an intrusion (or just data loss). https://www.postgresql.org/support/versioning/ https://www.postgresql.org/support/versioning/