yebyen

42 ms·

361.
by yebyen 7y ago
Here, this is the talk where the justification and case is made for the "cap your classes at 100 lines" and other 4 rules: https://www.youtube.com/watch?v=npOGOmkxuio
362.
by yebyen 7y ago
After spending some time to think about your reply, and watching an OO talk or two, I have a clearer way to state why your statement is unlikely to be true in context. I am not an OO "seer" or visionary, I don't mean to say
363.
by yebyen 7y ago
I'd love to accommodate you, but I'm still struggling to get my team of 8 to agree that we should impose any line length limit. My terminal is 180 characters wide because I have some team members that don't seem to believe
364.
by yebyen 7y ago
Your use of the word "every" makes me believe that I have not made my point clearly. I will try to restate it in less than 5 lines so that it can be understood better. ( Zing! ) I'm not saying that your code is wrong, (but I
365.
by yebyen 7y ago
I'm not saying that this rule is the most beautiful rule, or that you're a bad person if you write methods that are longer than 5 lines and don't get permission from a senior architect first. That's something dysfunctio
366.
by yebyen 7y ago
I will say also that I have >15 years of experience programming in different languages and I've only felt a need to reach for these design concepts in the last 2. Please don't feel like I'm talking down to you. We are the
367.
by yebyen 7y ago
I'm actually not arguing to change the default, I'm arguing that the team should have a conversation and decide on whether the default is reasonable for them. I'm not using a narrow width font because I want to pack more inf
368.
by yebyen 7y ago
Is it a method that's longer than 5 lines, or is it a method that is longer than 50? Because one of these things I could see being easily explained away without haranguing, but the other one is what I deal with on my team on a regular
369.
by yebyen 7y ago
I would ask if you're doing Ruby, or object oriented design? Because the first rule of SOLID is Single-Responsibility, and there is this great concept frequently repeated in the OO design circles of Ruby conference talks, "I just
370.
by yebyen 7y ago
That's fine, when it is more readable... but there is a convention in Ruby of making your classes and method names as descriptively as possible, not even ruling out the possibility that they might be very nearly full sentences. I am in
371.
by yebyen 7y ago
The thing about that is, what's reasonable for you and your team is not always reasonable for me and my team. Case and point, 80 character line limit: this was a reasonable limit when command lines were not usually rendered inside of h
372.
by yebyen 7y ago
I will say that as a Ruby on Rails dev, where many things have changed over time, there are quite a lot of highly voted StackOverflow posts where they go into detail about what the answer is on the date of posting, then someone comments &qu
373.
by yebyen 7y ago
It's also called the law of "Uphill Analysis, Downhill Invention" which states "It is much more difficult to guess the internal structure of an entity just by observing its behavior than it is to actually create the stru
374.
by yebyen 7y ago
Someone explained to me once that they had a friend who always cancels on them, or vice versa and they always cancel on them. And it was an open secret between the two of them that they both strongly hate going out, like serious dread fee
375.
by yebyen 7y ago
It is the truth that you are not required to disclose any information about medical situations of your own or your family, or any related to familial status, including even the fact that those issues exist or are medical in nature. How else
376.
by yebyen 7y ago
I don't know that he needs to make a point, can't he just publish a guide about his own setup like 1000s of others do? As for why it's notable and on the front page, if you don't know who Alex Ellis is, I strongly sugges
377.
by yebyen 7y ago
Thank you! I assume there are requirements to fulfill for the other distros which support it as well but they are probably not as well documented. One thing which RedHat has always impressed me with is the quality of their documentation.
378.
by yebyen 7y ago
I said RHAT family, but honestly I did not mean to include Fedora. I've been upgrading my Fedora Core desktop since probably 26, it's not the machine that gets the most use, but it works at least as well through upgrades as the Ub
379.
by yebyen 7y ago
I'm not sure that migrating to systemd is as hard as you think, I've done it on my Debian release train, and I've also done it with Ubuntu, after migrating from Sys-V to Upstart, no less even... It's actually standard po
380.
by yebyen 7y ago
I will concede, Fedora has as good a reputation and it's what I run on my desktop at home! Good point.
381.
by yebyen 7y ago
Honestly, yes. I let my brain interpret the headline, "shares Max problem" and this is exactly what I thought it meant, before I clicked through. As a non-aviation technologist, I initially thought it would be more surprising if t
382.
by yebyen 7y ago
This is generally one of the philosophical differences I see between the RHAT family of distributions and some others (those that I personally favor), that seamless upgrades are generally not well supported from each major version to next.
383.
by yebyen 7y ago
The other way to read it, I guess, is that you can correctly anticipate those unknowns. The canonical way I hear is to add 1/3 to your estimates.
384.
by yebyen 7y ago
I hope so! Please drop by our Team Hephy Slack if there are any gaps or if you need help.
385.
by yebyen 7y ago
I think this is really hard, it's a bit like how we talk about learning Rails in the Ruby community. "Don't do it" Not because it's bad or especially hard, but because there's so much to unpack, and it's
386.
by yebyen 7y ago
I think this is best explained without exaggeration by the famous Design-Stamina Hypothesis[1], which states the notion that time spent on Design is something which you can trade away to improve development speed, is reliably false in the l
387.
by yebyen 7y ago
> there's a minimum scale for running your own Kubernetes setup I would say there is a minimum scale that makes sense, for control plane ownership, yes. Barring other strong reasons that you might opt to own and manage your own cont
388.
by yebyen 7y ago
Yes, absolutely. But to hear it explained that way, it just seems like wishful thinking based on a circular reasoning, that invites an invocation of the rule... "We spend too much on our developer staff, so in the future we have adopte
389.
by yebyen 7y ago
Or, that there is a minimum scale/experience gradient behind which you are better served by a decent managed Kubernetes, when you're not prepared to manage it yourself. Most cloud providers have done a fairly good job to make it
390.
by yebyen 7y ago
So, assuming that Kubernetes was installed using kubeadm, this was the document you needed to find: https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/... Moreover, if you are keeping pace with

More ›