253 karma · joined August 24, 2016
In a similar vein, when both dog and bunny are on one field, I can't choose which one to pick up.
Now wait, how do developers develop without source control?
As an individual contributor, I consider a number of things in that paragraph good practice. Specs, say. But source control? That's just so fundamentally basic that I lack vocabulary to express how essentially important I consider it to be. How does a team get anything done without one?
> Based on the evident burn marks found within the excavated
> house and on the surrounding historical sources, Mr Kolář
> believes that the items were found in this state because
> the inhabitants may have been forced to abandon the house
> in a rush.
>
> “The working hypothesis is that the house was destroyed
> during the conquest of the city by the Hussites[...]"
OK, so that explains why the items are there at all, but /how/ did they survive unbroken for 600odd years? /Especially with a conquest going on?/Not too bad it turns out. You still have bold, italic, underline and gray. You can do an inverse text, which is good for headers (e.g. magit sections). I guess with a GUI editor, you can do things like boxes around tokens etc. -- I'm in an emacs over ssh most of the time, so I haven't looked into that.
I actually ended up liking this and have been using it since then, on a LED display.
That then would be the foot in the door for eventual full metric conversion!
Hmm, from my mechanical engineering times, 8 kP does not sound like a big deal at all.
Say it's 5 tons per elephant, which would be about 50kN. A human foot is about 25 cm long, and I guess two of them might be about as wide, so 0.0625 m^2. Pressure is force over area, so 800 kN/m^2, or 800 kP. That's per elephant.
I'm going to assume the article is missing a "mega" somewhere in there.
for ((i = 0; i < 10; i++)); do
echo $i
doneBe wary though, not all translations are created equal, there might be errors or divergences.
I remember the Russian version translated "I will go so far as to send you on this adventure" incorrectly as "I went all this way because of you" or some such. (And a number of other blunders of this sort.)
Also one of the Stephenson's Baroque Cycle books had "men-of-war" translated to Czech as literally "warriors".
It's a good approach overall though.
> Using the shortest timetable, the distance from the
> coastal centre of Porto to the Polish capital of Warsaw
> can be covered in 40 hours and 33 minutes (including time
> zone changes) with just four transfers.
Wait, what? How are timezones relevant? If I travel one hour across the date line, does it mean the trip took me minus 23 hours? Not that I don't care what time it is when I get off the train, but that has no bearing on the time that the distance can be covered in.Ha, nice, I will try this out.
> find a professional peer and become their formal editing buddy
Yeah, teams should have a review system for documentation, like they certainly have one for code review.
In practice, with many non-native English speakers in the team (100% in my case), this is something of an issue. But we do what we can :)
What tends to help me with long-standing documents in particular is to reread them after some time passes. A couple months down the line, I have lost much of the context, which makes it easier to spot problematic bits. I am also not invested in the text as much, which makes it easier to rip out the parts that have not aged well.
My experience has been that few people drive to the other side of the campus for a run of the mill chat or some random presentation. Unless it's in the same building, and unless it's something important, you just call, mail, chat, send office365 links, do skype presentations... you know, the remote stuff. So above a certain size, it's in the company's best interest to embrace remoteness anyway.
Just to make this bit clear: with effectively infinite number of pages. One would imagine that panning around infinitely large pages would be a possibility with a product like this, but the feature is not there.
Short papers are just fine. Long documents, as long as you read them mostly sequentially, are IMHO just fine as well. But trying to read something where you need to flip around a lot is painful.
One of the use cases I had in mind when buying rM was reading stuff like IEEE 802 standards, programming language standards, hardware references, etc. But with these documents, the table of contents itself can have 10s of pages. The tools for searching and moving around are there, but the high latency of the e-ink makes them frustrating to use. And hyperlinks in PDFs are not active. And you can't bookmark something to create your personal collection of pages that you often need, which would somewhat alleviate the abovementioned frustration.
I use rM daily, but just not for reading manuals. It's just not a good use case for the device.