hjertnes.blog

Where Lightroom CC have to improve.

10.08.2018 10:00

Lightroom CC have become pretty great. It is a fresh version of Lightroom where most of the heavy operations happen in the cloud. This means that you can get away with cheaper hardware if you have a good internet connection; or even an iPad.

But there are a few areas where I wish they would improve. Some of the very basic editing features still miss. The big thing however, is that they got to fix batch editing. One of the things that drive me nuts, and have been ever since it first came out is that I can’t tell it to auto tune all the images I have selected. Or most other things I often do on many pictures at once. The only way to solve it that I have found is to make keyboard maestro macros that look for a pre defined number of times.

#

09.08.2018 12:04

Liked: figwheel.main template | figwheel-main-template

#

09.08.2018 11:52

Liked: Tutorial | figwheel-main

Learning Clojure could make you a better Java or C# programmer.

09.08.2018 10:00

When you get into Clojure, you get really good at doing some stuff. Like for example writing small functions that do one thing really well in as little code as possilble, while still being robust. A part of this means that the function itself is made to be used together with other functions.

I think this will make you a better programmer in any langage. Because you kind of learn or get into the act of just writing a lot of small functions that you use all over. Instead of writing the same stuff over and over.

That is the first way where you become a better programmer. The other is about data. Once you get into the idea that data is not something that is changed, it could become something you use a lot in any language to avoid weird bugs. It is a lot easier to write immutable code with Clojure than other languages, because their api have been made to do just that. But you can still do a lot to move in that direction in most good languages (I’m looking at you Python).

#

09.08.2018 09:04

Liked: Clojure job at Apple

#

09.08.2018 09:01

Liked: https://blog.emojipedia.org/emojiology-grimacing-face/

#

09.08.2018 09:00

Liked: Blogging with Emacs org-mode

#

09.08.2018 09:00

Liked: Lisp: Common Lisp, Racket, Clojure, Emacs Lisp - Hyperpolyglot

#

09.08.2018 08:52

Liked: OmniFocus 3 for Mac Sneak Peek | Rosemary Orchard

Just got my invite, can’t wait to really start using the new tags.

SQL Injections

08.08.2018 10:00

This used to be the big security thing everyone safe guarded against back when I was learning how to write code.

There is even a XKCD strip about it.

The basic idea is that input from a user is used directly to construct a SQL Query, and that can therfore be used to for example drop tables in your database.

I personally think this is a non issue today. Well, I think the issue still exist, but I do not think that it is anything that anyone should be the victim of. Because all programming languages have (or should have) libraries for most SQL databases that take care of this problem.

The way they take care of it is by the way to create the query. You write the query, and where you want to place dynmaic data, then you give it all the variables after that. By doing this you make sure that all the data in the variable are always treated as data and not as a query.

In other words: this should not be a problem as long as you use a good library, use it in the recommended way. And don’t create the queries in a dumb was (something like "select * from table where value”+variable_from_url=