I did frontend before React, and it was a welcomed change. The core insight of UI being a function of state is a good one. It saves you a bunch of headaches from the jQuery days where you’d have multiple code paths per UI element (adding, removing, mutating). That said I think they lost the plot with hooks and things have gotten needlessly complex since then.
This is pretty cool! I wonder if you could make one with an adjustable mounting system for the long tail of weirdos like me with a new iPhone SE and other models.
I'm Jeremy, cofounder and CTO of WaySync. We're a venture backed startup building software for freight forwarders. Freight forwarders coordinate and facilitate complex, large shipments from the manufacturer to their end customers. This is a complex process that often involves multiple modes of transportation (rail, trucks, ships, planes) and customs clearance. It's $145B industry in the United States alone that's been historically underserved by software vendors. Along the way, we hope to do our part in alleviating the global supply chain crisis.
I'm looking for experienced, fullstack web app engineers to help us build out an MVP and a strong engineering organization. This could be a great fit if you like being given high level, potentially ambiguous problem statements and building end to end solutions with little oversight but as much collaboration as you want. Also a great fit if you’re interested in doing your own startup one day or growing into a leadership role.
Tech stack is pretty flexible aside from Rails (exp not required). Currently thinking a mixture of Hotwire and React for frontend.
We're a remote first company but you're welcome to join us in person in NYC. We're open to hiring remote from other countries as long as you're in North / South American timezones. We're also open to sponsoring select visas (e.g. TN) if you'd like to come to the US.
I'm Jeremy, cofounder and CTO of WaySync. We're a venture backed startup building software for freight forwarders. Freight forwarders coordinate and facilitate complex, large shipments from the manufacturer to their end customers. This is a complex process that often involves multiple modes of transportation (rail, trucks, ships, planes) and customs clearance. It's $145B industry in the United States alone that's been historically underserved by software vendors. Along the way, we hope to do our part in alleviating the global supply chain crisis.
I'm looking for experienced, fullstack Rails engineers to help us build out an MVP and a strong engineering organization. This could be a great fit if you like being given high level, potentially ambiguous problem statements and building end to end solutions with little oversight but as much collaboration as you want. Also a great fit if you’re interested in doing your own startup one day or growing into a leadership role.
Tech stack is pretty flexible aside from Rails. Currently thinking a mixture of Hotwire and React for frontend.
We're a remote first company but you're welcome to join us in person in NYC. We're open to hiring remote from other countries as long as you're in North / South American timezones. We're also open to sponsoring select visas (e.g. TN) if you'd like to come to the US.
Which may or may not be worth anything. The rule of thumb is to value stock options at 0 for a reason. As opposed to RSUs, which are liquid upon vesting.
Phone screen was super short, like 5 minutes. Followed by a vague exercise to create a tracking service without a database (wat?). Then there was like 2 weeks of back and forth emails for scheduling for a review until they said they needed someone with "stronger programming skills".
Seems like you should just reach out to the startups and see if there is interest. If there are multiple interested, try selling it as a white label service. Otherwise sell it outright with a multi-month contract to help with the integration.
If there's no interest though, then any upfront work you do now will be wasted effort.
Why not just explain it in plain English right on the page? Expecting potential users to read a wiki article just to understand what your product is seems like unnecessary friction.