captain_crabs

This is a pretty good point. However, there's also the chance that they can't use the gear and that's why they're sending it: https://www.google.com/search?client=firefox-b-1-d&q=virus+t...

However, could be this was a one-off genuine mistake (things are hectic). I'd love to know more

If real information about China were to leak out, my guess is it would happen through the vector of internet/social media. Chances are, some other source would need to copy + repost it before being taken down. This is what I looked for.

One such account which is purportedly doing this is https://twitter.com/truthabtchina. To summarize this, among other rumors:

    - lots more people have died that communicated (there's an estimate of ~22m due to missing cell phone contracts)
    - riots are happening between regions where lockdown occurred, and regions next to them)
    - lockdown isn't practically over in areas where resurgence of infection is happening (pending other containment approaches)

edit: I've eaten dinner with some friends from China in the past month before lockdown started, and am in frequent contact with people traveling throughout SEA. I was trying to provide and summarize a potential semi-primary source. Added some more specific #'s, info, and removed inflammatory words. Sorry - I wasn't trying to be fear-mongery. However, I am trying to accurately reflect a harsher reality

I do think it's quite reasonable to assume some areas of China are getting back to normal.

I also think it's quite unreasonable to assume info _isn't_ being censored and controlled, especially post journalist-eviction.

I'll drop into this more, because we might not be connecting on what layers we're talking about. I'm talking about immediate medical survival. If by "resources" you're talking about financial/economic support, then I could very much agree with an "everyone right away" approach.

I see the immediate health layer as subject to physical limitation, the economic layer subject to informational limitation. If by resources you mean money, then yes, I very much agree.

Part of the benefit of living in America is the fact America will put it's citizens first, no? I fail to see how putting the rest of the world before our own countrymen could at all work. To many, that would be viewed as betraying countrymen if we didn't handle it here first. I'd even posit that an America that's contained and controlled COVID-19 is better for the world than one that's not.

I'm _not_ saying we shouldn't help the rest of the world. That's the very next thing. I'm saying, let's make sure we're not drowning before trying to help others not drown.

This is a really weird line of reasoning because I don't think it even holds in the case of a broader unity.

A kind of concerning thought: who's to say there aren't higher-level versions of this same concept playing out? Say we figure out the nature of consciousness and are able to effectively interact with it's "thinginess." Then we find: there are things in our universe that're semi-conscious, but feed and replicate on/inside/with the consciousness of others and are incapable of existing on their own.

How's the process of getting him to present go? I'm interested in doing the same!

would you even suggest this over riker?

General question I've been wondering tangentially related:

Engineers:

is working [edit: replacing 'under' with 'with' due to replies! good clarification, didn't mean under] with a non-technical product manager a dealbreaker for you? (Do you look to filter out places you'd work at while job searching?)

Conversely, have you ever worked under a non-technical product manager you loved? Would you mind sharing details about your situation?

How did you go about creating your work sample test?

Although I've read through the "css grid isn't meant to do this details", you can get fairly close to this with pure css grid, see here: https://github.com/wesbos/css-grid/blob/master/20%20-%20CSS%...

When this topic comes up, I always come back to this: http://worrydream.com/ClimateChange/ If you haven't - give it a glance!

God I can't stay away from this thread.

Yeah - entirely depends on your subdivision vernacular. Some people make subtasks in a ticket, some people make tickets linked to other tickets, some people do both and link those to "features" which are themselves tickets (like the environment I work in).

Just depends!

Sounds like we agree, but use different names for the same things and some of the same names for some different things! :)

And final thought, "correct" or not, a guiding principle that's proven useful over time: individual tickets should deliver true pieces of "value" which is to say, once deployed, the software does more of what people need than before. So when a ticket is "done," it means something was improved however it was needed across all levels of the stack.

None of this "button here" "wire it up later" "now add the db table" etc.

I haven't read any further comments on purpose, immediately logged in to reply because I have a prediction:

People are going to say the user story you listed is _way_ too vague, general, or otherwise "not right" or "something they've never seen." They're going to reject it/pick it apart for a litany of reasons, all of which triangulated against their individual experiences. Me too! Here goes:

I've found "user stories" miss entire dimensions of context from the business side which are incredibly important to developers. In lesser-performing orgs, this is often a way the "business folks" (and yes - in some orgs, there is a distinct divide) wield information asymmetry to pawn off blame onto devs when "things aren't right." This information about how people are really gonna use the software vanishes somewhere along the way before it turns into a user story. This post gets at the heart of it pretty well: https://jtbd.info/replacing-the-user-story-with-the-job-stor... (which, btw, if this makes sense to you, is something you're strangely passionate about, and you're not familiar with "jobs to be done" then go get intercom's free ebook on it right now)

I have another guess. This is less of a prediction, more of a thing I'd like to find out: of all the people who reject your user story, how many of them have worked at places where their product manager isn't a technical person?

My guess is: most of them. I'm also guessing PM's get super specific because developers moan at them over minutiae, info gets cut out/they don't realize it's important, and there you go.

I'm betting most orgs adopt agile as a means of combating poor engineering dept performance, and generally (not all the time - but generally) this is directly due to the people managing the technical people not knowing what they're doing, so it's essentially a set of default behaviors that protect both sides and guarantees some minimum (read: not maximum) of performance. So these product managers who don't understand any development are put in charge of developers consider writing tickets their job, and instead of understanding reality -> reflecting that in tickets, they write their tickets and try to coerce reality to follow.

Frankly, take a bunch of people who already didn't want to change their process, force them to hear "you should update your process that's how things are supposed to be" every day, and after a couple months they actually start to do it.

Ticket shaping is super hard. I don't trust a non-technical PM to do it right, unless they happen to be experienced and/or have devs alongside them who are essentially just doing their job for them. Add onto this the fact that typically management consider all parts of software development a linear process.

Not to say you can't have PM's who are nontechnical, and can bring all the right context/organize everyone in the right ways. I believe they exist, I just haven't worked with any. Devs are generally ineffective at communicating technical context in non-technical ways, and reality is an emergent mix of both business & technical.

this has turned rambly. tl;dr - user stories are such a vague/overloaded concept for so many reasons, if you have the choice read up on "job stories" and try and switch to those. They're no less confusing to implement, but they force you to find answers to much better questions.

It's a matter of dosage. You might be talking about how another tech stack would perform better at this metric, but the price of that is the company would have been simply unable to ship anything in the time they could afford.

Swinging the conversation beyond the dosages of either side doesn't produce interesting insight

This is a good point. But I think PWA's are still better than monstrous everything chunks. It would be good to make pwa's configurable to user preferences

There's a little big detail w/r/t java comparison: every company I've personally worked with who uses rails for their backend vs java moves WAY WAY WAY faster. So in terms of the "enterprise stack" dichotomy, there is a difference in kind between rails/java.

I get things done faster and more maintainably (for future me and other devs) when I do it in rails. Hopping into apps that rely on (request, response, next) always hits me with a learning curve every single time I come back to em, which gets worse as complexity rises. It could also be that I'm very bad at thinking in terms of pipes and need to practice that more.

I also find that in rails, there really aren't _that_ many ways to do things. And, in general, apps that age gracefully always figure out how to phrase their domain concepts through the smallest restful url's/resource mappings they need. There's a lot to be learned from the approach the smaller micro frameworks take, and you can get the best of both worlds in a lot of ways.

Yeah. Dota's the one game I've consistently played my entire life. Seeing it bloom and blossom from just this thing I knew & enjoyed into the whole primetime, then merging into broader tech...this is awesome!

Crappy garena, banlists, vs 5 ai in wc3 when no internet... :')

Holy moly! Well, that's a different narrative than I suspected...

See shadow dom section in here: https://github.com/w3c/webcomponents/ which specified most of docs are maintained in here: https://dom.spec.whatwg.org/

And as for what it is, you know how a given web page has global css/query selector scope? Shadow dom is like a membrane in there, where styles and other things don't go in (unless you explicitly poke a hole). It's like a whole new document that you can nest inside an existing document. It's encapsulation inside browsers

Sketch + Zeplin are my tools of choice, also! :)

Give me right click + copy to css, and we'll talk.

What can I do?

Here's the line of reasoning I use that keeps me in the game. Sorry if this is way off the deep end! :)

"The impediment to action advances action. The obstacle is the way." - Marcus Aurelius

In the face of overwhelming despair, there's always a choice you can take that is hope. Right action is training yourself to habitually choose that, and continue with it, regardless of the circumstances.

Those deepest moments of self-doubt, those are when you're able to have thoughts from that context that you couldn't when you're all happy and stuff. Those moments themselves are intrinsically valuable to be present in, and pay attention to. And by inducing them in yourself and choosing to behave properly against them, you can train yourself before the big moment comes.

I feel like this might be crazy and overly intense, but I can't really conceive of any other aspirational way of existing, so I hope its somewhat helpful!

I've found it easier to just drop in `react-rails` and build out react components for certain situations than to try and string a bunch of jquery together.

I've transitioned from rails-everything to working exclusively with front-end frameworks and libraries (react, angular, polymer), and I'll tell you this still: if I'm working in rails, I use turbolinks. It's a wonderful approach, way under-appreciated.

When two or more things on the page need to know about each other/you require a high-fidelity interaction that you can't easily handle with just it, then yeah - reach for vue, react, or what have you. But no need to start there! Use those as targeted air strikes

Ruby on Rails has entered the 'boring' phase of the hype cycle, because it's 1) widely used 2) extremely reliable 3) lacking controversy. Have you used ActiveStorage or ActionCable lately? They're brand new, probably not relevant to HN at large, and awesome!

Depending on what you're doing, you might need to pause/play/rewind the podcast a lot. I walk to coffee shops through some neighborhood area, and then some busy roads. So I make sure to pause for traffic noises, often I've gotta do so to talk with neighbors, and then so on. I don't even have an apple watch, but not having to deal with pulling my phone out a good number of times per walk over a lot of walks means a lot less times I could potentially drop my phone.

Love that movie.

The house is for a very specific purpose: it's how I want my life to be. Both to live with SO, but also to have space to get an aquaponics setup running.

So that will be happening when it needs to happen regardless of market timing. But if there's a thing I can take advantage of in that window, totally should!

Is random walk on wall street viable on audio (audible) or are there a lot of charts and stuff?