3 ms·

Must be difficult to work in a company that can't reallocate resources.

by smeagull 3y ago

ilyt 3y ago
You can't just tell guy that moves boxes in CSS for a living to start writing database code
- orra 3y ago
  You say that, but plenty of job adverts are for fullstack developers, e.g. backend experience in C# with dapper or EF, and frontend in Angular or React. It's not an absurd transition for an experienced developer, even if there is a learning curve.
  - sgarland 3y ago
    As a DBRE, I assure you there is a world of difference between Fullstack Dev, and people who actually understand databases. Especially RDBMS.
    - _ea1k 3y ago
      As someone who works with database engineers, there's also a world of difference between the ones that know what they are doing and the ones that don't. To be fair, this is true in all fields.
      - orra 3y ago
        Precisely.
- mrguyorama 3y ago
  I was internally retasked from python to java full stack development. I have a bachelors in computer science, it's expected that I can just pick up, with a little time, any tool that fits the task. 95% of software development is just connecting pipes together. We are glorified digital plumbers for the most part, with only a few people working as the equivalent of civil engineers actually doing important design work. If you chose to save a few bucks by hiring limited devs, that's a choice you made. In our orgs, the guy who moves CSS boxes for a living absolutely can write some SQL queries. Most places don't write database code, they write code that uses an ORM or other framework to interact with existing databases.
pdpi 3y ago
Some companies can't for cultural reasons. Sometimes, it's really just that you got your strategy wrong and now you have a bunch of domain/technical experts who specialise in stuff that's altogether useless for your new direction.
- pwb25 3y ago
  at the same time many of those big tech companies never interview for domain or stack knowledge. both can not be true
steveBK123 3y ago
Taking an extreme, stupid, recent example - Let's say the ad market has slowed down and you really don't need so many ad salesmen. And you decide to switch gears to a subscription model so you need to do some work in payments. But you have a hiring freeze. Do you think the ad sales guys can help with the Square integration? Or let's say you've decided to bet your social graph / web / mobile app centric company on VR. How many of those existing devs are going to be useful in VR if you have a hiring freeze? Or when you realize it's a debacle and scale down VR, how many VR devs are going to be good iOS app update churners? Etc.
eecc 3y ago
heh, indeed... I'm a contractor and I got shuffled around into a team that's not really picking the steam it was expected to. Talked to the previous EM -- whose teams are under significant load -- and yeah, what a pity: budgets are locked so shrugs.
- steveBK123 3y ago
  Right, to me this is the challenge of "freezes". You lock in the an existing state of the world, regardless of how that begins to vary from reality. Wrong team sizes, wrong skillset matches, etc. EMs become greedy and hoard whoever they have regardless of the quantity need or size fit.

Must be difficult to work in a company that can't reallocate resources.

ilyt 3y ago

You can't just tell guy that moves boxes in CSS for a living to start writing database code

orra 3y ago
You say that, but plenty of job adverts are for fullstack developers, e.g. backend experience in C# with dapper or EF, and frontend in Angular or React. It's not an absurd transition for an experienced developer, even if there is a learning curve.
- sgarland 3y ago
  As a DBRE, I assure you there is a world of difference between Fullstack Dev, and people who actually understand databases. Especially RDBMS.
  - _ea1k 3y ago
    As someone who works with database engineers, there's also a world of difference between the ones that know what they are doing and the ones that don't. To be fair, this is true in all fields.
    - orra 3y ago
      Precisely.
mrguyorama 3y ago
I was internally retasked from python to java full stack development. I have a bachelors in computer science, it's expected that I can just pick up, with a little time, any tool that fits the task. 95% of software development is just connecting pipes together. We are glorified digital plumbers for the most part, with only a few people working as the equivalent of civil engineers actually doing important design work. If you chose to save a few bucks by hiring limited devs, that's a choice you made. In our orgs, the guy who moves CSS boxes for a living absolutely can write some SQL queries. Most places don't write database code, they write code that uses an ORM or other framework to interact with existing databases.

pdpi 3y ago

Some companies can't for cultural reasons. Sometimes, it's really just that you got your strategy wrong and now you have a bunch of domain/technical experts who specialise in stuff that's altogether useless for your new direction.

pwb25 3y ago
at the same time many of those big tech companies never interview for domain or stack knowledge. both can not be true

steveBK123 3y ago

Taking an extreme, stupid, recent example - Let's say the ad market has slowed down and you really don't need so many ad salesmen. And you decide to switch gears to a subscription model so you need to do some work in payments. But you have a hiring freeze. Do you think the ad sales guys can help with the Square integration? Or let's say you've decided to bet your social graph / web / mobile app centric company on VR. How many of those existing devs are going to be useful in VR if you have a hiring freeze? Or when you realize it's a debacle and scale down VR, how many VR devs are going to be good iOS app update churners? Etc.

eecc 3y ago

heh, indeed... I'm a contractor and I got shuffled around into a team that's not really picking the steam it was expected to. Talked to the previous EM -- whose teams are under significant load -- and yeah, what a pity: budgets are locked so shrugs.

steveBK123 3y ago
Right, to me this is the challenge of "freezes". You lock in the an existing state of the world, regardless of how that begins to vary from reality. Wrong team sizes, wrong skillset matches, etc. EMs become greedy and hoard whoever they have regardless of the quantity need or size fit.