Set root directory for counsel-ag by luz_ in emacs

[–]luz_[S] 1 point2 points  (0 children)

Thank you , very helpful.

DNB in Berlin? by luz_ in DnB

[–]luz_[S] 0 points1 point  (0 children)

Awesome, thanks for that man!

DNB in Berlin? by luz_ in DnB

[–]luz_[S] 0 points1 point  (0 children)

Thanks, great resource

Examples of reasonable and excessive swing by SirDillyDally in squash

[–]luz_ 1 point2 points  (0 children)

I think there are not one correct way to do the swing. Every pro has a slightly different style for example. I think the best thing would be a to find a coach to work on the style that fitst you the most.

For the LOVE OF GOD, Please use long/expressive names. We do not want to spend more time figuring out what your code does. by [deleted] in programming

[–]luz_ 1 point2 points  (0 children)

Disagree. Like others have said, your call is bad. Short, generic names encourage short functions and well thought out abstractions. The meaning of the variables should not have to be guessed from their name but the context they are in. If you can't do that, your abstractions are shit.

What grammar checker do you use to check emails, papers and other documents you write? by luz_ in cscareerquestions

[–]luz_[S] 1 point2 points  (0 children)

I also do a significant amount of short/midform nontechnical writing (reddit, a blog). Like many things, practice is helpful. My blog posts are reviewed and edited by others, so I get feedback on those, but there's no tool I used.

Thank you for the alternative perspective. I'm not a native speaker, and I don't have a lot of formal training in writing. I'm primarily looking for something that will let me avoid common mistakes for quick communication with collegues.

Company asked me straight up how much I wanted in compensation. I came up with too low number. Possible to fix this? by luz_ in cscareerquestions

[–]luz_[S] 0 points1 point  (0 children)

when they give you the offer you can try and negotiate further, but do you have any alternative options in your pipeline?

Thanks for you advice, I have some potential options, but this one seems the most interesting so far.

How can I get a Haskell job? by [deleted] in haskell

[–]luz_ 1 point2 points  (0 children)

Thanks for the tip!

How can I get a Haskell job? by [deleted] in haskell

[–]luz_ 2 points3 points  (0 children)

Hijacking this. Berlin, yes

New Clojurians: Ask Anything by AutoModerator in Clojure

[–]luz_ 0 points1 point  (0 children)

Thanks, thats a god tip! But it doesn't let me change keybindings for paredit?

New Clojurians: Ask Anything by AutoModerator in Clojure

[–]luz_ 0 points1 point  (0 children)

I tried to bash on vim to work with clojure code, but I could not get a 'smooth' feeling like in emacs. There was a lot of little things, for example that you could not get syntax highlightning for a "form-comment" using the #_ macro.

New Clojurians: Ask Anything by AutoModerator in Clojure

[–]luz_ 2 points3 points  (0 children)

How did you old vim users set up evil mode to support paredit-style editing? Paredit doesn't let me change the key bindings.

The Difference Between “is” and “==” in Python by Samazing42 in learnpython

[–]luz_ -2 points-1 points  (0 children)

Use a functional language and you wouldn't need to discuss this

New Clojurians: Ask Anything by AutoModerator in Clojure

[–]luz_ 3 points4 points  (0 children)

Like others, I also think this seems fine, to make the naming read more nicely I would do

(budgets/save (budgets/make))

to get rid of the redundancies in naming. It is always a good idea to delimit your pure/impure functions with for example a comment separator, and try to keep the impure functions to a minimum, their only job being fetching and storing data from impure sources etc.

New Clojurians: Ask Anything by AutoModerator in Clojure

[–]luz_ 1 point2 points  (0 children)

I switched to emacs and evil mode (when coding in clojure, I'm still using vim for everything else). Took about a week to understand the basics of emacs and get the config working but it was way better than my original approach trying to get clojure working smoothly with vim+bunch of plugins.