4 ms·

Maybe because Agile is not what it should be. Managers love it Devs hate it. And every place I worked in, no one could do it right. It's not helping at all. It

Maybe because Agile is not what it should be. Managers love it Devs hate it. And every place I worked in, no one could do it right. It's not helping at all. It helps the manager to have more tools at his disposal to annoy the team, but it doesn't help the common folk. Also I'm tired to see people referring to seniors as old guys who worked as Devs for XX amount of years. Most of these people are stuck in a loop and know nothing about the new technologies and the younger generation has to teach them in the end. Also most of the senior Devs will move up in to manager positions and won't look back. None of my workplaces knew anything about SOLID principles, Design Patterns and all that fancy unicorn stuff because it looks lovely on paper but in the end it slows development down, so people avoid it. Most of the development work is done like we were monkeys with typewriters. But this is only my opinion. Take it with a pinch of salt.

obiefernandez 10y ago
so sad
- MrLeftHand 10y ago
  'so sad' as in, it makes you sad how I think of these things, or 'so sad' because you agree in some extent? Anyway, I think it's sad as well. The best example is to describe how our world works is where a job advert tells you to have X amount of experience with Y technology. You have Z skills, which is close to Y, but the only way to get the experience in Y is to get that, or similar jobs. But the company won't hire you, because you don't have Y. Even if you go and get Y in your spare time, that won't cut it because they want 'commercial' experience not home learning. Welcome to IT kids, where you have to be 2X years old, with 30 years of experience (commercial) and 3 degrees and Agile and 20 programming languages and... I wanted to have a good Agile experience so bad, that in every job I had, I fell flat on my face. And when I wanted them to change some things. I fell flat on my face. When I asked the 50 years old 'Senior Developer' why don't we use the Adapter Pattern, the response was a question. 'What's that?' When I wanted them to change from ant to maven? Sorry we don't have the time right now. Most of my friends who are developers as well are thinking to start their on business, or go into management, because they had enough. And all of them I would count as senior regarding their knowledge and experience. I can only talk from my experience. I am sure there are places, which are like nirvana for developers, but I haven't come across one yet.
  - obiefernandez 10y ago
    so sad because those places you describe as nirvana do exist and they're awesome. i get the impression that you were idealistic about some of this stuff in the past, but that idealism has been crushed over the years.
    - MrLeftHand 10y ago
      Sadly yes. I should have known better. Oh well, hope never dies.
br3w5 10y ago
Avoiding all that "fancy unicorn stuff" might not slow you down but it will slow down the next person who picks up your code but who cares that's their problem. You must come from the same school as "who needs tests they're a waste of time".
- MrLeftHand 10y ago
  By calling it "fancy unicorn stuff" I mean, it is really hard to come by in real life. Because generally people avoid it and when they don't, they usually use it in a completely wrong way. I saw a Singleton pattern which made me carve my eyes out. And that came from a guy, who was a Senior Developer. And most of the times being a developer is about working with legacy code and trying to fix loads of problems, which wont be fixed in the end because there is not enough time, money and energy and so on and so on and... This makes loads of experienced people move in to management, or creating their own business, because they had enough of the trench work. That's why you won't see talented people on the market. Because they know... Oh and no, I'm not from that school. But having tests doesn't mean the tests are any good. You can have loads of methodologies, patterns, principles. If you can't tell when to use a Factory Pattern, or how to implement SOLID, then it doesn't matter how much you like, or want them.
  - br3w5 10y ago
    Ok I retract my tests comment! Design patterns can definitely be abused and pragmatism is important when deciding whether or not to use them. I would say though that implementing SOLID is certainly achievable if writing from scratch but harder when refactoring code that breaks those principles (usually badly with no tests or poor tests).

obiefernandez 10y ago

so sad

MrLeftHand 10y ago
'so sad' as in, it makes you sad how I think of these things, or 'so sad' because you agree in some extent? Anyway, I think it's sad as well. The best example is to describe how our world works is where a job advert tells you to have X amount of experience with Y technology. You have Z skills, which is close to Y, but the only way to get the experience in Y is to get that, or similar jobs. But the company won't hire you, because you don't have Y. Even if you go and get Y in your spare time, that won't cut it because they want 'commercial' experience not home learning. Welcome to IT kids, where you have to be 2X years old, with 30 years of experience (commercial) and 3 degrees and Agile and 20 programming languages and... I wanted to have a good Agile experience so bad, that in every job I had, I fell flat on my face. And when I wanted them to change some things. I fell flat on my face. When I asked the 50 years old 'Senior Developer' why don't we use the Adapter Pattern, the response was a question. 'What's that?' When I wanted them to change from ant to maven? Sorry we don't have the time right now. Most of my friends who are developers as well are thinking to start their on business, or go into management, because they had enough. And all of them I would count as senior regarding their knowledge and experience. I can only talk from my experience. I am sure there are places, which are like nirvana for developers, but I haven't come across one yet.
- obiefernandez 10y ago
  so sad because those places you describe as nirvana do exist and they're awesome. i get the impression that you were idealistic about some of this stuff in the past, but that idealism has been crushed over the years.
  - MrLeftHand 10y ago
    Sadly yes. I should have known better. Oh well, hope never dies.

br3w5 10y ago

Avoiding all that "fancy unicorn stuff" might not slow you down but it will slow down the next person who picks up your code but who cares that's their problem. You must come from the same school as "who needs tests they're a waste of time".

MrLeftHand 10y ago
By calling it "fancy unicorn stuff" I mean, it is really hard to come by in real life. Because generally people avoid it and when they don't, they usually use it in a completely wrong way. I saw a Singleton pattern which made me carve my eyes out. And that came from a guy, who was a Senior Developer. And most of the times being a developer is about working with legacy code and trying to fix loads of problems, which wont be fixed in the end because there is not enough time, money and energy and so on and so on and... This makes loads of experienced people move in to management, or creating their own business, because they had enough of the trench work. That's why you won't see talented people on the market. Because they know... Oh and no, I'm not from that school. But having tests doesn't mean the tests are any good. You can have loads of methodologies, patterns, principles. If you can't tell when to use a Factory Pattern, or how to implement SOLID, then it doesn't matter how much you like, or want them.
- br3w5 10y ago
  Ok I retract my tests comment! Design patterns can definitely be abused and pragmatism is important when deciding whether or not to use them. I would say though that implementing SOLID is certainly achievable if writing from scratch but harder when refactoring code that breaks those principles (usually badly with no tests or poor tests).