ritchiea

There's also good and bad ways to give feedback. It's important to find ways to give honest feedback that isn't crushing your reports's confidence. It's more of a question of when to step in with an important critique that whether to at all. There are some pieces of code and systems that aren't critical enough or won't be stressed by a junior learning through a bad design decision. And critical system where you absolutely have to step in and make sure everything is in the best shape possible.

Agreed. I find with JS I have to write a lot of code for features that could be handled with a gem in the Rails world. I miss gems like devise that had large amounts of common functionality that there is zero value in me re-implementing myself.

What's more pragmatic than not being precious about what technology decision is most perfect and instead going with what's popular and has a lot of community support?

Ok! Your opinion is noted

The zeitgeist is that hooks are easier to reason about than life cycle methods, functional components are more lightweight and result in less bundled code.

The latest consensus is to avoid class components, use only functional components and use hooks to handle state & side effects. Ninety percent of React is building DOM, hitting APIs with an HTTP client and using useState + useEffect. And remembering that you must pass functions & data to child elements to communicate between or share logic across components.

I'm not here to litigate this, Gellman has one take on it, Greenwald has his own. It's up to you who to listen to.

He/she said there isn’t evidence for what I was claiming, I told them where I got the info & where they can find it themselves. Couldn’t be a more straightforward interaction.

Listen to Barton Gellman on the Longform podcast or read his book.

This is good advice, I had similar issues with acid reflux. Though I didn't have the patience to cut so much out of my diet. I ended up starting a diet journal and tracking closer attention to what food & drink triggered my acid reflux. Coffee turned out to be the worst culprit, and cutting out coffee eliminated 80% of my acid reflux incidents.

It's probably best to go the full diet change route & slowly introduce new foods again, but if you read the OP's recommendations and think "I can't do that" there are other ways.

Greenwald didn't have to do any work for the Snowden stories, Snowden approached Greenwald. And from my understanding, Snowden didn't approach Greenwald because he was the "best" journalist to break the story. Snowden had an existing relationship with Barton Gellman of the Washington Post who Snowden also leaked to. But Greenwald was willing to put an encrypted key in the leaks to help Snowden prove he was the leaker to foreign governments while seeking asylum, which Gellman wasn't willing to do.

Then Greenwald parlayed having Snowden approach him into becoming a celebrity journalist. So Greenwald is a guy who takes a lot of credit for being in the right place at the right time and someone else handing him a scoop. Exactly the kind of person I wouldn't trust.

It’s really surprisingly difficult to jump between Python and Ruby. And Rails and Django. They are just similar enough that you think the switch shouldn’t be so tough but all the differences really bite you. Whereas jumping into a completely different ecosystem like JS or Go you don’t have the part of your brain telling you “this isn’t that different, you’ll be fine, look for something familiar.”

The job of an editor is literally to make decisions about what to publish, not to publish everything or kowtow to celebrity journalists or potentially big stories.

The editors have made public statements about this conflict as well. Pretty much none of this is hidden from public view by now.

This 10,000 times. And it’s not just Rails, the quality of the Rails documentation made an impact on the Ruby community that was generally replicated. Compare that to the JavaScript world where cornerstone, insanely popular libraries will have documentation that covers roughly 10% of a library’s API surface area and maybe one simple example that doesn’t cover production use cases. And dozens of out of date Medium blogs.

I don’t understand how people operate like this day-to-day either guessing at APIs or having to dig through large, complex open source codebases just to figure out basic library functionality.

Maybe it’s my conception of how things should work that’s off, because I’ve met developers who actually enjoyed guessing at library APIs and said they don’t like reading documentation. I hoped they were the reckless fringe minority. Maybe they are actually the majority?

I worked so much faster in Rails. The community made that possible by writing well about how their libraries were meant to be used. And if anyone’s response is “well you should read your open source dependencies’s code anyway,” many times I did have to jump into the code of Ruby libraries and it was a lot easier to read the codebase when the library APIs were well documented, providing a context for understanding. I miss Ruby and Rails.

It’s not about who Greenwald is, it’s about the quality of reporting & the evidence they have to support their claims. You can’t run big stories based on the reputation of the journalist rather than the quality of the reporting. You’re basically suggesting they should get out of the way of Greenwald because he’s a celebrity journalist.

Lots of users vote based on the headline before actually reading the article. Lots of users even comment without reading the article. HN is an extremely large community these days.

Is srcset commonly used? I am not familiar with it but I'm more full stack than frontend and often feel like front end moves faster than I can keep up with.

They could buy Vercel & Next with the intention of rolling their own React replacement to swap in later.

You didn't respond to the substance of my comment. It's possible for someone to misunderstand you and for you to lose your job over it. It's also possible to die in a traffic accident. The former is probably more rare than the latter but the former seems to be legitimately terrorizing many people based on the frequency of internet comments I see about it.

Your belief sounds rooted in fear. Can you actually cite cases where doxxing & abuse happened over a conversation with a stranger in a cafe? And even if such cases exist I would confidently guess you’re more likely to die in a car crash than get doxxed on twitter by a hate mob. And no one is avoiding ever using cars or being a pedestrian on a street with car traffic to save their lives.

Maybe knowing in 2020 one can experience rabid social media mobs, and the newness and degree of its terror is skewing our idea of how likely this kind of event actually is. But I see this view presented regularly as though every one of us lives in active risk of being a single slip of the tongue away from ruining our lives. And it’s so strange and not in line with the reality I live in.

Certainly not impossible but I don’t often have to deal with large amounts of files in circumstances where the performance hit matters to anyone. And while I know sed, awk, etc are powerful, I don’t know them & I’d have to learn how to use them, whereas I do know Ruby & Python.

At the very best this is an edge case where one would have reason to choose shell scripts over scripting languages.

Ok well #1 does not apply to me because I don't write a lot of shell. Ditto #2. So it would be better to understand your case for #3, when is shell the best tool for the job when writing a new script? Why?

Are there ever good reasons to choose a shell script over a Python/Ruby/etc script?

I suppose it is in theory but how many of us work in theory rather than with a set of tools that are commonly available?

Or maybe it’s just better to roll your own version control system to support your really amazing new app architecture that stores lots of logic in database functions, what do I know? ¯\_(ツ)_/¯

If you abstract at the db level then your db reading code is either unlikely to be in version control or you need a klug to for version control for stored procedures.

Impossible to generalize, would depend entirely on what specifically you want the stored procedures to do. Though I can’t think of a good reason to abstract your queries at the database level. Even ORMs typically allow execution of raw SQL, so you could still store a straight SQL query in your app code (perhaps in a constant) instead of using a stored procedure.

I’m not sure what you’re arguing. You should have rules for what code goes where and stored procedures are also considered an anti-pattern by most developers because they tend to split business logic between the application code & database.

Let’s say you decide to use stored procedures with rules about what belongs in app code and what can go in a stored procedure, the “discipline doesn’t scale” perspective would say that as your company and app code gets larger your rules get harder to enforce. So devs tend to fall back to the simplest, easiest to follow version of the rule: stored procedures are an anti-pattern.

Allow me to recommend another current HN front page article in response to this: “Discipline Doesn’t Scale”, https://www.sicpers.info/2020/10/discipline-doesnt-scale/

Lichess will flag your account as a cheater w/o notifying you so that your opponents see the flag and avoid games. I know this because a friend of mine who is an average player got flagged that way after a stretch of games he won handily, including one against me where I checked computer analysis and noticed he made zero incorrect moves. A red flag popped up next to his screenname, I asked if he was aware of it and he said he couldn’t see it and got no notification of it.

I love the shadow flag method for cheaters because opponents can avoid games with them and the cheater may never figure out what the problem is.