And I am writing my dissertation, so technically, those stats & the guess are also correct.
2b3a51, interesting planning process. My system with calendar.txt and planning courses: I use week headings for marking the periods and period weeks (4p1). When reserving course days, I just put the tags there (+pw). Later, when I decide the main theme, I add it ("+pw deploy"). If there is a special channel, guests and other info, I add it as it arrives.
For past events, calendar forms a nice basis. At least for me, most of the stuff I plan, happens. I understand you add some insight there, maybe I should try that, too.
And even worse, because they don’t only hurt performance and usability, but they also report private information. Even is the data is sent anymously, the url itself may contain private information. For instance, Google themselves still allow sharing documents via a “private” link which is then stored on some monitoring service. And some of those services allow anyone access and search these urls for some premium plan.
I don’t believe the users are made aware of this kind of usage of their network. In fact, I’m pretty confident that most extension burry this purposefully In such small letters it’s impossible to understand. Which, for me, qualifies them as malware.
Absolutely. I’m not sure why you’re surprised when 90% of websites out there with a cookie banner also lie (maybe even to themselves) about their GDPR “compliance”.
Understanding other’s feelings seems to be only part you’re focusing on, but it’s not enough to have empathy. The dictionaries you’ve linked to have each a list of skills and I don’t think each stands on its own. It’s a combinations of those.
I’m sure AI already have, and cenrtainly will have it perfected in the future, an ability to “understand” feelings and emotions if I use the term “understanding” the way you do with sociopaths - the ability to analyze and act on. Certainly it can not be called empathetic.
You're blaming the victim. Yes, it's better to know git than not knowing it, but the developer was merely tossing around with the various options of the IDE. It shouldn't be that easy to make an operation with such disastrous results. It is the responsibility of the product designers to prevent this.
I think the question is more likely: should an operation like this be possible at all? VSCode already gives you a big warning (as shown in the issue) that "discarding changes" is irreversible but it does not explain what "discarding changes" means.
When people empty their recycle bin they kind of understand what is going to happen. Discarding changes speaks to me but evidently not to this person. Personally I tend to put my code in Dropbox in early stages as git commits do not make much sense (of course one can squash everything and do a rebase but that is advanced git already).
I was surprised when the exact same thing happened the first time I "played" with Code :D ! Discovering this the hard way.
Well not that hard, because of course I tried it first on a copy of the project so haven't lost anything (if not time).
But even if I agree that what is going to happen is unclear for some (included me at the time), and a total wipe of your work is excruciating, you don't "try things" on the only copy of 3 months of work.
I think the obvious thing that VSCode could've done to avoid this disaster was moving files to recycle bin instead of deleting permanently on discard. You or OP might say why would the behavior of a Linux tool like git move to recycle bin? Well, TortoiseGit on Windows (git client) (or even going as far back as TortoiseSvn) will always move files to recycle bin when you discard changes. If they can, there's very little excuse why VSCode can't. There is also very little maintenance overhead for a user. Once in a while you notice your recycle bin isn't empty and you go and empty it.
One of the earliest lessons I learned using a computer is that you don't toss around with options unless you have backups and/or already use form of (distributed!) version control.
Even most of my relatively computer-illiterate friends and family members do rudimentary backup for their stuff (usually in the form of emailing themselves or just creating a copy).
He might know how to write code, but obliviousness towards source control (and backups, for that matter) is a HUGE indicator of him not being a professional.
I would agree. User friendliness isn't a bad goal for any piece of software, but there is a certain level of knowledge we can expect from a professional. Knowledge of their chosen tooling is one of them I feel.
It's not even knowledge of tooling, it's knowledge of practices. How would you feel about an electrician who doesn't properly ground the circuit he's about to work on? That's how I feel about a programmer who doesn't take backups of his code in short intervals (which is a big part of what VCSs do).
Come on though - there are so many ways you can lose data. Having 3 months of work not backed up in any way is foolhardy in the extreme. Hard disk failure, power surge, robbery, data corruption, coffee, fire/flood.. Personally I err on the side of paranoia with these things.
The victim did it to themselves, it's like playing with a loaded gun then complaining when you accidentally shoot yourself in the face. A bad workman always blames their tools. At the very least they should have learnt Git.
There are many more students than teachers, so even if hn crowd has x5 number of teachers than students, you're still statistically correct