Man… the battle between cultural expectations and our true selves is humanity’s oldest conflict. A few people get lucky. Most of us survive in the cracks.
No capitalization was as surprising as the narration itself… not sure how to feel about it! Counter culture?
honestly ive had it with the shift key myself. just a nuisance. besides, the text looks much nicer and 'even' when every letter is broadly the same height, but that is ofcourse subjective.
it would be good to track down the 'etymology' of capital letters.
Capital letters at the start of sentences makes reading easier for those who are used to reading languages where that is customary. The absence is a noticeable reduction in ease of reading.
> it would be good to track down the 'etymology' of capital letters.
Easy: Latin script.
The more interesting question is the source of lower case letters which appeared much later.
But an attacker with one of the biggest vulnerabilities on earth (hell, ssh noauth 0day) would very likely use it against big cloud providers and infrastructure (isps and others) and not burn it on your home server! Keeping it reasonably up to date with your distro's cycle is probably enough for most people doing this home server thing.
So of course, as things always are with security this is a matter of risk assessment and understanding your attack surface, a server with only public key and maybe on a special port goes a very long way, add fail2ban on top and i'd say it's probably fine for quite a while.
But that does make me think... what if... a wormable noauth 0day like that on ssh or some other popular system... how fast could it replicate itself to form the biggest botnet.. how long would it take, to take over all visible linux servers on the internet (so that your little home box ends up being a target)?
I guess at that point you are limited by bandwidth, but since you can scale that with every compromised server... hope someone does the math on that one day!
Ipv4 is only 4 billion addresses. It doesn't actually take very long to just try all of them. If you're running a service exposed to the internet and it has a published exploitable vulnerability, it's just a matter of time before it gets exploited. (that said, that time does give a little buffer for patching)
Drama - but I’m making progress with radical accountability (which I used to think of as self gaslighting). It has helped me cut down my own bullsh*t and I’m happier for it!
I’ve been toying with the idea of creating physical coffee table books with accompanying digital / online version (think photo blog) to document both pictures and thoughts for a particular trips for example- I think it’s much better approach than old school albums.
The landing page is a bit weird. I‘d expect stuff to be clickable (e.g. „Install software“) but it’s not and the text is very generic. Not a goof first impression, sorry.
Not when it’s at-will employment. You don’t need a reason to fire anyone in most states in US. Only exceptions are protected things like because of gender or race etc - but that is even blurry to prove it.
Unions are the only protection but companies do everything to burst unions e.g Starbucks and Amazon.
In the US at the Federal level the IRS and DOL have specific tests for contractor vs employee. If you hire contractors that are really employees they will come after you for misclassification. This is independent of State laws.
I most definitely struggle with this as well - a friend sharing their issues can result in instant solutions streaming out or even sleepless night “solving” their problems!
I haven’t completely gotten away from the habit but I now make sure I ask at least 3-5 questions about how they’re going to address the issue, details or how they feel - it helps me slow down the stream of solutions and more often than not they already have a solution of sort!
It would really depend on the severity of the bugs... assign severity levels as part of triaging.
Also what kind of bugs are coming up is important... I think bug do tell stories; it might help you identify issues with feature assumptions on workdlow or use-cases and that needs to inform your product development as a feedback loop to avoid technical debt and having to rewrite stuff later.
Depending on the size of your team, I would have a 2-4 people focusing on just bugs / QA (so you can catch most bugs going forward) while the rest of the team focuses on new features.
No capitalization was as surprising as the narration itself… not sure how to feel about it! Counter culture?
reply