2,220 karma · joined October 30, 2018
edit: Also, I challenge the notion that the reason was legitimate. I know the reason. But I wouldn't make that trade-off.
Interest in Japan is higher than average among the software developer crowd. My wife teaches Japanese and her biggest clientele demographic is single, male engineers in their 20s.
"Architecture is that which contains entropy."
One will filter you out for having too many keywords. One will filter you out for not having enough keywords. One will filter you out for including a picture. One will filter you out for not including a picture. One will ... ad infinitum
Your resume is being evaluated by different filters constantly. Different filters filter different things. There is no "right" answer. There are only answers you will or won't be filtered out for depending on which filter is being applied.
Which filter is being applied?
It's random.
Hiring is essentially random.
Yeaaaah no. I've seen people nope out of a job within anywhere between 30 mins to a couple of months. I've also seen people that knew it wasn't right for them stay 1 to 2 years.
I always find it funny when I drive by that and I see the sign MIT.
It _is_ a particular type of wrapper object. That's where the whole "in the category of endofunctors" comes in. An endofunctor being a functor from something to itself.
You have IEnumberable<SomeObject> and that lets you do SelectMany to flatmap some internal nested set of objects down to IEnumerable<SomeOtherObject>.
The shape of what you get back doesn't change. You get back an IEnumerable of something. That has a specific contract on which you can do specific operations regardless of the object it is wrapping.
The other piece of the puzzle is that it is monoidal. A monoid is just a collection of objects + a way of combining them + a 'no-op'. This is usually worded something like "a set of objects with an associative binary operator and an identity".
The classic definition "a monad is just a monoid in the category of endofunctors" is worth picking apart piece by piece. But it's also utterly useless because you have to spend quite awhile picking it apart and then looking at concretions of every one of the individual abstractions to understand what the hell each part individually looks like and then put it back together in your mind.
That definition is classically used as a joke because it's so terse you have no hope of understanding it without a lot of study, yet at the same time it's so precise it's all the information you need!
I'm deeply interested in these topics, but I'm not so good at them. I have gotten much further than I ever would because of efforts like these.
Thanks for being you.
Human factors always mess up software... _sigh_
Too much vs. not enough are just different sets of problems.
Too much = you risk no one on the team being able to troubleshoot when things go wrong because no one has ever had to run through the process themselves before so no one understands it.
Too little = a non-trivial percentage of your bandwidth is eaten up by trivial things you keep doing over and over again that are in the vain of servicing requests rather than solving problems.
In practice I find I'd rather have the first problem and I can think of solutions to it's problems that I'm happy enough with.
The point is the static analysis tool fails the build, so it becomes physically impossible for the godzilla method to exist. I trust the machine to produce a predictable result. People are a huge source of entropy and having a little bit of automation to help contain some of that entropy I think is a very wise use of technology in CONJUCTION with promoting a culture of caring about quality and diligent review.
It's hard to imagine how anyone ever lets godzilla methods and god objects and all other kinds of code smells become a thing... and yet... they're a real phenomenon that seem to make their way into large code bases at some point or other.
I find a lot of phrases like "I'm not convinced that..." soften things in just the right way that people get a lot less defensive or aggressive.
I have several mental models for this.
The first goes "most people are wrong about most things". You have to include yourself in that one or it just sounds arrogant, but it's true. Mostly we have a toy understanding of how anything really works if we are asked to scratch any deeper than the surface and the sheer amount of mental models required to begin to somewhat accurately map to reality vs. the search cost of finding those abstractions vs. the probability any individual is sufficiently motivated to pay the search cost. It's abysmal. So basically no one has truly good ideas. Yet some how the whole thing still grinds along.
You get what you incent. That would be another key model. Behavior follows incentives. Period.
Conflict of interest. That's another thing to watch out for. Loosely related to the idea of "subtext". People will say one thing but often mean the exact opposite of what they say. For example when someone says "I believe it is" this is a contradiction. The sheer timidity of the statement actually indicates that they harbor a hint of doubt. The subtext says "I acknowledge there is a possibility that it might not be and I cannot be 100% sure".
Power of ideas vs. Power of people. These are the fundamental two types of company culture that exist. If you're a thinker, you will be eternally frustrated in a power of people culture.
I'm probably rambling now, but there are a good many "human factors" that make companies awfully questionable at times.