445 karma · joined June 23, 2010
twitter/dylanized
we use Apollo Client to communicate with our bff layer, which is Express and Apollo Server. The graphql resolvers in turn grab data from underlying Java REST apis, which are not exposed to the outside internet.
Overall it's worked great for us. Graphql takes a lot of getting used to, but it frees our teams up to move fast on their own, especially vendor contractors. Negative is, our schema has gotten gargantuan and needs to be heavily refactored.
One really cool thing Apollo Server unlocks is caching, and also a great metrics dashboard
Also did bff in the past for a health care company using Go. Challenge there was natural latency hitting slow backend apis and transforming the data
Some startups just don't have the money to throw around where they can list a position over 150k.
For companies that do have that money, they change the title - I do a lot of DevOps but I am a Solution Architect. Some companies have Platform Architect role(s). Edit: and everyone needs experienced Site Reliability Engineers
For many non-tech companies, in-house salaries might be pegged low but then they hire contractors which can command high rates, perhaps billing as much as $200/hr (granted, a cut comes out of that). Also these contractors can conceivably be handling more than 1 client.
put your consumer marketing site front and center at x.com
sub-brand your enterprise offering, and have a section explaining it, i.e. x.com/pro
this way you're maximizing your seo juice and consumer reach
the actual apps themselves can live on a subdomain, i.e. app.x.com for the consumer and pro.x.com for the enterprise
if/when the enterprise version really takes off, you could always rename it something unique if desired
separate computers for work/media
quiet dark home work spaces
coworking membership
deliberately sticking with old (or no) technology
days off from social media/tech
- try linkedin and ziprecruiter
- volunteer for a project or launch your own side project, for more experience
Ask for 30-day paid leave of absense. You stay on during this time as an employee at your current role, so doesn't disrupt the financing.
IF they say Yes, then enter the agreement in good faith and be on standby during the 30 days. Maybe they'll end up wanting to extend the deal another 30 days. A the end of the 30 days, YOU decide whether to go back to your role or put in your 2 weeks.
IF they counter with lower pay during the leave of absense, then say OK but I want my stock options secured.
IF they fire you on the spot, then they deserve whatever pain they get.
Tell your team you intend to return to your role, but the writing will be on the wall.
Basically you're offering the company on-call transition consulting, in return for some extra vacation pay. Win win situation
better approach might be to build your own project/mini-startup, then hire a little consulting whenever you hit a pain point
1. Not effective
2. No ancillary benefits
3. ah, edgelord self congratulations
2. start a blog
3. get a tech job and save all your money for a year
4. try to find a girlfriend, you are obsessing yourself to death
In my team we do these on Monday/Thursday. If something conflicts, we just bump that checkin forward a day to Tuesday or Friday.
In the past I used BlazeMeter SaaS, which rocks
The Mythical Man Month explains it best
And start your own micro-startup