When the dam was built, they didn’t know they were cutting off the fish from it’s only spawn point in the world (it was discovered later).
Still, there’s an argument to be made for building a bypass or fish ladder in every single new and existing dam regardless of what the current expected impact is.
Studying fish habits when building dams is an ancient practice.
My guess: a political, hasty, rush to success to curry favor and clout drove bad decisions regarding a massive government project. Is that not the way of public bureaucracy, universally?
What's wrong with exposing SSH? It has got to be one of the most well tested pieces of network software out there.
Re. fail2ban - nearly all ssh scanning attempts in the wild seem to be from unsophicated attackers using some pieces of obsolete software. I disabled all but a couple of modern ciphers/mac/kex algorithms and hardly ever see any password bruteforce attempts in my logs (not that they have any chance of working - I disable password authentication as well). Mostly a bunch of "no matching key exchange method found" which I regard a minor nuisance.
you can set up a trigger port, that will open an SSH port when triggered properly. some routers come with this functionality, a third party opensource firmware usually does this or allows for a script to implement it.
so you "knock" on port 666 lets say with a majic packet of some sort this opens a secured SSH port, then drops it on command or idle time to live expires
I actually did try emailing Tim Cook a few months ago, but I got bounce backs. I tried tim@apple.com and timcook@apple.com but the mailer daemons said the addresses weren't registered. It sounds like a crazy thing to do, but I remembered how Steve Jobs would reply to users' emails and read an article where Tim said he set aside time to read users' emails.[0]
- I’m never filing a bug report ever again on a bug filing system where I don’t get to see the progress in a transparent manner or that I might have to pay for a developer account to see that progress (assuming that’s an option)
- I’m not wasting my time emailing a top level company executive to inform of decades old most basic of bugs because if they don’t know of it then that’s even a bigger problem.
I’m somewhat surprised that acknowledging outside emails is a thing. I know unsolicited ideas/content/etc. is commonly rejected without review in other fields. Is this successful beyond identifying technical bugs?
It would probably work better for the two Steves than it would for many others.
According to the below random site, there 218 Jobs and 10,602 Wozniaks. It claims 410,801 Steves.
Related, I emailed Tim Cook about iPhone sensor future plans, and a high-level exec of like 25+ years wrote back to me within a week. Apple is remarkably good at getting back to cold emails to top execs.
Interesting, perhaps I’ll cold email them about the pinned contact feature in iMessage being totally worthless.
If it just pinned the message thread to the top and didn’t change the icon to a giant circle that sometimes doesn’t show notifications, it’d be fine. I pinned my GF’s message thread and I ended up missing lots of messages and notifications from her and ended up unpinning her so the notifications would show up.
Not to mention the comically huge circle icon that is centered when everything else is left aligned.
I had a problem that appeared to be a corner case with Apple Pay. I wrote a paper letter to Tim Cook about it, and within a week got contacted by a staff person in his office. He worked exclusively with me to identify issues I had not considered, and followed up on all of the direct effects and side effects until they were resolved.
I emailed Craig about several controversies and he was very quick to reply to me. We last talked about the rumor that Apple was giving iPhones trust scores.
If they're interested, obviously. The fact that someone looks up to you as a mentor is great and instills a sense of responsibility onto you. I personally start with Python because its syntax is very easy to understand, even though most beginners struggle with indentation (this is where a good IDE / text editor comes in handy). Teach him about problem solving and critical thinking first. Encourage him to pursue a fun project even if it seems silly. After all, programming languages are tools just like screwdrivers. If he has nothing to fix, make or mod, he'll be directionless.
As a programmer myself, sure I'd like to tell people. It's not realistic to make everyone a programming genius, but I want them to know its significance in society. When I describe programming to somone, I start with the most basic stuff, like Theory of Computation. How inputs relate to outputs, how a computer can do stuff on its own, and how you can make it do stuff.
It varies depending on the field but what matters more than university popularity is how you spend your time at said university.
I'm a CS student from a very small university myself (so apologies if this doesn't translate well for you), and I know several smart people from very small universities whose contributions to open source software, personal projects, and connections within the startup community and various other factors really pushed them ahead.
So spending time meeting people with similar interests and pursuing meaningful things in university is essential to your experience there.
Thanks, that helped quite a bit! I’m guessing the difference between CS and my situation would be that I should spend more time doing research and studying than worrying about the “name”.
Yes, and I might sound naïve here but if medicine is truly your passion and you’re willing to go to any length to make sure you contribute positively to the medical community, then you won't regret your time there.
Have fun in university, and good luck with your studies. We’ll be rooting for you. :)
I don’t get why people don’t bring up documentation more often either. Having good documentation is a telltale sign that the software you write is high quality. Sometimes you even learn if a feature is stupid based on how you can describe it.
It’s sad to see how many great open-source projects get overlooked on GitHub because they’re poorly documented.
The fact that anyone can post anything, so you could have a serious issue in your code and they give you an inefficient solution, which is then upvoted by users who don’t know better.
https://en.m.wikipedia.org/wiki/River_bifurcation