Isn't it just that you can define monadic interfaces for lists, as you can with (probably all) parametric data types?
Saying "the list monad" wouldn't be correct, right? Although it's pretty common to see that phrase.
1,004 karma · joined November 21, 2016
Isn't it just that you can define monadic interfaces for lists, as you can with (probably all) parametric data types?
Saying "the list monad" wouldn't be correct, right? Although it's pretty common to see that phrase.
So, yeah, I'd say maintaining fake identities is hard no matter what and illegal.
But I think even before that folks are wondering how people can maintain several jobs at the same time, regardless of fake identity or not.
If you write that you clearly think it's problematic but hide it behind an unnatural question. Then either I do what you hint at or you will push / discuss until I agree. I am not the determiner. It sounds like you are schooling me with an awkward back and forth.
Honestly, to me this is beating around the bush and doesn't actually make me confident we can have a real discussion (in the context of that code review).
"Do you perhaps think that doing this <tylically discouraged coding practice> is problematic?" sounds like either you want to passively insult me, or you don't consider me a peer with whom to have an actual discussion on equal footing, or you don't have the guts to share your opinion without contortions.
Could you elaborate?
Not a frontend guy but my understanding was that the virtual DOM is what's necessary to enable a simplified model where you can code as if your entire view was rerendered from scratch when there's a change.
Mutating the DOM only where and when you need to in a handcrafted fashion is always going to be faster, it's just not scalable, I guess.
So, in that context the virtual DOM is not really a scam. Not sure in what sense it is? Was it claimed to be performing better than it does?
However, in a project there is a bunch of stuff you need to do that's mainly specific to product management. Tracking the feedback, talking to users, coordination with other product teams, covering the nontechnical pieces, etc. Every stakeholder does their thing. The PM in most cases doesn't code, a legal or compliance stakeholder doesn't try to talk to users or come up with product feature roadmaps, the engineers don't create the artwork etc.
The shittiest experience is when you work on a product with a formal PM but you wonder what it even is they are doing, not engaging in shaping the details just signing off, not talking to stakeholders, etc. and you, the engineer, has to fill in. Buuut you also cannot just do whatever because the PM exists and needs to be consulted.
Google used to have a way to ask for searches via SMS a while ago: https://www.youtube.com/watch?v=J937N9m-XtE
But "tunneling" to me implies some transparent layer allowing you to browse Wikipedia via the same way of interaction.
There's one set of rules. You don't need to read my own personal rules on some dedicated page before you are entitled to reply to this comment.
However, in some cases you want to enact a specific locking order on some objects that interact, and in particular if locks aren't reentrant, I'd be cautious and at least use a cryptographic hash here to reduce likelihood if collisions.
As far as I understand (from the wikipedia article) the Hoskins effect (also) applies if you simply got infected once. It's not something specific to the vaccine.
Claiming the "vaccine causes a fundamental change" is a bit misleading. The vaccine OR infective exposure have the described effect, which is normal! And altering the immune system to prepare it for future infections is the point of any vaccine, isn't it?
Now, one might say that it's not good to vaccinate everyone so that there remains a population that can get freshly infected with new variants and build up immunity fresh. But they'd then be altering their immune system by the response to that as well, if they don't die from the infection.
I've worked with a bunch of PMs on technical products, APIs, etc. and I've rarely met anyone discussing that level of detail or willing or able to make such a decision.
The engineers chose a way that worked and it's likely the best way supported at the time, given the other comments I've read here on HN.
House prices in attractive areas (in and around Tokyo) have increased drastically over the last few years.
Meanwhile, houses in the countryside are on the market for almost (and often literally) nothing.
I guess the question is what the data is actually measuring. would still expect the graphs to show an increase if they measure the price of actually sold property.
Just checked OECD data and to me it looks like prices are rising in similar ways in Germany and the US since 2015. Japan does in fact seem less steep but it's still rising, not flat as the graphs on TFA would suggest: https://data.oecd.org/chart/6ztU
IMO these acronyms have reached the point where they don't really serve a purpose.
What's "central heating"? I believe Germany already uses central heating in most places. The question is what powers it. Can it be efficiently replaced by renewable-energy (!) electric heating vs. fossil? Other commenters have posited "no".
The way I see it, investing in nuclear should have been part of the plan, instead of replacing it with renewables (vs. doing so for those uses of fossil where renewables make sense). The fear of nuclear energy in Germany is just ridiculous IMO, and arguably has become a self-fulfilling prophecy. With nuclear power on its way out know how and effort to research and to maintain existing plants and investment in it are at a minimum making continued operation now a liability.
For example {| might be paired with |} as special quotation syntax, at any rate some form of bracket. See, Fira Code has a ligature for those.
But in Ruby you'd see one of them in one liner blocks, e.g.: list.map {|x| x*x}
Here {| is not a thing that should be combined. It would look really confusing as you'd search in vain for a corresponding closing special bracket. { and } denote the block and | and | the argument(s).
How symbols are combined to form meaningful units depends on the syntax of a language and this issue cannot be avoided. So your milage may vary.
I'd be on board more if ligatures were applied in a language specific way, aware of the meaning of tokens in context, e.g. to leave <= in string literals alone, render it ⇐ when used as an arrow (maybe in a language that has left arrows), and something like ≦ when used in a comparison context.
But the same thing being rendered in different ways may be very confusing (unless there's an easy on/off toggle).
Not saying that Germany shouldn't "let you back in" if you want to immigrate back, but the mere fact that your ancestors were German should not qualify you more (safe for certain exceptional populations in recent war history) than others whose ancestors might for instance come from the UK.
That's even more of an issue, no? You accept the offer but don't yet resign (as others have said one should) until final confirmation, they tell your employer that you are joining, then rescind the offer, and now what?
What kind of tasks are you referring to in the context of on call here? Tasks to remedy the root cause of repeated alarms paging folks?
The recipient of Japanese bank transfers only gets the name. The phone number is only for the sending bank's side to reach out to the sender in case the transfer failed. Particularly of importance when you make transfers without owning an account at the sending bank (not sure how common that feature is outside Japan).
Also of note, the Zengin system actually allows additional metadata in so-called EDI messages. However it's somewhat rare to see this offered by interfaces, and so likely not generally suitable. Here's one example: https://faq-chibabank.dga.jp/faq_detail.html?id=31
> The Single Europe Payment Area (SEPA) offers free, instant transactions between European banks. They’re pull based
There are also push based SEPA transfers. Not that the article claims there aren't, just seems incomplete to present only the push based version for Japan (and not furikae and its challenges) and only the pull based version for Europe.
The method requires a substantial amount of effort (time) to learn and apply, and assumes a certain level of education.
Not that I know or could tell that the critics are right, but is it really just that easy to teach and learn?
I feel like there's always something odd about some of these taught communication techniques, where I feel like there's a reason these communication styles don't come naturally to us, and there is a bit of a manipulative aspect to them.
It seems like a farce, really. I also had quarters in which I got glowing peer reviews where folks declined to fill in the development piece, and my very off hands manager came up with some made up generic negative feedback for me that did not come up before.
Someone who needs to save face when asked if content made sense will have not understood the talk. It's doubtfull they'll have anything to add to make your explanation clearer if asked for that, not without again losing face and admitting they didn't understand a certain part.
However I do think the rephrased question will invite more feedback from those who already understood the content and themselves are aware of the more bumpy pieces and want to point them out. Those folks are indeed more ready to now provide feedback.