The post earlier from Single SPA about their import-map-deployer spurred some huge progress for coordinating frontend deployments.

Got laid off two weeks ago with not much to walk away with except a weeks salary. There were severe cash-flow problems, and I get the impression that those that remained at work are potentially facing some more layoffs soon.

Sort of freaked out for a day or so and started grinding through the "find a new job ASAP" process. Thankfully the market where I live seems to be doing well, so I have a new gig to walk into next week.

Remote: Maybe

Willing to relocate: No

Technologies: Ruby, JavaScript, Python, PHP, Kubernetes, ElasticSearch, Redis, RethinkDB, MySQL/MariaDB, Postgres, Google Cloud, AWS, Terraform, Ansible, Docker

Résumé/CV: www.linkedin.com/in/jpsandlin (PDF available by request)

Email: joshua.sandlin@gmail.com

Currently looking for a role doing full-stack development or purely backend work. Very proficient at some of the activities of an SRE as well.

Just spent the past two days rolling out a new Elasticsearch cluster for work that was giving me panic attacks for weeks (first time “architecting” on that level). Things went really well, so I can probably sleep alright before a big “investors meeting” later this week.

Idk, I feel good. I just think I could probably sleep a bit more and be better.

How are _you_?

Current job uses GCP and a lot of Kubernetes. I’m interested in evaluating replacing some of the smaller services with Cloud Functions (or Cloud Run if it fits better)

Looking around, a lot of the tools I used at my previous job have flakey or really hindered support for GCP.

Just sort of curious what other folks are doing out there or how they might compare GCP offerings to AWS offerings

Comments URL: https://news.ycombinator.com/item?id=20408013

Points: 2

# Comments: 1

It’s really strange to see people who are genuinely interested in knowledge and sharing a learning experience get shut down.

It also is just upsetting because Cody’s Lab contains so much interesting material.

Only qualms might surround ToS for `stats.nba.com`:

> You may download material displayed on the Site to any single computer only for your personal, noncommercial use, provided you also maintain all copyright and other proprietary notices contained on the materials. You may not, however, distribute, reproduce, republish, display, modify, transmit, reuse, repost, link to, or use any materials of the Site for public or commercial purposes on any other Web site or otherwise without the written permission of the Operator.”

But I don't think you're likely violating this.

I attended a General Assembly bootcamp last year (to great success afterward for me), and the pervasiveness of jumping right into a generator / boilerplate really caught me the wrong way.

I felt like going the path you describe, starting with relatively low complexity and building on top of it, was/is the right way.

Even talking to co-workers who have been doing this stuff for years, there's little incentive to jump into a boilerplate, if only there's then two learning curves... one for the boilerplate / its layout, and one for the tooling involved (React or Angular, etc).

> A boilerplate is another person's code, and while it's good to avoid NIH, unless it's superbly documented, it contains tricks and workarounds that only cloud real understanding.

This caused a lot of headaches with other students in my class (and classes afterward).

My idea to "solve" it was to incrementally build out my/our own boilerplate so we'd be able to at least use that confidently, as well as maybe have some understanding into how someone else built their boilerplate. It got shot down due to time constraints, though.

Whenever I'm asked to come in and mentor newer students for their projects, this is something I try to impart, though.

Go ahead and let me enter in my information and put me in some sort of potential new location queue-- get enough people near / around me, and you can start to decide where to support next.

Just a thought.

I've really only ever received an inordinate amount of entry level recruiters "connect" with me using the same canned email they send everyone. I thought the references feature was nice, but the past few places I've been at have officiously discouraged using the feature because of PR issues (I might personally give someone a recommendation which could then not actually represent the company's perspective of the person)

In my opinion, LinkedIn is just a very creepy and annoying service.