One of my favorite LNs. I really enjoyed this chapter coming to life in manga. Also, totally related to his observations of the detractors causing trouble for no reason.
Thanks to the scanlators for the TL!
jim
joined 1 year ago
Hah, nice chapter! Contact info has been exchanged!
It's not about what it is today but what it can be. I agree that there are a bunch of problems, but the future does look bright.
I think you've succinctly described what I hate about GPL. I could never put my finger on it except that it's a pain the butt.
Staying at this current job comes with a lot of risks. Say you got fired today, how well could you handle it? Do you have the financial and emotional wherewithal to land on your feet? I'll reiterate the emotional part - just because you can afford to lose your job for two months doesn't mean that your emotional health can take it.
If the thought of being fired is terrifying, then I would try to find someplace that is a better fit. You may not be in a good place to take the risks that comes with this position. That's OK. It's completely understandable that you aren't willing or ready to take it on. You can start looking elsewhere.
If you are willing to take risks and push yourself, you may want to stay at this job. In some ways, the turbulence you're experiencing now will make you a better engineering manager. It sounds like you have a good head on your shoulders, and the advice that @nibblebit gave is pretty much spot on.
Good luck.
Created a bot to post mangaplus (lazy fork of /u/AutoShonenpon from /r/manga). Let me know if things should be tweaked.
Story time:
There was a long data pipeline that produced wrong results. The wrong results were subtle but reproducible. Each run was about an hour long in dev, and there was no intermediate data set. It takes some input, runs for an hour, and produces an output.
The code was inherited and was a bit of a mess. Instead of digging through the code, I re-ran the pipeline through from about 6 months ago when we knew there was know bug. It was about 100+ commits since that time.
Mind you, the bug could've been anywhere in the codebase as far as I was concerned.
Took about a day of git bisect to narrow it down... to nothing. I found out that running code from the first commit from 6 months ago also produced incorrect data. Oops. That's weird though because the code was running correctly back then.
A few days of debugging later, and I eventually found the culprit: a dependency package got bumped a couple weeks back. Some sort of esoteric parser had a bug but didn't fail. It incorrectly parsed some data after the bump. Going back a version fixed the bug.
So yeah, git bisect killed about a day of my time.
That's pretty neat. I wonder if they had to switch sets because backgrounds for black and white shows used exaggerated colors to improve the contrast.
See The Addams Family set below.
TIL about the squircle
Nothing wrong with recommending a Mac. I'm not a Mac guy myself but I am pretty productive with one.
The code in the community's banner is in python 2. Can we get that changed?
I use shared Google Docs for most things, like meeting notes, 1 on 1s, performance reviews, etc. There are some HR tools but they aren't universally used.
Other than that, there's the usual suspects for project management, issue tracking, etc that most people use.