Mine is a dockerized Pharo that I deploy it as a microservice in Elasticbeanstalk (so it scales up/down and autoheals nicely). It's 2 smalltalk backends, plus one microservice which depends in one javascript microservice for one feature. The only reason for that nodejs microservice was firebase-auth. The NPM package was already available there so it made sense to just use that one. The rest is all good from Pharo.
And the frontend begun with react but I've switched to Svelte. I'm enjoying Svelte's clean concepts a lot!
Our application is written using C# and the database uses T-SQL. That being said, I probably spend 80% of all my dev time in SSMS rather than Visual Studio. Despite there being far more functionality implemented in C#.
Similar here, I always wonder how much I should be worried about the imbalance of time spent in the database rather than code. For me it always seems like that much time in the database suggests something is missing from the primary UI/App, however can be hard to identify what can be feasibly add into the app giving the same speed and flexibility as SSMS
Since you spend a lot of your time in SSMS, I would encourage you to take a look at SqlDbx. It's a really helpful tool and boosts productivity in very noticeable ways. I'm in no way affiliated with them. Just a happy user.
C# (.Net Core) MVC w/web languages (JS/TypeScript/etc).
The other replies, at the time of posting, don't match my experience with the local job market/postings.
Web development outpaces other jobs by a significant margin, then mobile app development, and finally everything else. But most replies are niche academic or desktop development languages. It feels like self-selection bias, wherein people with "boring" jobs skip posting and people doing interesting/unusual things want to post.
The fact that Java has zero replies so far, speaks to something unusual going on.
As Someone1234 said, web development is the largest area in software. I'm in embedded systems, though, which is a very different world from web programming, and C++ (or just C) is the king in that area.
44 comments
[ 3.8 ms ] story [ 92.0 ms ] threadAnd a personal project too.
Mine is a dockerized Pharo that I deploy it as a microservice in Elasticbeanstalk (so it scales up/down and autoheals nicely). It's 2 smalltalk backends, plus one microservice which depends in one javascript microservice for one feature. The only reason for that nodejs microservice was firebase-auth. The NPM package was already available there so it made sense to just use that one. The rest is all good from Pharo.
And the frontend begun with react but I've switched to Svelte. I'm enjoying Svelte's clean concepts a lot!
http://sqldbx.com/
Not a dev but working closely with devs in the company so I feel a bit more dev than what I saw before.
Especially when it comes to rubber duck debugging
For my side-project? Groovy mainly, and some Java for backend / service development. Javascript for front-end development.
Luckily the skills translate well to Python/JavaScript, which is where I’m heading once I’m out of academia.
There's nothing wrong with being good at R. I work with data every day, and R is a godsend.
Looking into bringing Nim into the fold when the need arises.
Python 3.7+ is very nice to work with.
[0] https://github.com/john-bokma/tumblelog
The other replies, at the time of posting, don't match my experience with the local job market/postings.
Web development outpaces other jobs by a significant margin, then mobile app development, and finally everything else. But most replies are niche academic or desktop development languages. It feels like self-selection bias, wherein people with "boring" jobs skip posting and people doing interesting/unusual things want to post.
The fact that Java has zero replies so far, speaks to something unusual going on.
As Someone1234 said, web development is the largest area in software. I'm in embedded systems, though, which is a very different world from web programming, and C++ (or just C) is the king in that area.
I'm the engineering lead, so I could force the issue, but it's better to let people keep using the tools they're comfortable with.
Feels productive thanks to his no BS attitude (which can be sometimes limiting though).