jmhyer123

From the linked docs:

> Catalyst v0.1.0 is a development preview with unstable dependencies.

So, yeah, it's still a work in progress.

Could you point me to some of those subreddits/forums? A quick search didn't yield anything but I'm probably not familiar with the specific terminology they would use.

I've noticed the same pattern but with one major difference. They are sending the emails to two email addresses, mine and my sister's. Both in the "To:" field so I can see who received the email. Somehow our emails got linked in their database and now she's constantly receiving recruiter spam on my behalf.

Not sure how they got linked, other than the same last name we have very little in common. We work in completely different industries and different job roles.

Really wish there was an easy mechanism to correct the mistake though.

Was there a comment box to tell them why you cancelled? Just wondering if the cancellations are sending mixed signals between the "I'm mad you took down Joe Rogan episodes" camp and the "I'm mad you took down Neil Young or others" camp of users.

I have a Pixel 3. It's the first phone I've truly felt I could live with beyond it's 2 year expected life because the OS is still fast and responsive, the battery still holds a charge and it lasts all day on a single charge. Being water proof definitely helps too. The phone still gets Android OS updates so I don't feel like I'm missing out on features or security. The only reason I'll be upgrading soon is the hardware buttons are failing. The volume up button gets stuck and the power button will occasionally get stuck as well putting the phone in a reboot cycle that's hard to break out of. I'm not sure if this is an issue from wear or if it got dropped on the buttons (I have kids, they're pretty gentle with devices but accidents have been known to happen). I've gotten around the issue with an app that remaps the buttons so if they get stuck held down it just doesn't do anything. The trade off is I have to use the Accessibility tools to change the volume or power off the device, but the tools are really well integrated with the OS (on the Pixel 3, at least) that it hasn't been much of an annoyance at all.

Prior devices were mostly Samsung Galaxy models, the Samsung flavor of Android was terribly slow and consistently got worse as you approached that 2 year mark. The plastic portions of the housing always managed to accumulate chips and cracks especially on the corners and even with screen protectors install the glass would manage to crack at the slightest bump or drop. The OS was already out of date before I bought it and it rarely got updates, if it did it was months after the Android OS release and usually made the device perform worse.

That assumes the general public will buy it and use it which isn't likely if the incentive to do so isn't there.

Except all of those are insured by the FDIC so there's almost no risk outside of market volatility.

No formal policy, just cultural.

We've seen several instances since last March (when we went fully remote) when co-workers were offline for all or part of the day. It was generally understood that it was out of their control and we'd just have to wait it out.

Making yourself available via Slack if possible (via mobile app, etc) helped in case questions came up.

1) I narrowly avoided being laid off as part of a 30% reduction in staff earlier this year.

2) I bought a house with an insanely low interest rate and very favorable terms.

3) That house's value has now appreciated nearly 15% in the last 6 months.

4) My family and I have avoided contracting COVID (so far) and have been enjoyed relatively great health.

I have much to be grateful for despite an otherwise lackluster year.

In the early 2000's I was a teenager, I was fascinated with computers, mainly because my father worked in IT at the time, but I was stuck in the building and tinkering with computer hardware phase. One day my father gave me a copy of "Red Hat Enterprise Linux for Dummies" which included a Liveboot CD. He told me that if I learned Linux I would always have a well paying job. Man was he right. Looking back, that was a turning point in my life. That knowledge opened up so many doors and gave me such a leg up at a young age.

Because cub scouts eat bears?!?

Nope you just have to get the URL right... http://bible-api.com/luke%2014:26

edit: nvm

Latest MacBook Pro and accessories (keyboard, mouse, two chargers, and a branded backpack to haul it around in). One 27" external monitor is standard, but you can request a second. A laptop stand, standing desk, dongles (USB, HDMI, ethernet, etc) are also provided.

Any chance you have a link for this? I'd love to watch/read that.

I highly recommend https://refactoringui.com/book/. It's not SaaS specific but it very much approaches design from a developer's perspective which has helped me immensely in understanding and implementing small tweaks that make huge improvements.

I also recommend watching his YouTube videos. They can get long but it's nice to see the thought process behind a visual refresh/refactor from beginning to end. https://www.youtube.com/channel/UCxqiDtkXtOCNJdckODHk9YA/vid...

Looking briefly at their site, it looks like on some (all?) cars they offer an Uber voucher to get to/from the pickup lot.

I've been very happy with DigitalOcean but be aware that $5 is not going to get you very much. If it's a small web app or static site then the $5/mo droplet will be fine but plan to be spending more like $15 or $20/mo very soon.

Edit: If price is your biggest concern then maybe look at Vultr (https://www.vultr.com/products/cloud-compute/#pricing) to get you started for less $.

I too noticed and was very annoyed with the UI sluggishness of my Android phones (LG something or other and Samsung S7) but decided to give it one last chance. I picked up the Pixel 3 with stock Android and I've never looked back. It's smooth and fast and hasn't seemed to slow as time goes by which was a huge problem with my last two devices. There's such a huge difference between stock Android on decent hardware and "custom" Android (LG and Samsung both apply themes, among other things, to their Android flavors to make it unique) on any hardware, even the best.

Check out https://github.com/255kb/stack-on-a-budget for a great list of services/resources that offer free tiers to get you started.

They we're running on DO account credit so they may have been using the service for a while but haven't needed to pay for the service yet.

We ran into the same problem with our SaaS. We haven't gotten to the point where we need to solve the problem yet but in my research I ran into TaxJar (https://www.taxjar.com/) and was confident they will be one of the easiest solutions to the problem when we get to that point.

This of course assumes a US-based product/users.

There's lots of courses out there similar to FreeCodeCamp, etc. but I think you'll find, like I did, that design is a different beast. It's not something that is codified into rules that are easy to reason about. It's fluid, it's a feeling more than a rule to follow. And what's more? It changes all the time. What was considered "trendy design" in 2005 is now old and antiquated (although, the same could be said of the JS ecosystem, so maybe it's not all that different after all)

That said, there are some "rules of thumb" that can be learned and applied to your existing projects.

Some of my favorite resources for learning design as an engineer:

https://refactoringui.com/ - The book is slated for release soon but I've followed the authors on Twitter for a while now and Steve in particular has some great advice for "designing" as an engineer [1].

https://dribbble.com/ - One thing I've found as an engineer is that most people recognize good design when they see it even if they can't create it. I've spent a lot of time picking out good designs from good designers and replicating them on my own. As I do so I try to reason about why they made that design choice versus something else. Over time I find myself thinking things like, "OK, so you gave the card a larger border radius because you wanted it to feel softer." It's just something you pick up with practice and deliberate effort.

[1] https://twitter.com/i/moments/880688233641848832

I, along with two other co-founders, have bootstrapped a profitable SaaS startup over the last two years while we all three maintained our day jobs. We all have families but have put in nights/weekends to get it where it is. I just made the jump and quit my day job and the other two are just about to do the same.

In retrospect, it was a much safer way to start a business because it took much of the uncertainty out of the equation and eliminated the financial stress. It was possible for us because our startup is a SaaS business, not all businesses can be bootstrapped or built with only nights and weekend efforts. I often wished it would go faster and still think we could have been profitable a year earlier than we were but with time being our biggest constraint it didn't happen. That was the tradeoff we made for financial stability. You have to be OK with small successes and slow progress that evolves into a business/product over time rather than one massive sprint to get an MVP ready to ship in a couple weeks/months.

> It’s been about 3 years now, with a 10+ person team now, so maybe I should write it all up somewhere.

Please do! I'm about a year into a cross-platform app build on react-native and I'd love to hear/learn from your experience.

I've heard good things from multiple first-hand experiences (one buyer, two sellers) about FE International (https://feinternational.com/) though I've never used them personally.

Perhaps. But if "voodoo" results in consistent returns then who cares?

Makes sense, thanks for the explanation.

> If someone says their algorithm relies on some sort of TA, run for the hills.

Care to explain? I'm genuinely curious as I've had some success in this area. Curious if I should be aware of something that I'm not...