3,096 karma · joined March 17, 2018
Annoyingly they're going to EOL the cloud connectivity for it in 2023 and then the product in 2025. I've taken all my notebooks offline and will deal with it at some point, probably in 2025 :D
I imagine a lot of that could be avoided with some assistance from the education sector along the way.
My eldest wants to be a doctor so I've tried to share as much of my experience with her on how to learn so she doesn't have to make my mistakes as they still don't teach them any of this today, at least in the UK.
If you're a single user, effective offline backups are probably a better investment. It's not that bad starting from scratch if you have all your data. It takes me about an hour to throw a usable build onto my laptop.
However corporate networks where the damage has a big multiplier may benefit from it and you certainly don't want to be asked all sorts of questions about whether or not you had a risk mitigation in place if something does happen.
if it's a crash on the client, you should apologise to the user and ask if it's ok to send the crash dump to the supplier and give them an option to review the content and add additional information if they see fit.
CHOICE is not a forbidden word in 2019.
This one totally caught me by surprise for ref when I upgraded, perhaps foolishly. I installed OneNote 2016 and am sticking my fingers in my ears until I have some time to deal with it.
Another vote for paper or neutral formats here. They persist longer than vendor whims!
Case in point I wrote a lot of my work up on TechWriter on an Acorn RiscPC. Where are we now with that. Hmm...
This is the problem.
Yes I dozed off in lectures too but only when I knew the material already (preparation - another modern day student failing!) or had a heavy night or a starchy breakfast.
Like I said I'm fairly experienced with LaTeX. I've used it for technical documentation for 20 years.
Picking an example, I did an EE degree. I sat there and watched a hundred students scribbling out a lecturer's slide with basic function laplace transforms in it. The lecturer moved on leaving 99 people with half a table of transforms. Me, I'm sitting there with <<laplace basic transform table>>. I took this home, reviewed notes and added a reference to my textbook which contained it, added a sticky note to the book page sticking out of the side. Then I spent some time playing with them and trying them out and building valuable real understanding.
Now I've completely forgotten what you even use a laplace transform for 20 years later but I can find out in 10 minutes with that textbook and my notes which I still have in a concise manor.
It takes a lot of discipline and time to write very high quality notes and to study. I spent more time thinking about things and experimenting with ideas and writing notes than I did in lectures or tutorials or labs.
They disclose vulnerabilities to US government agencies first and stil to this day have no transparency about what information they share with governments.
No thanks. That's disrespectful towards the customer and quite illogical. Why?
1. We deal with a lot of personal information and we do not want risk vectors associated with telemetry under GDPR. If you don't have full control over your data then you put your customer data at risk. This is indicated by Microsoft already getting into trouble over Office telemetry leaking customer data.
2. Opt-out is not a logical option because of the fragility of positive configuration. All things should fail safe. Microsoft already broke the opt out for dotnet core on Debian once.
3. It creates a hell of a lot of network traffic to tens of different hosts which makes it difficult to quantify what is telemetry and what isn't.
4. It costs us money to admin. Literally a pile of cash goes into compliance every year and this makes it harder and more expensive trying to plug all the holes in a giant swiss cheese. We'd rather have a cheddar and just make the holes we need in it.
5. If you're not an enterprise customer you can't opt out. This is just WRONG.
With respect to Mozilla and ending support for TLS v1.0 and 1.1, you do what we are doing with TLS deprecation which is communicate with your users, something Microsoft seem to have forgotten about in their drive to marginalise user opinion and move to a subscription model.
The problem is software management has got lazy and stupid and figures that every problem can be solved if you collect enough data about your clients and that total isn't true. What you end up with is a lot of data and a poor signal to noise ratio.
Edit: downvoters - explain yourselves! I explained my perspective!
The point of the lecture is to assimilate structure and basic understanding, not to produce a neat set of notes instantly. To take notes to this detail means you're putting more time into the note taking than the work.
Use a pen and paper. Write down structure as it happens. Write down things you understand, short hand. Write down things you don't for later review. After 2 hour long linear circuits lectures I regularly waltzed off with a couple of pages of loose A4 for review. A lot of the time, our lecturers would give us a copy of the OHP stack if we asked them as well.
Write your notes up at the end of the day with reference material at hand and no compromises. You can structure, extrapolate and transform things into your own understandable language then.
I think that's where shed started. A lot of people got lucky / rich and actually finished their car project. I had a proper shed which was a series III land rover with an engine in pieces in the back rather than the front. When I lived in Nottingham there were a lot of proper sheds!
Those "sheds" on pistonheads are ridiculously too good to be called a shed.
I’ve heard it used in London and Nottingham regularly.
You never know if you’ve won.
Incidentally the police did nothing.
Edit: this was early 90s.
This isn't a specific platform problem but a problem with a subset of humanity.
I do something I hate enough to walk in with a sword and fight it every day.
Epoxy even sounds like a stupid idea. I mean how are you going to repair that next time. It’s impossible to dig that stuff up.