every_other

I'm a little bit of a music nerd and I really like 925. Love that vibe and the video too!

I'd say 3 days/week would be ideal. Thanks, not sure I'm looking to jump ship immediately but I'll ping you.

Sounds like freelancing/contracting might be the way to go. I don't have direct client contracts for the most part so guessing it would take some time to build that up. I looked around on some of the generic job posting websites and was seeing some part time opportunities so, that might be an option as well.

This is cool! I had been thinking about creating something similar but I couldn't solve this problem:

Given a radius of 5 miles and three users in a geographic straight line, each 4 miles from each other. User 1 and user 2 are in the same radius, user 2 and three are in the same radius but user 1 and 3 are not in the same radius. Therefor user 1 and 3 will only see "half" the conversation (which would obviously be confusing). Do you solve for this problem? if so, how?

As you start to gain some experience it can be tempting to think your particular philosophy, framework, solution to a particular problem is the right one. Over time, you'll find lots of you assumptions and beliefs that you thought were beyond doubt change. Keep an open mind and don't assume you're right.

Yeah, think that's everyone's first reaction (you shouldn't mix style and markup) but with a component centered development pattern, those concerns largely become non-issues. `card-wrapper` becomes a component and you update your styles there.

I will just say theory aside, in practice, this has worked out great for our team. In my 5+ years experience, I've constantly run across the issue of legacy code with thousands of classes, referencing potentially non-existent markup and countless one-off tweaks. You can start with the best intentions and organization in your SASS files but eventually things start to get really crufty. Keeping everything in components and keeping styles in the markup alleviates a lot of that.

I'm not sure why that was suggested. Our team has migrated to utility css (Tailwind) and we never do this. The basic approaches are either to create a component or template for the button and put the utility class there or use Tailwind's `@apply` utility to create a `.button` class with the utilities applied to that class.

I had some reservations at first but in practice it's been pretty much universally agreed to be great for us. It removes a huge amounts of css cruft that happens over time (unable to determine which classes are still being used, where, etc), keeps colors, margins, etc. standardized through a centralized config file and prevents you from constantly bouncing back and forth between style and markup files.

Thanks, yeah, the ideal situation would be part time at one company so I wouldn't have to hunt down work but freelance might be a more realistic way to go. My skills aren't particularly esoteric but are pretty varied (node, PHP, WP, AWS, React Native, React, etc.).

Thanks for the info, good suggestions!