| ▲ | Pooge 3 hours ago |
| I disagree. Engineers choose the technical stack based on the specs. With LLMs, it's faster to ship even in a more verbose language like Go or Rust. |
|
| ▲ | lionkor an hour ago | parent | next [-] |
| The language doesn't matter much if you have memory-hungry workloads. Whether it's Rust or C or C#, you can write quite memory efficient code in either. |
| |
|
| ▲ | laughing_man 2 hours ago | parent | prev | next [-] |
| The spec is the important part, though. If memory limitations are part of the spec, you're not going to choose a stack that will be too wasteful. |
| |
| ▲ | Pooge 2 hours ago | parent [-] | | Yes, but that doesn't determine the technical stack. It only narrows it down. You could just as well use C, C++, Rust or even Go depending on the device the program needs to run on. The device may have constraints as well but those are technical limitations and still not the responsibility of the product owner. |
|
|
| ▲ | armada651 2 hours ago | parent | prev | next [-] |
| Who determines the specs? |
| |
| ▲ | Pooge 2 hours ago | parent [-] | | Specs are business requirements. Choosing a programming language is not a business requirement; it's a technical one. | | |
| ▲ | swiftcoder 11 minutes ago | parent | next [-] | | > Choosing a programming language is not a business requirement; it's a technical one. Technical decisions like this have to take into account a lot of factors outside of just the language itself. Is the language you want to use easy to hire for? Will we have to pay a premium for engineers with a specialised background in the language? Do all our 3rd party dependencies maintain SDKs for the language? Do libraries that meet various certifications we might need (i.e. FIPS) exist for the language? Something like Typescript or Java is going to win out over Rust/Erlang/FP-of-your-choice on a number of these criteria. | |
| ▲ | shakna 2 hours ago | parent | prev | next [-] | | Platforms are often part of the business requirements. If you're working on SAP or Salesforce, the language decisions are already made for you. If you're integrating with an existing Electron runtime, then you'll be using something in the JS family, like it or not. | |
| ▲ | Someone 2 hours ago | parent | prev | next [-] | | > Choosing a programming language is not a business requirement; it's a technical one. Not solely. The business will have reasons to stay on a mainstream language, for example because - it offers better guarantees for hiring maintainers in the future - it has a higher likelihood that security issues will be fixed rapidly for free - LLMs are better at maintaining code written in it | |
| ▲ | jpollock 2 hours ago | parent | prev [-] | | The programming language can have definite business impacts. It can impact hiring, salary costs (if the skill is rare), ramp-up costs (if it needs to be taught), etc. Even bus-factor comes into it. | | |
| ▲ | Pooge an hour ago | parent [-] | | Software engineering is an important skill to recruit for. Too many times I see "Java Developer"... Like, do they only know Java and are absolutely incompetent when it comes to something else? I don't even want to recruit or be recruited with such a title. |
|
|
|
|
| ▲ | retired 2 hours ago | parent | prev [-] |
| I have never worked for a company where the engineers choose the technical stack. It’s always the architect, the CTO or the mother company that decides what technology to choose. Could be a German/Dutch cultural thing though. |
| |
| ▲ | Byamarro an hour ago | parent [-] | | Depends on a type of company, I work at a mid-sized startup and through lifecycle of this company there were times when we've had architects and there were times when we haven't. Rn we don't have and a lot of decisions is made within teams and we just try to keep communication about what's needed for business tight | | |
| ▲ | retired 38 minutes ago | parent [-] | | Understandable. I worked mainly for 100+ people companies and the tech stack impacts team interoperability, hiring, licenses, life cycle management etcetera. |
|
|
