Hacker News Reader

yitznewtonon Ask HN: Who is hiring? (October 2020)

SevenFifty | Technical Lead (Rails/React) | Remote USA | Full-time

SevenFifty is an end-to-end supply chain and communications platform (B2B SaaS) connecting U.S. alcohol retailers, wholesalers, and producers/importers.

We're looking for an experienced full-stack developer to join our 15-person engineering team and lead development for a small squad. The squad you’ll be joining is currently two other engineers and a project manager working with stakeholders across the business, and a cross-team designer as needed. They work in two related Rails apps, with a combination of classic server-rendered Rails functionality, and React components on top of Rails. We use Solr for search, Postgres on Amazon RDS for data, and run our web apps on Heroku.

This role entails a mix of hands-on development and technical leadership. You'll be the technical representative for your squad of engineers, taking the lead on architectural decisions and quality development practices across the team. We expect you to be team-oriented and be comfortable mentoring, but we do not expect you to directly manage other engineers.

yitz at sevenfifty dot com (hiring manager)

More info and link to apply at: https://www.builtinnyc.com/job/engineer/technical-lead-web-d...

yitznewtonon Learn Languages, not Frameworks

Small units of code are good. The smaller it is, the easier it is to understand. It’s harder to screw it up — and I screw stuff up a lot, so limiting that is really important. So, I strive to build small modules of code with a single purpose, or at most a few closely-related purposes. They should be self-contained pieces that solve individual problems. These pieces then work together to solve larger, more complex problems.

To me the article's perspective misses the point. The language itself is just a vehicle for encapsulating data and logic, etc. for some purpose. A framework adds levels of tools and abstractions to "take care" of common situations. The small units can be modules that one employs within a framework, such as an authentication mechanism within a web app. I feel just the opposite of the author: the language is only as useful as the tools available to take superfluous overhead of shared tasks off my hands. The excessive fragmentation of the PHP framework scene is the main reason driving me toward Rails, and thus Ruby. I don't have any practical arguments against PHP and for Ruby, but I'm dismayed that I can't find a current midstream PHP framework like symfony1 was, with great community support, that's easy enough to adapt to a wide variety of projects. Looking into the Rails community (I still haven't rolled a project), I feel like Rails accomplishes that.