Yokohiii

21 ms·

421.
by Yokohiii 8y ago
Dan, please add author names to the suggested books!
422.
by Yokohiii 8y ago
I don't say you should never use "customers" over "list", but the latter is often good enough. List is a good fit for a compact method which is doing something generic on a list or the context clearly specifies what
423.
by Yokohiii 8y ago
Of course, but the scope is heavily limited. This doesn't justify nonsense naming, but it can be very compact.
424.
by Yokohiii 8y ago
Oh wow I totally ended up reading the 30m line problem story. I actually was confused about the title on HN.
425.
by Yokohiii 8y ago
Embedding types in the method names is a habit of using dynamically typed languages. If the method is private it can be shorter, if it is public it should be a bit more descriptive. With statically typed languages I'd agree with your s
426.
by Yokohiii 8y ago
I actually like using short variable names. Using "i" as an index variable has been widely accepted. It saves a lot of typing, the use case is clear and it is usually tied the a block which is visually identifiable. I carry over t
427.
by Yokohiii 8y ago
An almost 2h talk which is very worth it for everyone who has an interest in minimalism, simplicity, performance or anyone who has a feeling there is something wrong in software. Casey's complaint is basicly that there are several mill
428.
by Yokohiii 8y ago
The reasons for this isn't your privacy. But still it can match you as a person even if your other data is defect or incomplete. A good primary key.
429.
by Yokohiii 8y ago
Don't let the dark side blind you. Managing data is complex. ORMs add more complexity and they make data look easy. IMHO the biggest deal with most ORMs is that the satisfy the programming platform and coders aesthetics.
430.
by Yokohiii 8y ago
There is an worldwide AI hyteria ongoing. Google wants to monopolize and governments will be big customers.
431.
by Yokohiii 8y ago
They couldn't find out why I am procrastinating. We are on par.
432.
by Yokohiii 8y ago
This has so much bigotry.
433.
by Yokohiii 8y ago
Productivity isn't just doing things at all. It also implies to distribute your efforts on various tasks. Some tasks are less interesting then others and you can get lost on the ones you like. You can feel productive for streaks but af
434.
by Yokohiii 8y ago
SEO is still an unsolved problem, imho. Has anyone experience with this? We run a ecom business with millions of products, fast responses in time are necessary for us. I certainly like the idea of PWAs much more then fragmented native mobi
435.
by Yokohiii 9y ago
It is not a mistake, it is an error.
436.
by Yokohiii 9y ago
Fair point. Should have said last century star trek.
437.
by Yokohiii 9y ago
What you describe is opportunism. Watch star trek for a positive take on our future. If you watched the Q&A at the end you will know that this is just Stross' way to tell stories and he is interested in a better future. But it is o
438.
by Yokohiii 9y ago
> Reduce Operational Complexity If I hook everything into slack I have a simple interface that can cover and reflect all my needs!
439.
by Yokohiii 9y ago
That is beyond crazy. If I have more than 2h meetings a day my work is practically done. Bad meetings usually create internal discussions and dissipate discipline. Cost of bad meetings multiplies negatively.
440.
by Yokohiii 9y ago
Of course there has to be a balance between the task at hand and decision making effort. People have to be good at it and that is a management concern.
441.
by Yokohiii 9y ago
Exactly this, small but important details can disappear.
442.
by Yokohiii 9y ago
Well it sounds nice but I feel there are some parts left in the dark. Working this way seems to be over reliant on a single manager. The world is now smart enough to know that we are continually misled by biases, focusing on a single person
443.
by Yokohiii 9y ago
Wouldn't it make more sense to optinally add all dependencies?
444.
by Yokohiii 9y ago
That sounds quite chaotic and impossible to keep stable. I wonder who was responsible to find problems and fix the master after messing up?
445.
by Yokohiii 9y ago
Completely agree. Rebase is practically only safe on single developer feature branches which haven't been merged or completely isolated repos that produces patches only. Keeping track of all requirements in the former is hard, especial
446.
by Yokohiii 9y ago
When in doubt either: * commit to an itermediate branch as storage * git stash && git stash apply (repeat last to recover stuff)
447.
by Yokohiii 9y ago
The site should clearly differ between local changes and pushed changes. Latter usually requires different strategies to recover, depending on repo policies. Git golden rule: Never push -f if you don't know what you are doing.
448.
by Yokohiii 9y ago
Where I live, ISPs do distribute those devices.
449.
by Yokohiii 9y ago
Interesting viewpoint. But I am concerned that my mental capabilities can contain every brainfart that a misguided but smart person has.
450.
by Yokohiii 9y ago
left: optimist right: sceptic middle: opportunist Having shitty paradigm is certainly better than having none at all. But at some point we have to evolve.

More ›