ptasker

petetasker.com

Dealing with unicode bugs taught me a lot about computer science academic theory. It helped to understand memory addresses and how encoding works.

Repo was created by this guy: https://www.freecodecamp.org/news/why-i-studied-full-time-fo...

I started looking up plans online and built a bench and table. From there I've built various other pieces of furniture - tables, benches, shelves etc. It's mostly as others have said, trial and error.

Wood is pretty forgiving, especially soft woods like pine/spruce/cedar.

It's mostly just finding plans and ideas online and YouTube. Then taking your time. Like anything else, you have to enjoy it. I personally like how different it is from programming.

Definitely worth it for me, higher_quality_furniture++

I would imagine using a GPU compute instance would bring this time down significantly.

Yup ignore it. Front-end dev is super complex these days! I started when it was just HTML/CSS. JavaScript dev these days is much more complex than some 'real' programming languages!

For real, the OPL is awesome. Great spaces and they even rent out video games.

Yup, I also tried to use the debugging tools in the new FF Dev Edition with a larger React codebase and it's a bit buggy for sure.

We're currently using Level now and it's definitely different from Slack. I think the biggest issue we have with it at this point is that it's still in active development.

It's also missing a lot of things that you take for granted with Slack. Things like auto-link expansion and third-party integrations of any kind.

Same here. Apple music had trouble loading music and just generally acted sluggish. I gladly pay for Spotify.

Yep, also disappointed to see it in GA missing queries and back ups. Makes it a non-starter for most folks.

The issue we had with cloud Firestore is the inability to _really_ query documents through the Firebase console. It’s very basic and there is no third-party tooling available yet.

To run any kind of specific query you’d need to handle that application side. Just something to consider.

Pretty cool, but I recommend anyone wanting to do this kind of thing to check out the source Puppeteer library. You can do some really powerful stuff and make a custom crawler fairly easily.

https://github.com/GoogleChrome/puppeteer

Also, find companies that you'd like to work for that hire remotely. There are plenty these days.

Yep as been mentioned, it's obviously a lot more difficult to get remote gigs. I probably applied to around 20 places over the course of 6 months. Some I heard back from, some I declined, and most I never heard a peep. I've got almost a decade of experience too, but it's just that competitive.

- You need to stand out, have a decent Github profile and/or solid code samples that you can share

- Demonstrate the ability to work autonomously

- Be patient, it takes time.

It's also worth mentioning that if you do get rejected ask them what you can work on. Helps to know what you can do to bet better and get a remote gig later!

Source: working remote for the past year