IggleSniggle

Of course. And I thought I acknowledged that mentorship is many things and there are many things that we need to grow as individuals. I've had a lot of great mentors in my life.

I still think you've missed the point. You can be grateful for the many gifts you've received and still wish to have had engineering guidance from a trusted mentor. There is not enough time in a life to go down every single rabbit hole; it's nice to have experienced people accurately point out where the rabbit holes are. Non-engineers are not equipped to help spot engineering rabbit holes; they might even tell you that engineering itself is ultimately a pointless rabbit hole.

But even then...that's just my own experience and my own wishes for my past self. I try to give what I wish I had had, of course.. think that's what drives most mentorship, and maybe that's the point you're trying to make, that mentorship is given out of that wistful feeling of wishing you had received advice/help and passing along the lessons that took you too long to find.

But still, if your role is getting stuck alone in the server room or whatever with a team of people who don't understand or respect what you do, good luck.

The point I was trying to make (and maybe failed because I got too focused on my own experience) is that really, not everyone gets mentors, even of the broader sort that you're referring to (which I might say are more accurately called friends or peers). But even if we widen the scope of what mentorship is, it's also perfectly reasonable for field-specific mentorship to be a cultural expectation for software engineering. I think it's a good thing to expect this of each other, and to encourage explicitly making space for the practice.

But again, however you want to widen the scope of what mentorship is, not everyone is getting it. The reason people look under rocks is because they don't know where to look. Or they do know where to look but also know they have blind spots and don't know how to get them addressed. "Look up" is nice and all, but it's a bit rude and distracting when you're trying to build something and need help understanding the foundation below your feet. Sometimes you don't need someone telling you to look up, you need help seeing where to look closer.

Everyone is looked at as a young person when they are young. I've definitely had "junior" colleagues that "got it" better than my 50yo colleagues. It's possible I shouldn't say that outloud, because skilled youngsters have a tendency to misidentify themselves as being part of that set while the wise youngsters have a tendency to *underestimate* their own capability or insight. But I don't think you can make that same assumption about a senior thinking back to their early years.

I desperately wish, to this day, that I had been in the position to receive mentorship. I basically hang out on HN as a way to gather it where I can. Attended engineering meetups when I was younger as well. But I never had the benefit of working with engineers senior to myself. I was a junior "business employed person" but when you need to make a roof you do what you can and learn the hard way even if there's no other humans to show you how to make a proper roof. Luckily, you can receive mentorship not just online, but through books, or even just studying the craft of others...but you take what you can get.

Receiving mentorship is such a gift, and as I approach the end of my career, I am still hungry for it, and harboring some degree of wistful envy for those that receive mentorship as an engineer. I've had many great mentors, but my for the most part, engineering mentors have never seen my face, heard my voice, or known my name, and certainly not for the first decade of my professional career as a software developer, where I didn't have any other developers to work with.

Seems like it's anybody who wants to just use native js features without complication. Anybody who's been writing modern js and is aware of all it's features has probably had the thought "oh we really don't need almost any of this shit with the web native features we already have, we just need to teach people about those existing features."

Arrow-js looks like it's basically advocating for not using anything but vanilla js by tricking you into thinking it's a framework / lib. I mean, it is that, but it looks like it's barely that, and just sorta shows off how you can use vanilla js features to accomplish what all the various libs do, without introducing a lot of special lib-specific concepts.

[flagged]

Well said. Everybody has power, they just throw it away because exercising your personal power is at best a pita, and at worst, personally dangerous. But retaining access to your personal power requires exercising it from time to time, or it will atrophy.

It's a form of tithing. You give to the propagandists providing the slant you align with, even if they're wealthy billionaires. It's been common for belief communities for centuries. Poor people do it for access to wealthy individuals or as a form of gambling on the promises of the propaganda, and wealthy individuals, when they give, are also doing so for influence (access to poor people en masse). Its propaganda all the way down.

Holding long epic poems in your memory alone was once a celebrated skill.

Of course I trust my kids to make the most of the environment they are given, and given that their environment will differ from the one I am adapted for, they will likely surpass me in being well adapted to the environment of the future; it's still my responsibility to prepare them as best as I can for it.

You might put a baby in a pool so it can learn to swim, but you make sure their environment is such that drowning is an impossibility. A child destined to be an Olympian swimmer still requires guidance, even if their natural ability and inclinations outpace both their peers and their elders.

Caveat emptor, I don't write Zig but followed its development closely for awhile. A core design element of zig is that you shouldn't be stuck with one particular memory model. Zig encourages passing an allocator context around, where those allocators conform to a standardized interface. That means you could pass in different allocators with different performance characteristics at runtime.

But yes, there is a default allocator, std.heap.page_allocator

I agree that it's about usage and connotations over time..isn't that what etymology is at the end of the day?

Correct. So, you can emphasize your new identity as an "emigrant from A" or as an "immigrant to B." "Expat" goes one step further by not only emphasizing that you are an emigrant from A, but also that you are no longer a political participant or under the authority of A. It is not semantically incorrect to call yourself an "expat" if you are an expat, nor would it be semantically incorrect to call yourself an emigrant from A or an immigrant to B.

I'm attempting to pin down why some people might feel that someone calling themselves an "expat" has some negative connotations for the expat. It doesn't have anything to do with the correctness of any of the terms involved.

To say it a different way, I think people find it distasteful because it focuses on the political shapes you no longer are bound to, rather than who you are "now." It's normal to celebrate your cultural heritage, but it's kind of odd to focus on your status as a non-member of your former state.

It generally means that while you live somewhere permanently with no timeline on returning "home," you do not allow yourself to think of your new country as "home."

It comes across as a refusal to immigrate. It means that what you care about is that you are no longer living "at home," rather than caring about assimilating with your new home.

It's like going to a new place and identifying yourself as an "emigrant" instead of an "immigrant."

"Patriation" is about giving away authority so that the other country assumes authority. "Expatriate," then, would be that authority of the old country no longer applies, with no acknowledgement of your new circumstances.

Oh here's a good one; what if you got married, divorced, and married again? You would be an ex-husband or ex-wife, and it would be entirely appropriate for someone to refer to you as such in certain contexts, but it would be really off-putting...especially to your new spouse.

Imagine introducing yourself as an "ex-husband." If you're with a bunch of your ex-wife's old friends and associates, then it might make sense to introduce yourself this way under some circumstances...but usually, even then, it would be far more polite and in better taste to introduce yourself in some other way.

Much better to clarify your former relationship only when it's pertinent, and maybe even then "we lived together for awhile" might be a gentler framing. Otherwise, you are simply drawing attention to your divorce, and to what purpose?

That's funny, I always thought that meant, "my superior told me I had to do this obviously stupid thing but I'm not going to say my superior was the one who decided this obviously stupid thing." Only occasionally, that is said in a tongue-and-cheek way to refer directly to the speaker as the "superior in charge of the decision."

"Took some" does not match, although your overall point stands

Surely this one is near universal. At the very least a clarifying tooltip of the verb would be helpful!

Right! If you want it to denote an action, you need to include the verb: "TURN ON" would be entirely clear. It's even clear if you sometimes DO want to show state / not a button "IS ON" is also perfectly clear. There's only a few that might he confused when the verb is shown, like "INCREASE," although I would have to work a little to imagine the UI where it's not clear whether the button is showing the verb or noun.

Should have done it the other way around

What's the story?

It's very very good! I thought this one hit hard though, I assume inspired by the moon = 1-pixel viz.

https://hmijail.github.io/1-pixel-wealth/

??? I didn't say anybody using npm wants this. I'm saying npm had the wrong policy around deletion, that npm could have handled the situation differently, and also that Azer not knowing or caring about the effects of removing the package doesn't make him an asshole or even negligent (although it also doesn't mean he ISNT an asshole; that's a separate matter).

The point is that Azer didn't owe anybody anything; not even to know what he was doing. npm did.

That said, I'm glad the wake-up call came in such a relatively benign way.

Sure, but that license doesn't include the requirement to host in perpetuity, and anyway, I wouldn't expect a hobbyist to need to worry about this. If I decide to make my gamer-profile private / offline or something and that breaks your crawler, even though I previously granted unrestricted public access to that data, that's really not my problem.

Please. It looks like he was doing dev as a hobby, asked a big company how to handle removing his packages, and did what they told him to. They might not have had the right policy, but that doesn't make a guy who doesn't want to give his packages away to a company just because they're making threats into an asshole. It makes him typical.

The 3rd option is the one Azer describes in the post:

He wants to remove his stuff, but isn't sure what the right way to do it is, so he asks npm. npm provides him with a set of scripts to run to remove his stuff, and he, presuming that it's "ok" if npm told him to go ahead and run them, runs them. The impact isn't especially important to him, But since npm just gave him a set of scripts with an implicit "oh okay you want to remove your stuff, here I wrote you a script you can run to get it done," makes it more of an npm choice to handle it in this manner. npm asked him to handle it this way, so he did.

It doesn't, and at least in this thread, I don't think anyone was saying it did.

That's the selling point to VCs. The selling point to consumers of the tech is that AI will make only them, with their special inherent qualities, outperform their peers even more (unspoken, but also implying that if they are an underperformer they might be able to catch up), but only if they act now! This limited time opportunity will soon be used by everyone!

And their human content fed into the machine, so it can be mass produced whenever and wherever desired, allowing less of the total benefit to flow to the creator, giving them just enough incentive to keep feeding the machine.

We're talking about an Apple product here. We don't talk about that stuff.

We do periods. Because it just works.

What's a computer?

Last century, we showed you how to Think Different.

Now you'll never need to think again.

This stuff is readily available in the macOS ecosystem, but I don't fault anyone for jumping ship for these reasons. It's the same reason I did, before I figured out how to do it in macOS land by way of being required to work on macOS anyway.

Thank you for clarifying for me so elegantly. That self fulfilling prophecy does have a sense irony to it, especially given that the code is open sourced.

The customer's in-house developers raised their hackles and had reservations about using the product, even though the customer's in-house solutions were terrible, because the customer's in-house developers wanted to build it themselves. I'm not sure if the article wasn't well worded and you misunderstood, or if it's me who doesn't see the irony.