I was looking at new stuff coming in ES7 and ES8; you know, stuff that weirdos like me do. And I came over a very cool pair: padStart and padEnd. You can run it on any string and it will pad the end or the start with a string x times. It works like this:
Looks like a great option when you just want to add X of something either before or after a string.
The latest in hospital fashion
There are some obvious advantages to using immutable data types. I personally think it is much easier to understand immutable code, and much easier to understand. The reason is that you replace data, and you omit the problem of two methods in a class trying to mutate the same thing. For example by incrementing a int twice or changing a boolean to the opposite twice.
The reason you can avoid this problem with a immutable data type is that you would instead of changing the data, send the initial data set to the function, make a copy and then return the mutated copy, that you replace the original data with.
Knowing that the result is always input + the code, and know that something else can’t be doing something weird in the background makes many thing a lot easier.
Immutable.js is one way to
a part of the language. I’m not using Immutable.js at the moment, but I
have tested it out to a great extent in the past. And there are many
great things about it. For example to test if two objects are the same
by doing obj1
= obj2 is awesome.
I agree on the basic premise. But I would have preferred something like a babel plugin, that let me use Immutable data structures without having to use a separate API.
I guess most beginners start out with the assumption that a “raw” file is just a fancy image file. But learn as they move on that it isn’t really a image or a picture file like a jpeg, but rather a huge collection of data that one can use to generate a image.
RAW files are big and powerful. Especially big.
Most people probably start out with a single lightroom library and then they shoot, import, remove the pictures you don’t want to keep and continue like that until their laptop drive is full. And then I assume many people do like me, move it to an external drive and start a new one. And continue that process for way too long. A better way to go about it is to add your external drive to a library on your internal one. One library is easier to navigate, and there aren’t really any good reasons to keep multiple ones.
If you import some raw files into lightroom as they are. And don’t do anything but adding the files. Then the experience isn’t the best, because then lighroom have to generate a JPEG preview every single time you open a new file. A better way to do this is to generate previews. Lightroom has three different previews, standard, 1:1 and smart. The standard sized preview is used when you look at a grid of photos and when you look at a single image (before you zoom in) and the 1:1 are used when you zoom in. While a smart preview is a small, lossy raw file that you can use to edit your photos (when the external drive is offline or if you want better performance).
I personally generate standard sized preivews for everything; they don’t take up much space; and makes everything a million times more enjoyable. And I also generate smart previews for everything because they don’t that up that much space and makes it more enjoyable to use Lightroom.
Then I also generate 1:1 Previews that I keep for a limited time, when I process images, and I re-generate them for selections of images when I work on them. Be aware: they take up a shit load of disk space, but makes it much faster when you zoom in and compare a lot of images. My workflow is that I discard them as soon as I don’t need them anymore.
The notebooks I have been carrying as of late – I don’t remember exactly when I re-added the pocket sized notebook to what I carry – but it has remained the same since then.
I carry one Nock.co pocket sized notebook, one Leuchtturm1917 Bullet Journal, one Leuchtturm1917 Lined A5 and a regular sized Traveler’s Notebook filled with lined refills.
The reason I carry two different lined notebooks is that one of them contains drafts for various long form stuff I am writing, while the other is just journal entries.
I have decided to do something about this. What I’m going to do short term is to use up the last lined refill for my Travelers Notebook, before I move over to just using the Leuchtturm1917 and then I’m going to move back to using the Travelers Notebook.
As always, I might go back, if that makes sense. But at the moment it feels light to slim things down a little bit. And only carry one notebook for each thing, instead of two for long form writing. x
[@helgeg]1 where would I start if I was going to get into fancy keyboards?
Cleaning my office, and found my iPhone 4s. Still my favourite.
[@jack]1 what’s your favourite 35mm films?
I can’t wait until I get the chance of using this one. In functional programming languages like F# it is common to do things like “64 |> sqrt” instead of “sqrt(64)”. The value of it might not be as clear with the simple example I gave above.
But it can make more complicated chains of function calls much easier to understand and maintain because of how composable the syntax is. And not more silly syntax errors because you forgot to add or remove some opening or closing parentheses.