People ask me this all the time, and it's not something to sum up in two sentences. There are a lot of things to consider if you're moving from web to mobile, particularly in the React ecosystem.
That makes sense. Our boilerplate is for all new-code projects where we get to pick the stack, in which case we default to all things TypeScript anyway. If a client project has an incompatible existing codebase, we take a different approach.
* 20% personal investment time EVERY WEEK.
Learn, create, give presentations, etc.
* Life-first culture. NEVER get asked to work late or on weekends.
* Work on a variety of projects.
* Work on great tech for interesting clients. Univision, Teladoc, Bose, Axios to name a few.
** The job listings are for iOS / eng mgr / PM, but our core skillsets are React Native, React web (Next.js), Node. Some Ruby on Rails as well. Don't hesitate to apply. **
It's a great place to work. You will grow and you will love it.
Consulting is often the quickest cash, assuming you're an engineer with a decent network. You're not on socials, but do you have people you've worked with? Contacts at businesses? Other devs?
Email everyone telling them you have a few weeks free.
You could also call tech recruiters who could potentially place you on a short gig fast. But will naturally take a cut.
Alternatively, I know others made good money doing crypto day trading, but I'd imagine you'd have to know what you're doing.
Some of this you can look up on CrunchBase beforehand, which you definitely should do. For me I believe in trying to gauge just how prone to borrowing the founders are; if they have a solid model and are more inclined to seek profit rather than investment (except after proving the model, and primarily to increase growth), then that's a good sign.
If however they seem like they approach is constantly to borrow money, that's a red flag.
* How much runway does the company have? What will the plan be when we start to run out?
* How well have you proven the business model?
* What type of validation/research did the team do for product-market fit (before building the product)?
* What's the management team's approach to profit vs investment?
I wrote this up to share some things we've learned about how to reuse your styles in React Native, closer to how you might do it on the web with SASS/LESS.
Location: New York City.
Remote: yes. Onsite ok too.
Summary:
* 15 years dev experience
* Full-Stack Development / Team lead optional
* Ruby on Rails
* Pro Front-end (jQuery, Angular, React, Backbone, Responsive sites)
* Wordpress augmentation
I think this is a very reasonable argument for per-project billing, for the reasons you mentioned. But the downside you mentioned is valid also - that some clients will be greedy with your time.
I prefer time based billing, because I don't work 8 hour days like normal people. For this reason I also make sure I'm working on things that can be done in those timeslots, and I'm very, very conscious of the client's time.
I think either method is fine as long as you're comfortable with it, and you're on the same page as the client.