Hacker Newsnew | past | comments | ask | show | jobs | submit | skierguy's commentslogin

I think a lot of the "religious" feeling I get from FP advocates is the constant focus on purity and the "No, you AREN'T DOING IT RIGHT!!!" kinds of tantrums. You HAVE to understand the nuance. You HAVE to participate in these strange little paradigms that esoteric thinkers have come up with. Ultimately, I think of FP languages like Haskell as playgrounds to pilot bleeding-edge ideas before the best ideas get incorporated into languages that are widely used in production.

Ultimately, some real-world processes are just procedural, and procedural languages are easier to apply to them. When it comes to callbacks, mapping functions to a list, etc., it's pretty clear to me that FP paradigms are superior.

In other words, I think it's part fad/religion, but as with anything, you can learn from it and take the good parts.


Most languages have already taken the good parts. We barely even consider them a "FP thing" anymore. Callbacks and map() are just things you can do in most languages.

What remains when people advocate for more FP is the more esoteric stuff. (And non-nullability, which inexplicably gets associated with FP surprisingly often despite being orthogonal to everything else in the paradigm.)


Problem is, it's hard to distinguish the chaff from the wheat. A lot of practices that advertised themselves as "the way of the future" and most of them faded into nothingness.

At some point people try to save time and stick with practices that stand the test of time.


It's much more complicated at scale. Many conflicts can come from things like backporting or working on a feature in a codebase that deals with a lot of churn (like some drivers or the Linux kernel). Some open source projects have internal versions of the code within the company that eventually gets upstreamed after internal validation takes place, but that version of the code may not rebase for a while for some very good reasons (unresolved instability on the main branch, for instance). In that case, the code base is now both significantly ahead (with internal changes) and significantly behind (due to the other changes that have come from other massive organizations working on the same project). I have published on the topic of merge conflicts a couple times, and even I didn't understand how inevitable massive merge conflicts can be until I joined a kernel integration team at a large company.

Open source is a helluva drug :)


Everyone at the top of our class in undergrad were the people who got internships early. I went from being the confused guy who still had decent grades to being one of the people who could go above and beyond. Debugging is weirdly under-taught in school


Practical experience is such a good teacher. I've been doing LeetCode problems lately, and (re-)learning about things like trees is so much faster when you see and play with code rather than taking notes while a prof explains everything algebraically on a whiteboard.


I have my masters in computer science and work on the Linux kernel at a company you know for a product that you know. I often miss the point of leetcode questions and lose points because I don't use some certain tricky thing that they specifically want me to study for before the interview. I personally think it's just a handy way to build ageism into the interview process, because it's all this academic-style stuff that I've used maybe twice since I graduated 5 years ago. And for people like you, you've probably only really heard about these things in passing because they're not part of most people's workflow.

Kind of like applying for a job restoring Native American artifacts and being asked tricky questions about artifacts discovered in Egypt 5 years ago. Sure, you might have noticed the story or even read a lot about it 5 years ago, but it's not going to be a part of your daily work. Different procedures, different materials, and different local laws? I guess you should get studying if you want this job! And really, I just wanted to see your problem solving style when I ask irrelevant questions!

But ya, I think it's fair to say that my degree helps me not take that sort of thing as a rejection of my intelligence or qualifications though. I don't feel lesser than. I just feel belittled by someone who doesn't put effort into their interviews, which is useful information if you're considering working with them.


I have trouble with leet code problems because I'm 100% used to teasing requirements out of real people, whereas leet code has a skill of exactly reading and understanding the exact implementation requirement the question is asking. That and well real debugging tools in real life versus the sometimes broken web versions (I spent 45 minutes on an 'friendly' interview debugging the debugger in an online testing system which was truncating output and having threading issues).

Which is funny because I was prepping my Daughter for leet code for interviews, she only practiced leet code all summer despite me pushing her to do some open source or pet projects (aka real code). She's much better at LC than me despite barely being able to code in real life. What's really funny is that she got completely owned when I and some friends asked her the same leet code questions verbally but leaving ambiguity in and not specifically calling out all edge cases. We did about 10 practice verbal questions before she actually interviewed so she got better at it... and then she got asked one leet code question read off of the site.

It's fun watching how fast she picks things up esp with the ability to ask me and her mentors questions. She calls that "powerleveling"


I mean, it's literally called l33tcode... It's really a handy way of building l33t d00dz culture into Big Tech firms. Gatekeeping at its finest.


I see it more as a sign of reviewing incompetence. Or perhaps lazyness, or wanting to haze the incoming devs the same way they were? Either way you slice it though, it's unrelated to the actual job we do and should be done away with.


A more boring answer is probably risk management. You don't want to be the radical that introduced a new innovative interview process and produced false positives for your company.

It's like how everybody knows IBM sucks but nobody gets fired for choosing IBM (TM)

If you want change, it has to start at the top of the management


One has to admit, there's also a certain elegance to the l33tcode thing. It's all about easy-to-survey "code katas" taken to an extreme level, which is pretty much what you'd want if your problem was to cheaply select the most likely capable 1% or so out of some huge amount of applicants. But most real-world code problems look nothing like those clean whiteboard examples.


> I personally think it's just a handy way to build ageism into the interview process, because it's all this academic-style stuff that I've used maybe twice since I graduated 5 years ago.

I'd argue it's time-ist in that it works against those who don't have time to prepare for a leetcode interview. Candidates of any age can grind leetcode, but I concede college students have more time on their hands, compared to someone with 3 kids and a demanding job.

IMO, interviewing at big tech is like the Spelling Bee competition; asking people to spell 4 or 5 letter words is hardly a filter; so you start giving increasingly longer and unusual words and it becomes a feedback loop with kids have to getting coaches and spending an inordinate amount of time studying, which raises the bar further. The end result is only those who invest a lot of time can get anywhere (and sometimes still fail), and those who don't prepare barely get off the ground unless they are geniuses.


Leetcode-style interviews seem to be somewhere between "what year did you take your last algorithms course?" and "have you seen this problem before?"


I think the issue is that you're not taught how to interview people. So usually you'll notice that you need to do an interview in a few hours and scramble to think of what to ask and leetcode is the easiest thing that comes to mind.


Same. As an American, I would be much less likely to use or spread good word about a product that centered around the act of "tooting". Our culture sees the word as silly, childish, and a bit gross. I could get used to it eventually, but if it's the first thing I see about the product, I'm probably going to find something else to use that doesn't make me think of farting or introduce fart terminology into my everyday word choice.


Being a native English speaker from another country I don't possess this association at all, and have to dig quite deep to remember that Americans do.

I do get tootsuite => toute de suite i.e. a sense of immediacy, the present moment, with greater impact for being a bilingual pun. Along with that, the onomatopoeic elephant.

Cynical take: notwithstanding the denial in the PR, that original author knew the scatological allusion, and that it has parochial scope, i.e. they actively intended to annoy Americans, and in particular those with a prim streak.


As a very young child & native American English speaker, I was told the rhyme,

Beans, beans, the magical fruit, the more you eat, the more you toot.

That cemented the association with farts, but 'toot' as in 'toot your own horn' (idiom for self-promotion), or even just literally tooting a horn, are also strong associations. So it's not exclusively, or primarily, a word for farts to my ears – but that's one of the top few potential meanings.


Note, this is botanically incorrect. Leguminous plants, as compared to angiosperms generally (and most starkly when compared to those with pericarpal fruits), may have differential edibility: that is, beans are not the fruit; the seed pod is the fruit (i.e. the mature ovary of the flower), and beans are an edible seed contained within the pod. Some legumes with edible pods (notably phaseolus vulgaris, the "green bean" or haricot verts) are known as beans in the culinary vernacular, but this is solely by common name, and does not hold up to anatomical scrutiny.

Regular correspondents to this forum may also encounter Java beans, but be warned that their palatability is disputed, and ungoverned use, particularly in their enterprise form, can lead to buildup of toxic and irrevocable technical debt.


Beans, beans, they're good for your heart. The more you eat them the more you fart.


Yes, this is the rhyme I learned as a kid, warning against the gastrointestinal consequences of oligosaccharide consumption but extolling the cardioprotective nutrients they accompany.

The GP form I have never encountered before, and by my assessment falls short in pedagogical qualities.


I'm pretty sure that's supposed to be musical fruit.

That's why they make you toot.


It’s apparently a variant. I realized that the “magical” version was much more common than I’d expected a couple of years ago and did some informal research. It seems about evenly split, and I didn’t see any regional correlation.


I'm not surprised. That's why there are qualifiers.

It's not intended as smack talk asserting "My variation is better than yours!" (Throws down gloves.)

Sometimes, it's nigh impossible to readily come up with the wording that captures the myriad thoughts flitting about my mind and account for all possible social bits and potential misinterpretations. And I comment anyway, knowing it's likely to go sideways cuz hoomans.


The "musical" form seems more refined, bringing poetry to a variant that is otherwise botanically problematic and nutritionally attenuated.


I'm having trouble deciding if you are tugging everyone's leg or being straight up serious or tugging everyone's leg by being straight up serious.

Sometimes that last is funnier, though usually only to the person doing it.


Well, the entire discussion deriving from the proposed code change is ultimately debating the relative merits of a fart joke, so any contribution is bound to be a gas.


... and by virtue of the contribution being a gas, it expands to fill the entire containing volume - in this case, the discussion we’re having.

That makes total sense.


As a Canadian "musical fruit" still makes you fart. It is some nice potty humour.


I am not a native English speaker, even if I am flattered that nowadays you can't tell


Yes. If you wanted to be charitable, the other connotation is tooting your own horn, which isn't that great either. Bragging is better than farts, though.


Yes, yes, yes. My advisor would have laughed me out of the room if I brought this narrative to her.


Because the study pushes the narrative that correlation is causation, and that's just not true. The data is interesting, but the spin is irresponsible. Many people with mental health issues feel a stigma to seeing therapists and reach for something to numb the pain.

Plus, just because something has percieved negative effects on life outcome doesn't mean we outlaw it. For example, alcohol, prescription meds, having children before completing your education, the lottery, cigarettes, etc.


Hm, good points. But maybe we should at least raise the minimum age ? ( I feel the same about minimum age of gun ownership ... don’t ban guns but raise the age ... how many school shootings are committed by 25 year olds? I digress)


I’d much rather use THC/CBD than benzos. Look ‘em up and the withdrawal symptoms for each.


There's a performance mode that Google has a support article for. Google exactly "Change your Chromebook’s performance setting", and you should see it.

If lscpu still shows some offline cpus (let's say cpu 1 and 3 are offline), echo 1 >> /sys/devices/system/cpu/cpu<1 or 3>/online. Run lscpu again, and you should see all CPUs online and 2 threads per core.


I was with you until that last line. Maybe it's because I never saw IBM in its prime or because I only happen to hear about IBM when there's a ton of media spin on a product that never shows up as anything more than a gimmick (IBM has 5nm chips in 2017!!! Look at Watson!). I just don't find laughing at IBM to be that far-fetched of a concept.


Aaaaand the EULA and menu buttons are in Italian when I download from the en-us version of the site. I knew there would be 90 languages, but I didn't know I'd need to learn all of them to use Edge!


It was french for me. German for a coworker. The language settings are all screwed up.


Just strip the query part of the URL. I guess the submitter of the blog post is an Italian.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: