Yes they are?
If it's not referenced it, it's not needed. That's pretty straight forward?
2,220 karma · joined October 30, 2018
Yes they are?
If it's not referenced it, it's not needed. That's pretty straight forward?
Re: your comment about "And of course I have seen adverse effects from it (eg. your linked article complains of innumerable, non-sensical interfaces) but that is mostly due to inexperienced developers that don't get it"
While this is true, there is a deeper implication here. Assume programming talent is normally distributed. Now, ask yourself above what percentile do you have to be in that distribution to truly grasp the how/why of SOLID and to be able to wield it to solve problems. Now, ask yourself what percentile do you have to be below where you just go crazy with creating non-sensical interfaces and thousands of awfully named classes with single responsibilities such as "CustomerCommandMapEmbelisherConverter"?
The real problem is that code bases tend to be horrible (also normally distributed!) because a lot of talent doesn't meet the bar and can't actually produce programs that aren't rubbish. In any org you'll find the quality of the code base is somewhere on a normal distribution. And you will find all the engineers somewhere on a normal distribution. You'll have a couple of brilliant people, a couple of horrible people, a lot of average people.
The only time you truly see exceptional code bases that everyone stops and goes "wow, this is nice!" are the rare times the stars aligned.
So far the answer I've worked out is:
Because its optimal solution to let talent flow through BigCo in SV. There is no domain or tech-stack specific stuff. So studying for the interview process allows the applicant to apply for multiple companies. At the same time it's a pretty hardcore process, so the company knows they are getting engineering talent that is a) smart and b) obedient.
For the rest of the world it absolutely doesn't make sense and that's why where I live, you don't see that style of interviews at all.
Different industries, different problems, different solutions = different definitions of what an MVP will and can be.
Most of this entire discussion is useless.
I'm not 100% on SaaS. Need something more fine-tuned. Call it SaaSGile.
On the current code base I work on I swear every single one of my pull requests contains large amounts of variable and method renaming to make it easier for the next person because if it takes me half a day to compute an understanding of what "var result = apiTotal - total" is actually doing then it isn't named nearly clearly enough.
He was saying people tend to fall into the trap of thinking that in a million years none of this is going to matter and that they're just one of seven billion people, so they don't really matter etc. Then he said now imagine your 6 year old daughter gets cancer... what do you tell her? That in a million years it isn't going to matter? That she's only 1 of seven billion people, so who cares? And if it's not the answer at a time like that then it's probably not the answer.
I dunno... but it struck a chord with me and I've not been able to entertain the nihilistic perspective ever since. Now whenever I find those thoughts coming on and think why on earth do I push so hard or why do I bother with what I do etc... I take on a more cosmic perspective. That through our actions and experiences the universe is able to observe, enjoy and comprehend itself. The point is to be the matter and the energy. The point is to be the experience.
Like why do you sit down and watch a movie when you know it's going to end?
Yes. Please. Stop. Doing. That.
Turns out they actually do do all of the things you suggest, but that's not how they perceive themselves to be, so 'they don't do that'.
True story - I worked on implementing a billing system for a Japanese utility company and when our team asked for the requirements around how to handling dunning when people don't pay their bills the response we got back was "Japanese people always pay their bills."
I shit you not.
But here's the kicker... in software engineering average means bad. Because average code is not good code, because only amazing code is good code. So all these questions and tests trying to figure out who's a good engineer are kind of rubbish. Mostly they will be average engineers. But companies seem to think "we only hire the best" all the meanwhile the trash-fire slowly burns.
I like the people I work with to have a good sense of humor.
This. So much this. I didn't realise that until a little while ago but when I did it made me realise I need to understand actually what make someone a senior. It's not just an automatic progression.
A Monad is just a Monoid in the Category of Endofunctors.
I don't really get the need for the files panel on the left hand side. In theory the first page just acts as an ad-hoc version of that. Seems unnecessary to me. I could look past that though as if you just hide it and pretend it's not there then it doesn't really matter.
Also... no mobile app :/
I use workflowy every day and there are definitely areas for it to improve on that I feel like dynalist is trying to address. Will keep an eye on this one. Not ready to switch at this time but hopeful for the future.