Working out some discovery and maybe a PoC for a CI/CD pipeline. We're trying some interesting micro-service techniques for a new internal platform, and I'm juggling a lot of technologies and stacks to get everything to operate and deploy correctly.
The post earlier from Single SPA about their import-map-deployer spurred some huge progress for coordinating frontend deployments.
I narrowly avoided layoffs when I worked in the enterprise space for years; finally got spooked enough after a very large merger that I left to go work in the start-up space.
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.
Mostly good. Celebrating 10 months of being sober and leaving my last job.
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.
Was certainly an interesting alert when my Cloud Functions started reporting downtime. Among the many things that dip in and out on what seems like a monthly basis, I’ve not seen them just drop out in quite a while. Hopefully they get things sorted out. I can’t really imagine what it looks like internally when this level of outage is going on, but I want to think everyone is fairly collected
Showed this to some of the dev team / folks around NBA. Overwhelming good response. Good job!
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.”
> For Webpack, that's creating an empty project and incrementally adding config, starting with just an entry point (use a simple script importing some modules) and an output filename. Add one loader/plugin at a time. Move into boilerplates once you're familiar with the basic concepts.
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.
Hmmm. I think the interaction where it says that it is not yet available in my area and to try again with a New York address could be improved a little.
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.
Perhaps purely anecdotal, but in the years I've been working, I can't say I or anyone I've talked to has perceived an opportunity cost in not having / ignoring LinkedIn (especially the folks who had one and then got rid of it)
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.
I have been using Zoho Mail for years without much issue. They do have occasional outages, which can be frustrating, but they're generally alright for what I'm doing.
I recently finished out a stint at General Assembly's Web Development course in Atlanta. I'm definitely not an average example of my cohort, though I would like to say that prior experience I brought in really drove up the "average" for many of my peers.
Of a class size of 17 people, many of us had jobs lined up before we finished while several were / are still taking time to "get ready"; There was only one who sort of remained clueless during the cohort, but in spite of that they have worked very hard to keep up in class.
The coding required to get into GA was minimal, and the interview beforehand was not very difficult-- the person I mentioned who was generally clueless actually blew through the admissions process (better than I did, in fact).
I'm not sure where it's appropriate to set that barrier to entry, especially given that most of the early material caters to someone with very limited knowledge-- it would have been interesting to see a course targeted at someone who already has a foundation in basic web technologies.
Living in Atlanta, I've had the opportunity to speak with grads of many other bootcamps both in Atlanta and on the West coast. The biggest difference I really notice is between people who were able/willing to work those 60/70 hour weeks to gain as much as possible and those who couldn't/wouldn't.