Software Engineer

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Do you pay more than 100k for a senior developer (>5yrs exp)?

Yes.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Culture has changed though. Work has devolved into an "assembly line" type of situation where you are timed and constantly pressured to develop things as fast as possible at the expense of creativity and quality. This has even penetrated consulting which used to be expertise driven field. Agile and "sprinting" took all the joy out of being able to engineer interesting solutions and have time to solve problems instead of patching things up. And this has become tough for older people to keep up too. Many younger developers are on a fast moving treadmill and take ADHD drugs and anxiety meds.

This notion of Agile “taking the joy” out of software development is entirely a reflection of people who know nothing about Agile claiming to apply it.

Robert Martin is great on this —- Agile is a tool for teams of 8-10 software developers to write software. Non technical people don’t and can’t meaningfully understand it and shouldn’t be allowed working 50 miles of a software development project as so called “scrum masters.”

Agile is a way for self-organizing teams of software developers to manage their work. Automated testing, pair programming, and protection from clueless non-technical middle managers tearing for control are essential components. For example, story points are not a metric to be used by manager la to try to squeeze more productivity out of developers. They are a tool for ongoing learning by the team, period. Managers’ job is to manage scope. Period.

When practiced this way, Agile leads to craftsmanship, quality, clean code, clean architecture, and always deployable code. Unfortunately, all of the non-technical IT bureaucrats with PMPs who feel threatened by tech people make it’s their life’s work to coop Agile into a tool for managers, and thus guarantee awful code and continual failure.

This is why the foreign workers are better, never had one argue with me about methodology.

PP you’re responding to. Not sure what this means. On the teams I lead, we have a mix of US and foreign born developers, and we talk methodology all the time. Then again, we all have CS degrees, aren’t as wildly ignorant as most of the posters on this thread, and don’t hire non-technical people to manage software.

Yeah, we're pretty much the exact opposite, just getting things done instead of worrying about roles and ceremonies and burning through budgets while under producing.

Bless your heart. As people who actually know software development know, in the long term, you ensure productivity with automated testing, pair programming, and clean code. Agile is critical to that mix.

What ALWAYS happens to people who "just get things done" is that they end up with unmaintainable code that consumes steadily more cycles just on O&M and that everyone is terrified to refactor because they have no idea what they will break.

I love those companies though, because they make great customers when we are brought in to replace the old mess and (try to) train the dinosaurs that created the mess. By all means, keep "just getting things done" -- I could use a bonus!

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Culture has changed though. Work has devolved into an "assembly line" type of situation where you are timed and constantly pressured to develop things as fast as possible at the expense of creativity and quality. This has even penetrated consulting which used to be expertise driven field. Agile and "sprinting" took all the joy out of being able to engineer interesting solutions and have time to solve problems instead of patching things up. And this has become tough for older people to keep up too. Many younger developers are on a fast moving treadmill and take ADHD drugs and anxiety meds.

This notion of Agile “taking the joy” out of software development is entirely a reflection of people who know nothing about Agile claiming to apply it.

Robert Martin is great on this —- Agile is a tool for teams of 8-10 software developers to write software. Non technical people don’t and can’t meaningfully understand it and shouldn’t be allowed working 50 miles of a software development project as so called “scrum masters.”

Agile is a way for self-organizing teams of software developers to manage their work. Automated testing, pair programming, and protection from clueless non-technical middle managers tearing for control are essential components. For example, story points are not a metric to be used by manager la to try to squeeze more productivity out of developers. They are a tool for ongoing learning by the team, period. Managers’ job is to manage scope. Period.

When practiced this way, Agile leads to craftsmanship, quality, clean code, clean architecture, and always deployable code. Unfortunately, all of the non-technical IT bureaucrats with PMPs who feel threatened by tech people make it’s their life’s work to coop Agile into a tool for managers, and thus guarantee awful code and continual failure.

This is why the foreign workers are better, never had one argue with me about methodology.

PP you’re responding to. Not sure what this means. On the teams I lead, we have a mix of US and foreign born developers, and we talk methodology all the time. Then again, we all have CS degrees, aren’t as wildly ignorant as most of the posters on this thread, and don’t hire non-technical people to manage software.

Yeah, we're pretty much the exact opposite, just getting things done instead of worrying about roles and ceremonies and burning through budgets while under producing.

Bless your heart. As people who actually know software development know, in the long term, you ensure productivity with automated testing, pair programming, and clean code. Agile is critical to that mix.

What ALWAYS happens to people who "just get things done" is that they end up with unmaintainable code that consumes steadily more cycles just on O&M and that everyone is terrified to refactor because they have no idea what they will break.

I love those companies though, because they make great customers when we are brought in to replace the old mess and (try to) train the dinosaurs that created the mess. By all means, keep "just getting things done" -- I could use a bonus!

What employers use pair programming?

Agile is wholly separable from testing and code quality.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Culture has changed though. Work has devolved into an "assembly line" type of situation where you are timed and constantly pressured to develop things as fast as possible at the expense of creativity and quality. This has even penetrated consulting which used to be expertise driven field. Agile and "sprinting" took all the joy out of being able to engineer interesting solutions and have time to solve problems instead of patching things up. And this has become tough for older people to keep up too. Many younger developers are on a fast moving treadmill and take ADHD drugs and anxiety meds.

This notion of Agile “taking the joy” out of software development is entirely a reflection of people who know nothing about Agile claiming to apply it.

Robert Martin is great on this —- Agile is a tool for teams of 8-10 software developers to write software. Non technical people don’t and can’t meaningfully understand it and shouldn’t be allowed working 50 miles of a software development project as so called “scrum masters.”

Agile is a way for self-organizing teams of software developers to manage their work. Automated testing, pair programming, and protection from clueless non-technical middle managers tearing for control are essential components. For example, story points are not a metric to be used by manager la to try to squeeze more productivity out of developers. They are a tool for ongoing learning by the team, period. Managers’ job is to manage scope. Period.

When practiced this way, Agile leads to craftsmanship, quality, clean code, clean architecture, and always deployable code. Unfortunately, all of the non-technical IT bureaucrats with PMPs who feel threatened by tech people make it’s their life’s work to coop Agile into a tool for managers, and thus guarantee awful code and continual failure.

This is why the foreign workers are better, never had one argue with me about methodology.

PP you’re responding to. Not sure what this means. On the teams I lead, we have a mix of US and foreign born developers, and we talk methodology all the time. Then again, we all have CS degrees, aren’t as wildly ignorant as most of the posters on this thread, and don’t hire non-technical people to manage software.

Yeah, we're pretty much the exact opposite, just getting things done instead of worrying about roles and ceremonies and burning through budgets while under producing.

Bless your heart. As people who actually know software development know, in the long term, you ensure productivity with automated testing, pair programming, and clean code. Agile is critical to that mix.

What ALWAYS happens to people who "just get things done" is that they end up with unmaintainable code that consumes steadily more cycles just on O&M and that everyone is terrified to refactor because they have no idea what they will break.

I love those companies though, because they make great customers when we are brought in to replace the old mess and (try to) train the dinosaurs that created the mess. By all means, keep "just getting things done" -- I could use a bonus!

What employers use pair programming?

Agile is wholly separable from testing and code quality.

Oh dear. No, it's not separate. Not at all. Repeat after me: Agile is a tool for software development teams to deliver better quality code, it's not and never has been a management tool or any of the other nonsense that people in the Agile Industry(TM) try to sell it as.


There is no Agile without automated testing and pair programming. And to answer your question, every place I've worked has done some pair programming, and the better the code quality, the more, up to about 30% of developer time.

[Anonymous]

Check out this discussion of what Agile is by one of the people who was most responsible for creating the movement.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Culture has changed though. Work has devolved into an "assembly line" type of situation where you are timed and constantly pressured to develop things as fast as possible at the expense of creativity and quality. This has even penetrated consulting which used to be expertise driven field. Agile and "sprinting" took all the joy out of being able to engineer interesting solutions and have time to solve problems instead of patching things up. And this has become tough for older people to keep up too. Many younger developers are on a fast moving treadmill and take ADHD drugs and anxiety meds.

This notion of Agile “taking the joy” out of software development is entirely a reflection of people who know nothing about Agile claiming to apply it.

Robert Martin is great on this —- Agile is a tool for teams of 8-10 software developers to write software. Non technical people don’t and can’t meaningfully understand it and shouldn’t be allowed working 50 miles of a software development project as so called “scrum masters.”

Agile is a way for self-organizing teams of software developers to manage their work. Automated testing, pair programming, and protection from clueless non-technical middle managers tearing for control are essential components. For example, story points are not a metric to be used by manager la to try to squeeze more productivity out of developers. They are a tool for ongoing learning by the team, period. Managers’ job is to manage scope. Period.

When practiced this way, Agile leads to craftsmanship, quality, clean code, clean architecture, and always deployable code. Unfortunately, all of the non-technical IT bureaucrats with PMPs who feel threatened by tech people make it’s their life’s work to coop Agile into a tool for managers, and thus guarantee awful code and continual failure.

This is why the foreign workers are better, never had one argue with me about methodology.

PP you’re responding to. Not sure what this means. On the teams I lead, we have a mix of US and foreign born developers, and we talk methodology all the time. Then again, we all have CS degrees, aren’t as wildly ignorant as most of the posters on this thread, and don’t hire non-technical people to manage software.

Yeah, we're pretty much the exact opposite, just getting things done instead of worrying about roles and ceremonies and burning through budgets while under producing.

Bless your heart. As people who actually know software development know, in the long term, you ensure productivity with automated testing, pair programming, and clean code. Agile is critical to that mix.

What ALWAYS happens to people who "just get things done" is that they end up with unmaintainable code that consumes steadily more cycles just on O&M and that everyone is terrified to refactor because they have no idea what they will break.

I love those companies though, because they make great customers when we are brought in to replace the old mess and (try to) train the dinosaurs that created the mess. By all means, keep "just getting things done" -- I could use a bonus!

What employers use pair programming?

Agile is wholly separable from testing and code quality.

Who has resources for paired programming? We're too busy squeezing water from rocks.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Do you pay more than 100k for a senior developer (>5yrs exp)?

Yes.

Don't you have your pick of Hlb Visa holders to choose from?

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Do you pay more than 100k for a senior developer (>5yrs exp)?

Yes.

In my world, 5 years experience only moves someone from an entry-level position to a standard Software Engineer; in my world, a senior software engineer has 15-20 years experience. Maybe other places have more title inflation ?

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Culture has changed though. Work has devolved into an "assembly line" type of situation where you are timed and constantly pressured to develop things as fast as possible at the expense of creativity and quality. This has even penetrated consulting which used to be expertise driven field. Agile and "sprinting" took all the joy out of being able to engineer interesting solutions and have time to solve problems instead of patching things up. And this has become tough for older people to keep up too. Many younger developers are on a fast moving treadmill and take ADHD drugs and anxiety meds.

This notion of Agile “taking the joy” out of software development is entirely a reflection of people who know nothing about Agile claiming to apply it.

Robert Martin is great on this —- Agile is a tool for teams of 8-10 software developers to write software. Non technical people don’t and can’t meaningfully understand it and shouldn’t be allowed working 50 miles of a software development project as so called “scrum masters.”

Agile is a way for self-organizing teams of software developers to manage their work. Automated testing, pair programming, and protection from clueless non-technical middle managers tearing for control are essential components. For example, story points are not a metric to be used by manager la to try to squeeze more productivity out of developers. They are a tool for ongoing learning by the team, period. Managers’ job is to manage scope. Period.

When practiced this way, Agile leads to craftsmanship, quality, clean code, clean architecture, and always deployable code. Unfortunately, all of the non-technical IT bureaucrats with PMPs who feel threatened by tech people make it’s their life’s work to coop Agile into a tool for managers, and thus guarantee awful code and continual failure.

This is why the foreign workers are better, never had one argue with me about methodology.

PP you’re responding to. Not sure what this means. On the teams I lead, we have a mix of US and foreign born developers, and we talk methodology all the time. Then again, we all have CS degrees, aren’t as wildly ignorant as most of the posters on this thread, and don’t hire non-technical people to manage software.

Yeah, we're pretty much the exact opposite, just getting things done instead of worrying about roles and ceremonies and burning through budgets while under producing.

Bless your heart. As people who actually know software development know, in the long term, you ensure productivity with automated testing, pair programming, and clean code. Agile is critical to that mix.

What ALWAYS happens to people who "just get things done" is that they end up with unmaintainable code that consumes steadily more cycles just on O&M and that everyone is terrified to refactor because they have no idea what they will break.

I love those companies though, because they make great customers when we are brought in to replace the old mess and (try to) train the dinosaurs that created the mess. By all means, keep "just getting things done" -- I could use a bonus!

What employers use pair programming?

Agile is wholly separable from testing and code quality.

Who has resources for paired programming? We're too busy squeezing water from rocks.

People and organizations that haven’t ever done software development right (including pair programming, automated testing, and Agile) think that doing things that way takes more time. In fact, over time it’s MUCH quicker because you avoid the steadily growing mountain of tech debt that projects done the other way have. There’s a dynamic in those projects where the effort to make change goes up exponentially - from tiny at first (“no tests to write, no coordination with others! Woo hoo”) to slowly more (“WFT is Joe’s code doing?”) to a locked up mess that everyone is afraid to touch.

Doing things right actually takes less effort in the long run.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Do you pay more than 100k for a senior developer (>5yrs exp)?

Yes.

In my world, 5 years experience only moves someone from an entry-level position to a standard Software Engineer; in my world, a senior software engineer has 15-20 years experience. Maybe other places have more title inflation ?

I’m the “Yes” poster.

I was going to say the same thing. 5 years is not close to senior. Also, someone with a degree and 5 years makes more than $100k. Both are true.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Culture has changed though. Work has devolved into an "assembly line" type of situation where you are timed and constantly pressured to develop things as fast as possible at the expense of creativity and quality. This has even penetrated consulting which used to be expertise driven field. Agile and "sprinting" took all the joy out of being able to engineer interesting solutions and have time to solve problems instead of patching things up. And this has become tough for older people to keep up too. Many younger developers are on a fast moving treadmill and take ADHD drugs and anxiety meds.

This notion of Agile “taking the joy” out of software development is entirely a reflection of people who know nothing about Agile claiming to apply it.

Robert Martin is great on this —- Agile is a tool for teams of 8-10 software developers to write software. Non technical people don’t and can’t meaningfully understand it and shouldn’t be allowed working 50 miles of a software development project as so called “scrum masters.”

Agile is a way for self-organizing teams of software developers to manage their work. Automated testing, pair programming, and protection from clueless non-technical middle managers tearing for control are essential components. For example, story points are not a metric to be used by manager la to try to squeeze more productivity out of developers. They are a tool for ongoing learning by the team, period. Managers’ job is to manage scope. Period.

When practiced this way, Agile leads to craftsmanship, quality, clean code, clean architecture, and always deployable code. Unfortunately, all of the non-technical IT bureaucrats with PMPs who feel threatened by tech people make it’s their life’s work to coop Agile into a tool for managers, and thus guarantee awful code and continual failure.

This is why the foreign workers are better, never had one argue with me about methodology.

PP you’re responding to. Not sure what this means. On the teams I lead, we have a mix of US and foreign born developers, and we talk methodology all the time. Then again, we all have CS degrees, aren’t as wildly ignorant as most of the posters on this thread, and don’t hire non-technical people to manage software.

Yeah, we're pretty much the exact opposite, just getting things done instead of worrying about roles and ceremonies and burning through budgets while under producing.

Bless your heart. As people who actually know software development know, in the long term, you ensure productivity with automated testing, pair programming, and clean code. Agile is critical to that mix.

What ALWAYS happens to people who "just get things done" is that they end up with unmaintainable code that consumes steadily more cycles just on O&M and that everyone is terrified to refactor because they have no idea what they will break.

I love those companies though, because they make great customers when we are brought in to replace the old mess and (try to) train the dinosaurs that created the mess. By all means, keep "just getting things done" -- I could use a bonus!

What employers use pair programming?

Agile is wholly separable from testing and code quality.

Who has resources for paired programming? We're too busy squeezing water from rocks.

People and organizations that haven’t ever done software development right (including pair programming, automated testing, and Agile) think that doing things that way takes more time. In fact, over time it’s MUCH quicker because you avoid the steadily growing mountain of tech debt that projects done the other way have. There’s a dynamic in those projects where the effort to make change goes up exponentially - from tiny at first (“no tests to write, no coordination with others! Woo hoo”) to slowly more (“WFT is Joe’s code doing?”) to a locked up mess that everyone is afraid to touch.

Doing things right actually takes less effort in the long run.

Quite a lot of software was involved and getting your comments from your fingers to my eyes, including your computer, or phone, mine, the forum software, the networking systems in between, and ancillary features like the advertisements.

What fraction that do you suppose was built using a techniques you espouse?

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Do you pay more than 100k for a senior developer (>5yrs exp)?

Yes.

Don't you have your pick of Hlb Visa holders to choose from?

+1

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Culture has changed though. Work has devolved into an "assembly line" type of situation where you are timed and constantly pressured to develop things as fast as possible at the expense of creativity and quality. This has even penetrated consulting which used to be expertise driven field. Agile and "sprinting" took all the joy out of being able to engineer interesting solutions and have time to solve problems instead of patching things up. And this has become tough for older people to keep up too. Many younger developers are on a fast moving treadmill and take ADHD drugs and anxiety meds.

This notion of Agile “taking the joy” out of software development is entirely a reflection of people who know nothing about Agile claiming to apply it.

Robert Martin is great on this —- Agile is a tool for teams of 8-10 software developers to write software. Non technical people don’t and can’t meaningfully understand it and shouldn’t be allowed working 50 miles of a software development project as so called “scrum masters.”

Agile is a way for self-organizing teams of software developers to manage their work. Automated testing, pair programming, and protection from clueless non-technical middle managers tearing for control are essential components. For example, story points are not a metric to be used by manager la to try to squeeze more productivity out of developers. They are a tool for ongoing learning by the team, period. Managers’ job is to manage scope. Period.

When practiced this way, Agile leads to craftsmanship, quality, clean code, clean architecture, and always deployable code. Unfortunately, all of the non-technical IT bureaucrats with PMPs who feel threatened by tech people make it’s their life’s work to coop Agile into a tool for managers, and thus guarantee awful code and continual failure.

This is why the foreign workers are better, never had one argue with me about methodology.

PP you’re responding to. Not sure what this means. On the teams I lead, we have a mix of US and foreign born developers, and we talk methodology all the time. Then again, we all have CS degrees, aren’t as wildly ignorant as most of the posters on this thread, and don’t hire non-technical people to manage software.

Yeah, we're pretty much the exact opposite, just getting things done instead of worrying about roles and ceremonies and burning through budgets while under producing.

Bless your heart. As people who actually know software development know, in the long term, you ensure productivity with automated testing, pair programming, and clean code. Agile is critical to that mix.

What ALWAYS happens to people who "just get things done" is that they end up with unmaintainable code that consumes steadily more cycles just on O&M and that everyone is terrified to refactor because they have no idea what they will break.

I love those companies though, because they make great customers when we are brought in to replace the old mess and (try to) train the dinosaurs that created the mess. By all means, keep "just getting things done" -- I could use a bonus!

What you say always happens hasn't happened yet, while we've watched big agile projects come and go. Ask an agile team to do something quickly and they'll add it to their backlog grooming sesssion to see if it can be included in a future spint. Should call it Rigid.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Be aware that we have over a million foreign workers temporarily in the US doing IT work.

Any it keeps growing. Anyone waiting for a green card can stay forever so the
Numbers grow and grow.

They are all desperate for a green card and with this huge supply they suppress wages and allow ageism to be rampant in IT field

It is not a career anymore but a 5 to 15
Year job path before you will be fired and replaced with an HXXXb

This person has no idea what they are talking about.

I’m a 56 year old US born development manager and was just hired for a new role. Also, I’m actively hiring developers and happy to talk with people of any age. The reality is that 95% of the applicants we get are not US born, and those that do apply are often wildly unqualified (e.g. can’t answer the question “what’s a relational database”).

Culture has changed though. Work has devolved into an "assembly line" type of situation where you are timed and constantly pressured to develop things as fast as possible at the expense of creativity and quality. This has even penetrated consulting which used to be expertise driven field. Agile and "sprinting" took all the joy out of being able to engineer interesting solutions and have time to solve problems instead of patching things up. And this has become tough for older people to keep up too. Many younger developers are on a fast moving treadmill and take ADHD drugs and anxiety meds.

This notion of Agile “taking the joy” out of software development is entirely a reflection of people who know nothing about Agile claiming to apply it.

Robert Martin is great on this —- Agile is a tool for teams of 8-10 software developers to write software. Non technical people don’t and can’t meaningfully understand it and shouldn’t be allowed working 50 miles of a software development project as so called “scrum masters.”

Agile is a way for self-organizing teams of software developers to manage their work. Automated testing, pair programming, and protection from clueless non-technical middle managers tearing for control are essential components. For example, story points are not a metric to be used by manager la to try to squeeze more productivity out of developers. They are a tool for ongoing learning by the team, period. Managers’ job is to manage scope. Period.

When practiced this way, Agile leads to craftsmanship, quality, clean code, clean architecture, and always deployable code. Unfortunately, all of the non-technical IT bureaucrats with PMPs who feel threatened by tech people make it’s their life’s work to coop Agile into a tool for managers, and thus guarantee awful code and continual failure.

This is why the foreign workers are better, never had one argue with me about methodology.

PP you’re responding to. Not sure what this means. On the teams I lead, we have a mix of US and foreign born developers, and we talk methodology all the time. Then again, we all have CS degrees, aren’t as wildly ignorant as most of the posters on this thread, and don’t hire non-technical people to manage software.

Yeah, we're pretty much the exact opposite, just getting things done instead of worrying about roles and ceremonies and burning through budgets while under producing.

Bless your heart. As people who actually know software development know, in the long term, you ensure productivity with automated testing, pair programming, and clean code. Agile is critical to that mix.

What ALWAYS happens to people who "just get things done" is that they end up with unmaintainable code that consumes steadily more cycles just on O&M and that everyone is terrified to refactor because they have no idea what they will break.

I love those companies though, because they make great customers when we are brought in to replace the old mess and (try to) train the dinosaurs that created the mess. By all means, keep "just getting things done" -- I could use a bonus!

What you say always happens hasn't happened yet, while we've watched big agile projects come and go. Ask an agile team to do something quickly and they'll add it to their backlog grooming sesssion to see if it can be included in a future spint. Should call it Rigid.

Serious question — you believe in “just getting things done.” Does that mean you don’t write automated tests? If so, how the heck do you automate DevOps? Push and hope for the best?

[Anonymous]

I believe in getting things done efficiently, but that doesn’t mean skipping automated tests. It’s about finding balance—testing what truly matters while keeping delivery fast and reliable. In my experience, automation is essential to sustainable DevOps. Without it, you’re just guessing outcomes instead of ensuring consistency. I’ve seen similar principles applied in projects like healthcare data integration https://www.abtosoftware.com/blog/healthcare-data-integration where automation directly improves reliability and performance.