lberlin

ReciPal (https://www.recipal.com) | Founding Rails/Full Stack Software Engineer | REMOTE | Full-Time

We aren't actually hiring anyone immediately, but we've hired a handful of great engineers from HN and inevitably will need to hire again. We've found having those conversations and keeping in touch is much better than going through the process from scratch each time, as it fast tracks the process a great deal when the time comes. So reach out if you think you're a good fit.

ReciPal is a profitable, growing, bootstrapped, and (have always been a) fully remote company (based in New York) with 6 full-time employees. We make simple software for food businesses - nutrition analysis and labeling, costing, and inventory management. We've been around for almost 15 years now!

You'd be working directly with me, solo founder, our senior engineers, and marketing and support colleagues, and hopefully take on a growing role over time to treat the business like your own. It's a very low key work environment, but independent and plenty of responsibility and ownership for the right person.

Stack includes Rails 8, JavaScript, Postgres, Heroku.

Full job description: https://docs.google.com/document/d/1At0_nQH5Vqvn3AQRjPLLUMi2...

Thanks for the comment, glad it resonated with some folks! Underqualified, overqualified, we'll take a look if you want to send us an email.

Sorry for the super delayed reply, didn't expect questions/comments, so just checking this a week later! It's not strictly ruby if you're comfortable adopting another language/framework and are otherwise a great fit for the role.

ReciPal (https://www.recipal.com) | Founding Rails/Full Stack Software Engineer | REMOTE | Full-Time

We are hiring a full-time engineer who can hopefully be a technical stakeholder and business partner.

ReciPal is a profitable, growing, bootstrapped, and (have always been a) fully remote company (based in New York) with just about 4 full-time employees. We make simple software for food businesses - nutrition analysis and labeling, costing, and inventory management.

You'd be working directly with me, solo founder, and our senior engineer and hopefully take on a growing role over time to potentially lead engineering and become a business partner. It's a very low key work environment, but independent and plenty of responsibility and ownership for the right person.

Stack includes Rails 7, JavaScript, Postgres, Heroku.

Full job description: https://docs.google.com/document/d/1At0_nQH5Vqvn3AQRjPLLUMi2...

This is amazing in every way. Well done on the business, choice of backend, and post.

Have been using the Free Forever plan and it's solid! They've made a lot of UI changes to streamline the whole process. Nice to have it auto scheduled with a report of changes every month. And they summarize the issues in their UI much better than the standard reports you'd get running the scan yourself.

"Sheepishly"!

I meant the risk of being reported to CPS (or being called out in general) rather than the risk of CPS overreacting. Once it gets to them it sounds like they go by the book, but fair point.

Seems like what "CPS would do" is the same logic described in the article itself, but instead of the perceived (but not statistical) risk to the children it's the perceived (but not statistical) risk to the parents of those children. I doubt (don't have real data) that reporting actually happens often at all, but it's so easy to imagine and potentially embarrassing and scary for a parent that they avoid it. So even if you don't buy into the perceived risk to your kids, you buy into the perceived risk to yourself.

It didn't sound crazy at the time. It sounded crazy at the time to investors - old, rich white guys (I'm generalizing, of course). These guys didn't need to or want to stay in an AirBnB, or at least didn't before it had already become commonplace.

Younger folks though, traveling on a budget, interested in meeting other people while away from home - it's a no brainer. We all stay on friends couches, in guest rooms, share cars.

The main difference I see between bikes/pedestrians and cars/motorcycles is that there is minimal cost/effort to reverse and change your mind. So, on a bike or on foot, you can jaywalk or run a red light by slowly peeking out and making sure it's safe. If someone with the right of way is coming, you can simple stop and let them by. You absolutely can't do that with a car or motorcycle.

My general rule, as both biker and pedestrian, is to not get in the way of others who have the right of way. They shouldn't have to change course or worry about you. Most pedestrians (and plenty bikers too) are absolutely clueluess though. They don't look for bike lanes, they walk in the bikelanes, they jaywalk without looking if a bike (or car) is coming, they open car doors without looking, etc. I think this frustrates a lot of bikers, so they end up not caring and trying to ride through a crosswalk full of pedestrians and doing other asshole things, but I don't think that's the norm.

As a reasonable adult, I know I shouldn't jaywalk or run a red light because they are rules, but I have confidence via my senses that I can do that with absolute safety and respect for myself and others.

I can't comment on the situation of writing code for useless features for bad managers. That is a separate mental hurdle.

But I think all of us sometimes struggle with sitting down and getting things done. When we have a bad day, it's because we struggled making decisions and didn't end up accomplishing very much in our own eyes. We're our own harshest critics.

One thing that I've realized (actually just in the last few days) is that you simply feel 10 times better at the end of the day if you write a lot of code, knock of tasks on the to-do list, and generally "get things done".

Knowing that diving in and doing hard things will make you feel good makes a huge difference for me. It's like "Ok, this might suck a little getting started, but it's what will actually make me feel good and happy." It's really easy to sit and think, or read the internet, but it's not a good feeling at the end of the day.

As far as wasting time, whenever I'm struggling coming up with an approach or solution to a problem, I start writing it down. It usually doesn't get too far just in my head. But if I map it out, write it out, I get back to working on it much faster. An inefficient solution that works gets you much closer to the final product than struggling to find that "perfect" solution right off the bat. Make it work, then optimize.

Full disclosure - it's not actually a 4-hour hackathon, but we're looking for mentors/programming experts to help out remotely, which can just be a few hours at a time.

All thoughts on the general idea would be awesome as well.