mfrye0

A helpful tip for finding a new job that uses technologies you don't have professional experience with, but you want to learn...

Say you want to learn Rust, but all your experience is in Javascript. Most recruiters will immediately filter out your resume if you don't have the keyword "Rust" somewhere in the document.

Before you start sending out your resume, spend a few weeks hacking on a Rust side project to learn some of the basics. Then on your resume, include a description at the top saying you're proficient in Javascript, but want the opportunity to work in Rust. Then include a "Side Projects" section at the bottom that lists your Rust experience.

I've landed 3 jobs that way, where I'm hired for my experience with X, but under the condition I will have the opportunity to learn Y. Otherwise, it's easy to get trapped working with the same tech at a new job, and your skills eventually become obsolete over time.

I replaced "normal" TV with occasional documentaries, news, educational programs, TED talks, etc. If I'm feeling lazy and don't want to read a book, something like Vice on HBO is pretty legit.

It depends on your situation.

Part of mine is that I've had 3 bosses straight up steal money from me over the years. So the fear/pain of getting screwed by another boss is greater than the pain of starting a company.

Apart from that, I don't know about you, but I came to the realization of how short life is awhile back. You have 70 or so years to do your thing, then that's it. You're dead. For me at least, the pain of dying and not having done anything with my life, is more than the short-term pain of working on your dream.

So I don't know man. I'd say it's more what do you want out of life vs self imposing pressure.

I think this is it: https://www.raspberrypi.org/forums/viewtopic.php?t=172114

I read it awhile back. Really interesting.

Idk if it's just me, but it hurt my eyes to look at that site. The dark background and red/pink font were too much.

Apart from that, it looks awesome.

This looks really interesting. We've been having challenges internally where we have a number of microservices, some running locally for active dev, while some running in a dev/staging env we connect to via ssh.

I have some experience working with docker compose, and the original idea was to use that to set everything up locally. Is this similar / are there any other comparable frameworks to this?

I was thinking the same. Realistically, I believe the only way you could do that on the client would be JS. But if they added that, it would change all their feel good marketing about no JS...

Yeah. That's why I bought a webcam cover. I highly recommend if you don't have one already.

From my experience, as I did exactly that..

- If you're looking for a new job, find one that has a good work life balance and where you will learn skills relevant to what you want to do. In my case, I was weak in dev ops, so I picked a job where I'd learn that.

- As far as the legal front, a company can't own 100% of your time. When you begin working on your own stuff, use a separate computer, and keep notes with dates. Basically you want to show evidence, in a worst case scenario, that you created this in your own time and not using company resources.

- Then don't tell anyone about what you're working on until after you leave your job. Once you leave, ideally everyone will think that everything you built is post-job.

- Once you leave your job, depending on what you built (if it's competitive with your past job) it's good to tell everyone about it. My early investors were my co-workers.

That's just stuff off the top of my head. Happy to provide more info if you want. And best of luck to you! Starting a company is a hell of an adventure.

I've evaluated Timescale, Clickhouse, Druid, and Pinot for our own use case.

Druid and Pinot have a lot of moving parts. If I remember correctly, Druid was something like 6-8 different nodes for different parts of the ingestion / querying processes. So it's going to be a lot of upfront and ongoing dev ops work.

Clickhouse is interesting because it seems to just "work". One thing to deploy and you just increase the number of nodes as you scale.

Being a small team, we try to have managed hosting as much as possible. One less thing to think/worry about.

Then our stack is primarily in AWS. So when it comes to DBs, I'd prefer to keep it all within our VPC for security / latency reasons - for sensitive data at least.

No. https://forums.aws.amazon.com/thread.jspa?threadID=261623

The theory is they are not supporting it in favor of promoting their new time series DB.

BigPicture (https://bigpicture.io) | San Francisco | ONSITE and REMOTE | Frontend Engineer and Fullstack

We help sales & marketing teams identify, prioritize, and act on accounts in real-time.

Engaging prospects at the wrong time costs companies $591B each year. BigPicture surfaces ready to buy signals to help teams identify hot opportunities and prioritize which accounts to focus on.

We've been flying under the radar for quite awhile, and have been working closely with early customers to rapidly iterate on our product. 2019 is going to be a big year for us. We're looking for solid devs to help us grow.

Front-End: React, Typescript, PostCSS, Webpack, etc. Back-End: Node.js, Python, Rust, PostgreSQL, Redis, Docker, AWS

You can reach us at jobs@bigpicture.io if you're interested.

BigPicture (https://bigpicture.io) is a solo founder operation. I was the only person for the first couple years before I grew it enough to start hiring.

I don't recommend anyone follow this path now having been through it myself. Being a solo founder is absolutely brutal.

Yeah, Moesif is legit. We're a customer.

For sure.

Google Chrome Version 71.0.3578.98 (Official Build) (64-bit)

Looks pretty cool.

Heads up though. There's a bug on your sample page: https://www.pubilling.io/sample

When you click the "Edit" button for the CC, the UI shrinks into nothing...

For sure. Like I said, I usually do a custom build of a framework, then strip out the stuff I don't need. And if it's designed with variables, changing small stuff like breakpoints etc is maybe a few quick changes.

I've done frontend for quite awhile. I usually start with some sort of framework for every project and use only the minimal pieces for the foundation.

Generally you need the same stuff for every site:

  - reset/normalize the styling cross browser
  - basic grid system
  - typography, forms, and buttons
  - "componentized" files with variables (sass, less, post css, etc)

Basically I start with a custom build of whatever framework, use that to build the MVP, then customize it according to the designer requirements. Lastly, I'll pull in components as I need them.

Why reinvent the wheel and start from scratch?

I've seen very odd events as well that have convinced me this is happening.

Went to a friends house and ending up discussing the most random, very specific topics. 2 of the 3 topics popped up in ads on the way home an hour later. Never searched anything related on my phone prior to then.

What I do have are a very particular set of skills; skills I have acquired over a very long career.

:)

Thanks for the advice guys.

I'll have to think it over, but it seems like the general sentiment here is towards taking the job.

Tried that. I got 1/3 refunded so that helped a bit, but it's still ~6x what I had planned vs the 10x bill.

I'm in kind of a unique situation. My last startup was too many founders and gave up all the equity for an early fund raise. So I decided to go solo for this one and bootstrap it.

Since I'm bootstrapping, I haven't had funds to hire anyone. So I've been giving equity to friends to help part-time and then hire contractors for stuff as needed. I've already cut down all expenses to bare minimum.

I'm generating income and almost there on breaking even. I think a couple more decent sized customers will get me there.

I've been doing some consulting and custom dev, which has helped, but it's been as needed type of stuff.

That's what I was thinking too. I've been off the job market for a bit, so I guess it surprised me to get such a high offer.

That's also part of the frustration though. The business is just starting to take off, but I'm fucked financially if I can't figure out something soon. This AWS bill really messed me up...

Not a bad idea. I was thinking something similar to where I could possibly hire a few people for what the salary is.

Only fear about going into hibernation is falling behind competition wise...

I'm using API Gateway, Lambda, and the IOT Platform to do realtime lookup / enrichment stuff for contacts in our CRM.

I setup a webhook in the CRM to call the API when a contact was created or updated, which would then enrich (update) the contact. I didn't realize that I had to disable the option to not trigger the update when the contact was updated via the API. So it created an infinite loop of updates that called everything millions of times before we realized what was happening.

I guess the one positive here is that our system can scale and handle the traffic :)

Yep, lesson learned.

I've thought about that. I'm not sure where I'd begin on that front though.

Ironically, I've been talking to this huge company who's interested in our IP. If I played it right, I could probably sell to them, but it would likely take at least a few months to make a deal happen.

He's been trying to recruit me for awhile now, and I already tried that strategy a couple months ago. He wants full-time people to build the team.