Open as DOCX, then convert to ODF, then save as PDF, then FML, then look at the utter fucking mess it's made, then give up and go home early because this shit is infuriating. Thank god I'll be retiring in 20 short years!
There's your problem: don't convert it to FML. The warning's right there in the name.
...who never metaverse they didn't like.
We're all still at work.
I didn't come here for facts. I came here for an argument.
A collection of black holes should be called a "bailout".
Don't mess with the plan, Samsung:
1. First, wait for Apple to do it.
2. Then, make fun of Apple for doing it.
3. Finally, do the same thing.
Sure, they'll survive the weather, but won't they just get eaten by dinosaurs?
Here are ten easy steps that you can take to implement Hype-Driven Development for your project.
1. First, choose a new tool. Find somewhere that the tool is being used by a company everyone has heard of. Don't be too concerned about what they're using it for, or whether it relates to your work in any way.
2. When you start using the tool, don't mention it to anyone until you've already decided to base your finished product on it.
3. Don't bother finding out if the tools you have can already do the job you're doing now.
4. Expensive tools are automatically better than cheap tools. This makes it easy to measure fitness-for-purpose.
5. Even if you only use the tool to simplify very mildly half a line of code that's only used once, incorporating a new tool is still worth it.
6. Compare the tool by re-implementing some of your existing tasks. Only test the simplest and most trivial scenarios: if it works in a simple case, it's bound to work just as easily in a complex case.
7. Any inconsistencies with existing standards can be readily overcome by creating a new standard that the new tool fits exactly. Try not to be disheartened by the idea that you've previously been doing everything wrong for years.
8. Have some like-minded suckers re-implement everything even vaguely related to the new tool from the ground up. The more suddenly you can implement this, the more of an impact it will have - and impact is always cool.
9. If the re-implemented product turns out to be awful, or if it doesn't do what users want or need it to do, you'll be committed to the new tool by then, so it won't matter. Tell anyone who is critical of the product that it's too late to change it and that they should have raised their concerns earlier - especially if they did.
10. Stride confidently into your next performance review, knowing that even though you wasted a lot of time and resources to build a product that does slightly less than it used to, you've certainly achieved a lot.
... "I love systemd"? I bet that's what they are.
Replacing a MacBook Air battery depends entirely on having the right screwdrivers. I've done one in a 2012 MacBook Air, but the same procedure works for newer models as well.
5. I use it all the time to manage separate tasks simultaneously. Between that and All-In-One Gestures, I'm staying with Firefox for the foreseeable future.
...he told you that "you shouldn't change your behaviour" in response to government surveillance. Clearly, that message has gotten across.
Source: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3F...
I picked up the VHS cassette of this about half-way through seeing it at the cinema. Thank you, Instant Cassettes!
It's ironic that you can't take high-tech spy gadgets into a James Bond film.
What if I'm turning up in costume? Then I *have* to have them.
Sexbots are going to be really, really popular.
Yeah, but they'll just date each other.
Doubt isn't the opposite of faith; it is an element of faith. - Paul Tillich, German theologian and historian
