For me, it's working from home with AI assist to save keystrokes and free up my comms bandwidth with colleagues from less interesting technical questions.
137 karma · joined May 10, 2020
Fwiw I don't think SSH adds the include line upstream. Most distros add it now.
There's pushback on the killer feature that I want. I want to be able to sync photos from my phone and clear them automatically so I don't run out of room. I've been told there are ways to do this but they all feel brittle. Syncthing should be in a position to do this safely. E.g., I have 3 destinations and set a policy that photos can be cleared from my phone when they've reached 2/3.
Then jumped over to a startup where we work hard but in a much more organic and empowering way. People come in when it makes sense.
Options pattern is an alternative, I use it frequently, but still miss named arguments and default arguments if I'm going back and forth with Python.
- The options pattern is much more verbose to implement.
- The defaults aren't as easily clear, they need to be documented and kept consistent.
- You can't, or it's not as easy to, make some arguments required.
- And, as a caller, if the API I'm using doesn't support them, I sometimes have to rely on comments to clarify what each arg is. For example, if a function takes a bools like `func MyFunc(dryrun, inverse bool, items ...string) error { ... }`
IMO this came first and is a driver for people stepping back and defending their boundaries with Google. Most of the eng I know just cared about their work (some driven by the ladder, for sure). Google made it difficult and put a bad taste in people's mouths about "work[ing] like hell". Meanwhile, on the startup side that I've seen, people work a lot but in much more harmonious way.
Why not remember how a user logs in with localstorage?
I don't feel like that makes me dependant on any of the big tech cos, but I do recognize everyone won't be able to pull off such a setup.
You can take it even further and authorize requests for verification. E.g., I can let my car insurance company see my zip code, or even just get a yes/no that I live in a specific zip code.
Since I'm a cynic in general:
> Cyan was likewise disinterested in pursuing other solutions that would have been even easier to implement than panning rotation, but that could have made their game less awkward to play...
I disagree with this paragraph.
I think back then, I thought this was intentionally helpful. Thinking on it now, I also think it was part of the character of Myst that would be too risky to lose for Riven.
How?
I pushed it off for a few years -- got pinged once a year about the same time, was in grad school -- but eventually interviewed with and landed at that company.
The premise of the headline is obvious... But I don't know if I even agree with the actual research. It seems like it's overwhelmingly selection(?) bias. The data seems based on humans bringing in or calling for help on wild animals. They do mention predators but also more on vehicles, etc.
In my experience it takes a while to cut over because many managers were strong ICs and it's difficult for the team to suddenly lose that productivity.
But still, seems ridiculous. Was Twitter making ad money off unauthenticated (aka most) views?
- The fair use update is reactive, and won't help anything
- Not separating microsoft/github from users of the platform (I agree the line is an worthwhile discussion)
- Not following up on the reasonable technical solutions that are being proposed
- Not seeming to ack that while the firewall ban might be the best they can do now, it'll block interested users of their own (GMP) library.
That said, the part in the GitHub reply dismissing GMP's hardware is also immature.
However, reading through their response thread [0] I do think they aren't appearing particularly mature. It feels like they are refusing to characterize what is actually going on and digging in and escalating this defensive mindset.
[0] https://gmplib.org/list-archives/gmp-devel/2023-June/thread....
Social media has to deal with something more ambiguous.
The internal lan issues didn't bother me because I still prefer a local fd##::/64.
For a few firewall rules that used the prefix, I noticed that the /56s I'd get weren't completely unbound so it was easy to keep a list in an nftables var.
For inbound access, I have DNS rfc2136 with frequent updates for IPv4 so adding v6 was trivial.
Your suggestion may protect against accidents, but doesn't seem to me to do anything for deliberately malicious behavior.
It's almost as if there's not a one-size-fits-all. Unlike your comment.
What worked for me was to point out the issue early, and keep pointing it out to the high level leads that could do something about it.
At the same time with my own smaller group just buckled down and delivered more, high visibility work.
When the complaints started coming in about the other groups I pointed out we could do more with a consolidated team and that design overhead was to blame for most of our problems.
In the end, there were a couple of folks who didn't make out well here and I feel bad about that. But the overall tone from various stakeholders seems to be a huge sigh of relief.
I may be biased though because I agree with the opinion. I use a combination of my browser's support and `pass`.