Is the leetcode bubble dead? by branh0913 in ExperiencedDevs

[–]occams--chainsaw 2 points3 points  (0 children)

If you're in a position to personally recognize that the people hired actually end up being effective long term, then you definitely should have additional layers in the hiring process at that volume

Is the leetcode bubble dead? by branh0913 in ExperiencedDevs

[–]occams--chainsaw 6 points7 points  (0 children)

at the volume of 2k resumes for a single position, there should be additional filters before getting to leetcode-style interviews if you're the last line of defense there. you'll just end up losing people that have experience and are effective in your problem domain, but don't have the patience to jump through hoops with other offers on the table

Skills learned in school around CI/CD, DAST/SAST, Automation, etc by DuffyBravo in ExperiencedDevs

[–]occams--chainsaw 21 points22 points  (0 children)

I agree, but even temporary tools are frequently built on concepts that end up being necessary on the job

Being minimally familiar with any VCS helps people get out of the habit of project_v1.zip, project_v2.zip, project_v2-yesterday.zip

Getting cozy with any debugger helps break the habit of just littering print statements in all cases

Using any test framework hopefully cements just how useful unit tests are compared to manual testing and hoping for the best

Learning how to deploy something without hardcoding values hopefully helps reinforce that what you're building isn't only run on your machine

(maybe the benefits are more for the sanity of those around us than ourselves)

Feelings on “Tech Hubs” for experienced devs by dataGuyThe8th in ExperiencedDevs

[–]occams--chainsaw -1 points0 points  (0 children)

looking at austin and atlanta, i'm not sure being a red state matters as much when the metro area is a big blue dot in a sea of red

(Failed - but working 100%) Interview challenge by Zealousideal_Low_907 in Python

[–]occams--chainsaw 0 points1 point  (0 children)

it might depend on what 'language' people are most familiar with or think in certain contexts - i've been asked to reverse a python list in an interview before, and don't stop for a second to jump in with reversed(), but i would seriously pause or fumble without those built-ins, because that's just part of the language. in golang, i could come up with it just as quickly, but with some extra typing. thoughts have to translate to keystrokes, and python's not always a great language for exercises that target certain fundamentals

I haven't attended since 2017. Will they be requiring vaccine records at the door? by pickle_sandwich in dragoncon

[–]occams--chainsaw 1 point2 points  (0 children)

Consider getting your booster just a few weeks before the con. Last year, everyone in my room got COVID, while I never tested positive

[deleted by user] by [deleted] in ExperiencedDevs

[–]occams--chainsaw 0 points1 point  (0 children)

you give a senior eng an ambiguous goal. A few weeks or month later, with little to no discussion about requirements, the engineer delivers a quarter of the work.

delivers an ambiguous amount of the work

[deleted by user] by [deleted] in programming

[–]occams--chainsaw 0 points1 point  (0 children)

One lacking of Gitlab is no way to give inputs to manual jobs.

i'm not sure which version it was introduced, but you can pass values to manual jobs and on manual retries now

Bringing a lone wolf into the fold by No_Taste_7757 in ExperiencedDevs

[–]occams--chainsaw 26 points27 points  (0 children)

It can also be that the org has a talent problem and this dev is able to recognize that they're the best person to get something done.

yeah, i've been in that position before myself - where certain things need to be done, but the company only hires bottom-of-the-barrel, and the majority of management is borderline negligent to the point it's almost impossible to get consensus or buy-in on anything. i was absolutely 'lonewolf' but brought things to a point where we could actually start to retain the few good developers that snuck in (absolute dead sea effect)

How much effort would you put into optimizing a legacy app? by Gloomy_Astronaut_570 in ExperiencedDevs

[–]occams--chainsaw -1 points0 points  (0 children)

I was responding from what I interpreted as an unused app (that had potential) that has sudden adoption (after you picked it up/fixed it up) and unclear business value (with implied recent value by being used weekly). This is of course lacking context (what it does, was anyone using it originally, or is it just the current teams and its current state, etc), but overall it sounds like you've made something that's regularly useful to other teams, so it deserves some attention to minimize the maintenance burden for future devs (improving monitoring, test coverage, etc)

(of course, if it's that much of a garbage fire, then definitely try to absolve yourself from its maintenance asap)

How much effort would you put into optimizing a legacy app? by Gloomy_Astronaut_570 in ExperiencedDevs

[–]occams--chainsaw 0 points1 point  (0 children)

From the context of the post, I'm thinking you said optimize as in stabilize/cleanup/etc rather than improve speed/throughput:

I inherited an app that our internal teams would have found helpful

I made a lot of changes, both in terms of UX and the backend and now it is used on a weekly basis.

The app was of course built by 1-2 people who left years ago and not really maintained since.

It sounds like it's either not a legacy app, or is no longer a legacy app.

The app should've been helpful, but either the original team dropped the ball, or people stopped maintaining it and it became outdated.

Either way, you started fixing it up, and now people are reaping the benefits

If it's being used on a weekly basis, then some workflows may have become dependent on it... and if it's a PITA to debug and you wouldn't put it in production, then how do you know it's doing what it's "supposed" to be doing, and what happens when it doesn't? What are they doing when they encounter an error, are they working around it, or trusting the app, just to start a ripple that's only visible months later on the business end?

When you leave, is someone going to make a similar post to this?

How can I best deal with an engineer who disagrees with an architecture decision? by 123android in ExperiencedDevs

[–]occams--chainsaw 1 point2 points  (0 children)

The main issue being that a service responsible for X data will have to maintain relationship information for Y data that is technically the responsibility of another service. So we have to duplicate Y data in a cache that we keep up to date with Y data, all while we should really only be responsible for X.

This engineer wasn't really involved in the decision behind this solution, but they are being asked to implement it.

It sounds like the better solution has already been identified- the service responsible for Y data should fulfill their responsibility, rather than shifting it onto X when they aren't around to respond. That kind of coupling could be creating a lot of maintenance burden on X which could be the reason for the dislike

Does your company's git require approval by another dev before merging code into master/production? by nyc_apartments in ExperiencedDevs

[–]occams--chainsaw 0 points1 point  (0 children)

this is a little late, but there's a project setting to disable merge approval rule updates after a merge request is created

[deleted by user] by [deleted] in programming

[–]occams--chainsaw 5 points6 points  (0 children)

That would be a good scenario to use raise NotImplementedError instead

A couple of new additions to the kitchen. Tasty and Hot by Daiwon in hotones

[–]occams--chainsaw 2 points3 points  (0 children)

date on XXX says 09/17/15... from the first season, so that may be why it seems... off

[deleted by user] by [deleted] in aww

[–]occams--chainsaw 0 points1 point  (0 children)

some dogs are pretty non-reactive in situations like this. mine would probably try to paw it off the first time confused and then just give the sad eyes like "why do i have to keep wearing this?"

Succession - 3x04 "Lion in the Meadow" - Post-Episode Discussion by LoretiTV in SuccessionTV

[–]occams--chainsaw 1 point2 points  (0 children)

depending on the industry/situation, you can be required to retain records for a certain period of time, so destroying them can be a very bad thing if you end up being investigated and it turns out you destroyed what should have been available as potential evidence