HN user

jgill

56 karma
Posts14
Comments52
View on HN

Backtracks| https://backtracks.fm/?ref=hn | Product & Engineering | Austin, TX, USA | Full Time | ONSITE

Backtracks helps audio content creators and brands know and grow their audience and revenue. We build delightful software for podcasts and spoken word audio.

Roles:

* Mid-Senior Front-end Software Developer https://www.workable.com/j/29D360401E

* Senior Python Developer https://www.workable.com/j/6250CAA462

You should know that we don't eat lunch at our desks. It's important enough to put here. We trust you to get your work done and don't micromanage a highly talented and professional team. Backtracks is a "Get Things Done" culture that deeply cares about our team, partners, and changing the world of spoken world audio. We value mastery, talent, and a good sense of humor.

Benefits:

- Equity

- Medical, dental, and vision insurance

- Flexible vacation policy; take time when you need it

- Flex-work; ability to work from home or remote at times that fit with life

- 401k

- Annual company retreat

- Subscription to a consumer audio service

- Choose your own laptop

- Audio gear allowance

This is a really good link to share. Thanks, I also ordered Thinking, Fast and Slow the book because of this posting and the comments. This thread has been pretty interesting to me even from an "at speed of thought" perspective.

Certainly in lower levels of education, "fast" thinking against known problems and problemsets is the norm (at least in the United States). I worked with a few "fast" thinkers that fell into a strange, at the time to me, category of people that I could recognize as intelligent and could solve a certain class of issue or problem easily, but when it came to a more difficult problem space or perhaps one that requires delayed gratification (or no real external recognition/validation/praise) they would give up. The "deep" thinkers seemed to give equal or near equal weight to the validity of options in many cases. There's a time, place, and type of problem that can benefit from each mode of thinking.

You need to really analyze your requirements. Why do you want/need a message queue and not a database? Do you need to support message durability, clustering of nodes, nodes in different geographical regions, topical subscriptions, what kind of routing concerns, technology support (do you want/need to write your own client to interface with the message queue? hopfully not...if you're using a particular language you just might though), protocol support (do you need amqp support), etc.?

Personally I like RabbitMQ.

I would second this. Imagine you can self-fund a successful company, there is no reason for your company to go public if you are profitable and generating revenue unless that in turn generates more income. This is a great for the owners of the company if you never have to take outside funding, but imagine that you have options in a company that never needs or wants to go public. Sure they can get you to work hard for a few years under the illusion of going public, but without a forcing function like a well timed exit there is no way those options will possibly be worth anything.

So by taking outside VC equity based funding an entrepreneur is signaling that they can raise money if needed, that if the company works out there's a chance the non-founders will make money, and that the founders can deal with the pressure VCs will put on them and the company to perform [and yes that can sometimes mean ousting the founder(s)] and produce an exit event.