He must be talking about the good, benevolent Western corporations that have outsourced their carbon emissions to the evil and greedy Chinese and Indian corporations.
This risks hiring candidates who can present themselves and their past projects very well but fail to actually write code and ship anything on the job. I've seen it happen.
Substack | San Francisco, New York City, remote (US & Canada only) | full time
We're beginning to build writer capabilities into Substack's Android & iOS apps.
Today, writers, podcasters, and video creators use Substack on mobile web to write drafts and manage their publication. Despite the difficulties and shortcomings of working in a mobile browser, they're already asking to do more: to record podcasts (and video podcasts), to share their work, and to easily understand their business and audience.
They deserve a world-class native app experience and we're looking for the right engineer to help us make this happen. We're a fully remote team with an extremely exciting mission: we're making the Internet work for writers. Come join us.
Substack | San Francisco, CA; New York, NY, and remote in the US and Canada
Help build a better future for writing. We believe that what you read matters and writing is valuable. We’re here to help writers go independent and thrive, and we’re hiring.
We're hiring software engineers for web (JavaScript + TypeScript, Node,
React), iOS (Objective-C, Swift), and Android (Kotlin), and data analysts, security & systems engineers, designers, and product managers.
Here's how we think about engineering:
- We bias to action. We work fast, make bold bets, and then course-correct as needed.
- We believe great things are built by small groups of exceptional people. We assemble tight-knit teams and give them clear, ambitious goals and the autonomy they need to succeed.
- Remote Collaboration and Community. The team has a home base in San Francisco, but there’s also an office in New York and some people are remote. We get together a few times a year to build relationships and work and celebrate together. Engineers are autonomous and independent and balance that with highly collaborative pairing sessions, problem solving, and more. It’s a team that celebrates one another.
- Empathy for writers. We do Empathy Hour, Office Hours, shadowing customer support, and find ways to get writers and engineers talking with one another. Substack started by building a product for a specific writer (Bill Bishop writing Sinocism) and we’ve strived to maintain that ethos as we’ve scaled – focused directly on the needs of people.
- Feelings Friday. We’re here to support each other through the ups and downs of a high growth startup.
- Diversity of perspectives. We are engineers with a diverse set of professional and personal backgrounds, and as a result have a working environment that demonstrates a wide variety of skills and knowledge.
- We like to have fun. We have a quarterly hackathon where engineers collaborate to build things they want to see on the platform. Many of the things people build get shipped. (~50% of things from our last hackathon have shipped or will soon)
We’re looking for a founding member for a full-stack engineering team in Toronto. Initially, this will be a remote role — work from anywhere you like, with occasional meet-ups with our small (but growing!) Canadian team.
We’re looking for someone with considerable experience building out scalable UI architectures and who is comfortable working on a wide variety of projects, including mobile apps, internal tools, e-commerce sites, and other customer- and partner-facing portals.
We're a two-person software consultancy helping start-ups in San Francisco and Silicon Valley get things done. We're looking for a senior full-stack software engineer, someone who is professional, takes pride in their work, and is comfortable working remotely and dealing directly with clients. Depending on the needs of our clients, we take on end-to-end projects or integrate with existing development teams.
Over the past two years, we’ve worked with a wide variety of clients, which means a wide variety of tech, and we pride ourselves on being able to adapt and deliver. While we are looking for a seasoned engineer, we don’t require you to have experience using a particular language or framework; the ability to pick things up as you go is what’s essential. That said, we're currently doing a lot of work in Node, React, and Shopify so bonus consideration will be given if you have experience with these.
We work remotely from our home offices and you would, too. You’ll interact directly with clients and have the freedom to set your own schedule and complete your projects however you work best.
Get in touch if you’d like to be the third member of a small, professional team.
Earlier Labs is a two-person software consultancy helping start-ups in San Francisco and Silicon Valley get things done. Depending on the needs of our clients, we take on end-to-end projects or integrate with existing development teams.
Over the past two years, we’ve worked with a wide variety of clients, which means a wide variety of tech, and we pride ourselves on being able to adapt and deliver. Today, we're working with Ruby on Rails and React.js; tomorrow, we could be working with something entirely different. While we are looking for a seasoned engineer, we don’t require you to have experience using a particular language or framework; the ability to pick things up as you go is what’s essential.
We work remotely from our home offices, and you would, too. You’ll interact directly with clients and have the freedom to set your own schedule and complete your projects however you work best.
Yes, but the same attack could happen if an attacker gains control of an npm module. Users without tight control over their modules could unwittingly pull in malicious code.
This approach is fine for small projects but you'll run into organizational problems once your application's complexity grows. For example, how many event listeners are you going to pile into that $(document).ready callback before you decide to break things up? How do you organize your code if/when you separate your listeners.
Another aspect your code doesn't address is fetching/posting data from/to the server, which leads to many more tangles, especially once you start duplicating code between models, etc.
Anyway, this isn't a criticism by any means. If such a lightweight approach is working well then you're doing it right. I'm just pointing out that things can get hairy as your app needs to do more and more.