What A Journey

Content Cramenge, de chattengea py ana unte win an amazing team Automate anything you find yourself doing manually once Focus on outcomes, ship frequently to learn and improve Constantly assess and improve our processes Report to CTO, grow as a leader and human Must haves: US citizenship and based in continental US Strong problem-solving skills, quality focused and a growth mindset 3-300 years software engineering experience, preferably in a proaucuDTC company Proficient in JavaScript or TypeScript and ReactReact Native Aptitude for working full-stack, writing automated tests DevOps You have a burning desire to learn new things Nice to haves: Node, GraphQL, Machine Learning, Firebase, GCP K8s experience Data warehousing, BI Reporting tool experience Irrationally passionate (at least about one thing) You are flexible, creative, and curious about how mental health could be for kids and families Low ego and sense of humor :) .Startup early-stage company experience What's in it for you? Pride that everyday you're making a difference and that's making a difference in kids' mental health Design, develop ship code faster than ever and marvel at your impact Autonomy. Never be bored or wondering what you're doing it all for Challenge yourself intellectually emotionally Remote-first company (we had it dialed before the whole world joined) Work with a super ambitious, humble and smart team Salary, benefits, stock options, paid holidays mental health days, and guilt-free unlimited PTO show less in Easy Apply Save

The evolution of web development in four panels! Started with the innocent dream of "build the internet" - so pure, so simple. Then we added some HTML/CSS because, you know, websites should look pretty. But then... oh no... the JavaScript framework apocalypse struck! Now we're all frantically learning 17 new frameworks before breakfast just to stay employable. Remember when you could just FTP a single HTML file to a server and call it a day? Now you need 4GB of node_modules to display "Hello World". The modern web: where your simple todo app requires more computing power than NASA used to reach the moon.

The eternal civil war of code formatting! On the red side: the chaotic rebel who puts opening braces on the same line as the function declaration. On the blue side: the structured purist who insists the opening brace deserves its own dedicated line. This syntactical holy war has crashed more team meetings than null pointer exceptions. The tabs vs. spaces debate might have siblings now, but this brace placement battle has been dividing dev teams since K&R style faced off against Allman style in the coding thunderdome. Your IDE's auto-formatter is the only thing preventing actual bloodshed at this point.

GASP! The absolute AUDACITY of someone suggesting JavaScript users are just lazy TypeScript avoiders! 💅 The eternal holy war between "just let me write my code without 47 type declarations" and "excuse me sir, your variable might be a string OR a number and I simply cannot function without knowing which!" The JavaScript rebels living on the edge while TypeScript devotees clutch their strongly-typed pearls in horror. Meanwhile, that smug reply with the smiley face is just *chef's kiss* perfection - like proudly admitting you eat cereal with a fork because spoons are too much work!

JavaScript's type conversion is like that friend who's confident but wrong about everything. Empty string? That's clearly 0! "07foo"? Obviously 7! And my personal favorite: a tiny decimal like 0.0000005 somehow becomes 5, because who needs those pesky zeros anyway? The best part is how parseInt() and Number() can't even agree with each other. One sees scientific notation, the other just sees numbers to ignore. It's like watching two drunk mathematicians argue about how to split the bill. This is why JavaScript developers drink.

Oh, so you thought the great tabs vs spaces debate was intense? Welcome to the real battlefield: brace placement for else statements! Four different developers, four completely different approaches to where the "else" keyword should live in relation to its curly braces. Top left says "closing brace, else, opening brace all on separate lines" like some kind of vertical spacing enthusiast. Top right is giving "same line energy" with the else snuggled between braces. Bottom left puts the else BEFORE the opening brace like a rebel without a cause. And bottom right? That developer woke up and chose chaos by putting else AFTER the closing brace on its own line. The beauty here is that literally ALL of these will compile (in most languages), but your team's code review will turn into a gladiator arena over which one is "correct." Spoiler alert: there is no correct answer, only strongly held opinions and passive-aggressive comments in pull requests.