The fewer bugs you’ll introduce.
I don’t know squat about kernel programming, though. :-)
1,448 karma · joined January 17, 2017
I don’t know squat about kernel programming, though. :-)
“Which burner is your favorite? Mine is back left.”
Wound up spawning off a separate thread from our would-be stateless web api to run recurring bulk processing jobs.
Then coupled our web api to the global singleton-esque bulk processing jobs thread in a stateful manner.
The wrapped actors up on actors on top of everything to try to wring as much performance as possible out of the big server.
Then decided they wanted to have a failover/backup server but it was too difficult due to the coupling to the global singleton-esque bulk processing job.
[I resigned at this point.]
So yeah color me skeptical. I know every project's needs are different, but I'm a huge fan of dumping my code into some cloud host that auto-scaled horizontally, and then getting back to writing more code that provides some freeeking busines value.
Didn’t care to get out much., but figured I’d stroll to the beach to watch the sunset.
Got about halfway there before figuring out where I’d gone wrong.
Foo Technology unambiguously did not exist as a separate company in any form.
Thing is, Foo was the unlikely company where the line workers were more satisfied than the Technology employees - the company overall was very decent but the technology org was toxic.
Accordingly, Foo Technology had lousy ratings and negative reviews, while Foo has largely positive reviews and a strong rating. The difference was on the order of Foo~=4.0 while Foo Technology~=2.0, both derived from a significant number of employees.
You can imagine the pitfall this could create as a prospective technology employee contemplating a stint at Foo.
As a disgruntled Foo “Technology” employee I contacted Glassdoor to notify them that a nonexistent company was distracting many genuine reviews away from a legitimate company.
Glassdoor notified me that they would not provide any corrective action unless the formal owner of the Glassdoor account for Foo agreed to it.
This told me that accuracy of reviews on Glassdoor comes in a few positions shy of their top priority.
Although in full disclosure, a year or two later the 2 separate “companies” did get merged on Glassdoor. I don’t know what the impetus finally was, but they certainly didn’t give a shit when I notified them of the snafu with their system.
My recent experience is probably a fluke and would therefore be unhelpful, but I finally optimized job selection exclusively by pay rate, accepting a role in a tech stack I have no experience with and honestly, very little interest in, and yet the engineering culture and overall experience are turning out to be the best in my recent memory.
I strongly suspect that it will stick this time.
Is but one single data point, but it cost me quite some months to learn (I tried to talk them into simpler solutions for a while and then gave up and bailed).
What is 10 million jobs minus 9 million jobs that are reluctant to hire you due to a history of job hopping?
“grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too”
And it was severely under reported.
Recommend sending Biden a message (I guess via whitehouse.gov) that you’re tracking this issue.
I’ve had the same thought before - America does a great job within its population bracket, but it doesn’t make sense at all comparing us to, say, a Switzerland or a New Zealand.
Eventually perhaps building in some moisture sensors and some pi/arduino logic to then control the pump.
"Tell me about a recent time the team was allocated time to resolve some technical debt. Tell me about a recent time the team was NOT allocated time to resolve some technical debt." I worked at once place which shifted from outsource to in-house software development, discovered that some of the primary html views of the website were built using a jumble of string concatenation, and to add a new feature using the existing string concatenation.
"What percentage of my time will I spend coding in this role?" Worked at one place which assigned excessive non-coding bureaucratic duties to developers.
"How often do you release software?" Worked at once place which did not release anything for the 1.5 years that I was there.
"How do you incorporate the lessons learned partway through a project into the remainder of the project work?" Worked at one place that could not pivot due to inability to admit that they didn't have a perfect plan from Day 1.
"Tell me about some advanced design patterns that you don't use." Worked on a team that used every advanced design pattern that mankind had ever given name to, each in 200 places without an iota of consideration to the costs that go along with the potential benefits.
"Do you plan on shifting your entire tech stack into something else that can scarcely be considered software development?" Self-explanatory, but has happened to me 2x now, so be on the lookout.
Fifteen+ years into my career, I've discovered that every job will give you one or more damn good reasons to move on, and each of these lessons above took 1-2 years to learn, so my latest strategy is just optimizing for pay rate. :-)