yebyen

57 ms·

511.
by yebyen 8y ago
You're right, I can tell you as a broke college kid I never thought of any of that, but I sure should have...
512.
by yebyen 8y ago
Haven't you ever been a broke college grad looking for 3 months with no luck? I'm not exactly on the market right now, but there was a time when I'd take any offer, and making a principled stand over something like NDA/
513.
by yebyen 8y ago
And if you don't have another job lined up yet? Just hold out?
514.
by yebyen 8y ago
In Debian unstable, many of the packages are submitted from upstreams (eg. the folks that made the software.) The bar is simply "Debian developer" uploads the package, as I understand it. The Debian developer may or may not be t
515.
by yebyen 8y ago
> Debian/sid has its freeze phase Correct me if I'm wrong (I don't think this would have changed), but Debian/testing has a freeze phase, and what you say is true about testing. I don't recommend Debian/test
516.
by yebyen 8y ago
I misread the issue is about the Lock screen and not the login screen, my mistake. That's a bummer! But you're saying they've fixed it, woohoo? The phenomenon of the "current Linux distro" is an interesting one,
517.
by yebyen 8y ago
> Highly customizable, especially the desktop interface The freedom to choose MATE, which doesn't solve this issue for you, is included in that statement. But this "Highly customizable" vs "uniform experience" o
518.
by yebyen 8y ago
Thanks for answering. That is clear, and it makes sense.
519.
by yebyen 8y ago
Thanks for explaining it clearly. I hate to ask for more, but it's a rare opportunity that my question about capital gains is not completely off-topic. Can you (or anyone) tell in a similar idea about how Capital gains losses work? I
520.
by yebyen 8y ago
So are they marginal, or based on brackets? Cause it sounds like they're bracket-driven, if the entire gain was taxed at 23.8%. What part am I not understanding? Is the idea that capital gains tax itself is marginal, but if your othe
521.
by yebyen 8y ago
> artificial restriction One man's artificial restriction is another man's invariant. "We can't rename this thing without renaming it everywhere" is a thing, but honestly not in this case, because we're tal
522.
by yebyen 8y ago
Ain't that the truth, but he said so at least the once, and now I guess that's how we remember him!
523.
by yebyen 8y ago
I don't buy this argument. This is syntactically valid ruby, current state: tuple.collect{ |x,y,z| [x * 3, y * 3] } and so is this: tuple.collect{ |y,z| [x * 3, y * 3, z * 3] } The last one will generate a runtime error (unless "x
524.
by yebyen 8y ago
Deis Workflow (now Hephy) used them too! We still use them, and it's a great resource for projects in the same vein. Although there are some issues with buildpacks in production, they are a great set of training wheels. I'm exci
525.
by yebyen 8y ago
I'm sorry, but there's a great deal of literature in support of this idea that naming things /well/ is one of the harder problems of programming. If you're arguing that "fst" and "snd" are better
526.
by yebyen 8y ago
Those are all scary indeed. Ways you can cut your hand off. Has a nice ring to it, sounds like something to worry about more than "ways you can write unreadable garbage code that not even the author can still parse for themselves in
527.
by yebyen 8y ago
You can keep your opinion, I don't need to spend any more time trying to convince you, but to be pedantic one last time, you omitted the part of that snippet that would have made it clear the named parameter is not needed and unnecessa
528.
by yebyen 8y ago
{} is for one-liner blocks, stylistically speaking. I occasionally use it for a longer block without refactoring it into a method (and line-breaks are permitted for sure), but typically if the one-liner is above a single line's worth
529.
by yebyen 8y ago
> I, however, can still read that code perfectly fine and well because it has variable names. Not @1 and @2 for hashes, etc. If I do {@1 + @2} exactly once is that really harder to read than {|x, y| x + y}? If I'm doing it everywher
530.
by yebyen 8y ago
> Maybe you might, but plenty of other people will not. I have also lied to myself and added "TODO" comments in some small projects I've worked on. So it was cheaper to leave the TODOs in the perfectly OK code, sounds like
531.
by yebyen 8y ago
You know, naming things is hard, and it's not reasonable to argue that your code should always be in the optimal state. There are "on the way" states, and it seems like this feature can be used well by saving you from choosi
532.
by yebyen 8y ago
I was looking for the Steve Jobs quote in this thread, thought this was going to be "It doesn't make sense to hire smart people and tell them what to do; we hire smart people so they can tell us what to do."
533.
by yebyen 8y ago
If you read the book you would not call it advertising material. It's very open-minded and it's honestly not a book that is designed to sell you on Pivotal PAS in any direct way. The first line in the first chapter is more like a
534.
by yebyen 8y ago
I agree, but it's fun and sometimes enlightening to let the debate be framed this way Compare[1] Chapter 1: > “Nobody has ever built cloud-native apps without a platform. They either build one themselves or they use Cloud Foundry.”
535.
by yebyen 8y ago
That's common in Rails too. Except I don't think it's necessary to make it a go-between. Where controllers have simple interactions with models (which represent database structures, and may have logic in them) you let the co
536.
by yebyen 8y ago
I think the payoff is for merging unrelated histories, that you can then rebase one history on the other, and present a new unified history. Is the really only reason why people do this, so that you can rewrite your initial working commit i
537.
by yebyen 8y ago
You can also use the 'magic empty tree object' to make your repo more amenable to joining disparate histories of other trees. It requires both the source and destination repo to abide by this practice, but I do this on all of my
538.
by yebyen 8y ago
Yes. Literally ten minutes before Amazon announced their Lambda support for Ruby at this year's re:Invent conference, one of our lead architects who was watching the livestream sent out (and I quote) > I guess if you want to know w
539.
by yebyen 8y ago
Can you share a link about what you mean by this? I went searching but came up pretty empty ... do you literally mean adding an "app/services" directory, is that all? Where you put classes related to external dependencies th
540.
by yebyen 8y ago
I've just skimmed the TOC and, having never seen this book before, I'm a little in love. Here's why It's a cynical UNIX manual from the 1990's. Here: > 14 NFS..............283 > Nightmare File System > Not

More ›