aeonflux

> And then people still think their developer jobs are safe.

From my experience, most developers are actually very anxious and scared about their future.

> I'm not a team player or something. It's ridiculous.

This. In the past, when you could challenge a sloppy and rushed feature, done wrongly. You could steer people into better designs without adding much overhead. These days, if you try to challenge those no-reviews, ship-50k PRs daily, you instantly get labeled as AI-sceptic, someone who is afraid of change, afraid of loosing your job. I don't see a way out from this.

> Hobby groups projects like this are less fun for a lot of people who used to enjoy interacting with smart people.

Same thing did happen to many work places. People at all levels proxy questions through LLMs and don't even bother to read/trim/edit the response.

Funny, how suddenly a tight, 1-2 sentence response on point is a sign of skill.

> At this point "developers" these days sound a lot more like consumers than those who actually do research on a tool that solves a problem.

No need for snarky comments. These days tools/frameworks/languages/libraries/etc are popping all the time. Do you expect people to research every simple signal they catch in the wild?

Does this project have any meaningful traction? Seemed like a cool idea, but I wasn't even sure what problem does it solves. Looks like its completely missing from the regular discussion / news outlets. Every 1-2 years some barely visible post/article reminds me it even exists...

I don't really understand where is this need to compress the logic into where small chunks comes from. In result we get single line of code which has multiple statement conditions, different paths, and it's not possible to grasp in one go.

Other practical example why ternary is bad: Many code-coverage solutions break on ternary because they don't correctly see that one of the branches was missed in tests.

Those two behave in the same way if you drop the parentheses:

1. statement if (condition || something)

2. (statement if condition) or something

I don't think rewrite the in Scala was great decision, business wise. Fast forward 15 years its way lower on popularity than Ruby. Not sure what they use these days though.

"There are only two kinds of languages: the ones people complain about and the ones nobody uses." -- Bjarne Stroustrup, The C++ Programming Language

Results from outsourcing can vary. You might end-up with totally unmatched 5 candidates and complain that there is no good people on the market. How would asses that the agency did good job (or any job at all)?

Types are helpful in large codebases, but in Web Apps they tend to get into the way more than they help. You can still use semi-typed constructs in Ruby, but you have the freedom to choose where you need them.

After moving to writing web in Go (from Ruby) I am still baffled how much more boiler plate there is and how much slower things move because of this. Types are great when you want to refactor some things, but thats just part of the job.

In Ruby I loved how can you just quickly jump into REPL or just do inline breakpoint to inspect state: `scope.map(&:names).last.tally.sort_by(&:last).reverse.first(10)`

Something like this is such a chore in Go that I simply skip it more often than not.

> it uses a lot of special characters, which makes writing the code slower

I don't get this part. What special characters?

Hey man, you should really put some effort into formatting the code samples, as they are awful to read.

Could you point out where do you get your data from? Anything to back-up your claims that Rails is in decline and Elixir/Phoenix is growing? For a time not long ago I was heavily into looking for an Elixir gig, but couldn't really find offers, while there were still tons of offers for Rails development.

List is available after paying. Which makes a lot of sense.