another-cuppa

> it is still a long way for woman in STEM/Physics.

Do you know a single woman who wanted to go into STEM but couldn't because she was a woman?

This is a bit more specific than I thought it would be. Most of my projects around the house don't involve concrete.

Yeah, but the nice thing about it, and emacs in general, is you use as much as you want and the rest just stays hidden away until you need it.

I learnt emacs for org-mode and magit. If you see what org-mode can do and you find that attractive, learning emacs will just happen. Learning emacs will set your life on a new course filled with joy. At least that's what happened to me.

For me that's a reason to ditch my mobile, not ditch org-mode.

OK, implicit self in the signatures is probably OK. I don't find it a problem personally because I use snippets to generate functions and methods etc. while I write them.

> I personally wish they would just make `self` implicit

Hell no. Go use Java if you want that. If you find typing self is making you more work then you're not using classes correctly. Write functions and use classes if you need them.

Anyone reading this thinking a "bunch of markdown files" sounds like a good idea should really look into org-mode. Trust me.

The article.

> I’m not willing to give up an extra two hours of my day when I can drive in.

Right. But in the future you won't be able to drive in. So move closer to work, I guess.

That looks really great. Bookmarked.

Shame the site is one of the rather large group of sites that assume everyone's default CSS is black on white text, though.

You can do that with React too.

It's hard to explain. I know how the web works. I used to write HTML in Notepad many years ago. With Vue I just didn't know how the stuff I was writing was turning into the stuff that the web browser actually sees. React is just a JS library that you can add on to your HTML and CSS and makes sense in the standard model.

I guess with Vue I just don't feel in control any more, and that's a big no for me.

I'd been out of the loop of frontend Web stuff for several years but I tried Vue.js because I read here and elsewhere that Angular was a mess. I just couldn't stand the weird hybrid html/css/js editing. At no point did I feel I had the slightest clue what was going on and it felt like I wasn't supposed to ask. React felt much more natural to me. Is there any way to do stuff differently with Vue or should I just stick with React?

OK, but most people in the world simply can't afford that, so you must be an outlier.

The on-prem one I use has checkbox when you merge. It's unticked by default.

So? Does race matter or does it not?

Remember Atlassian in their infinite wisdom renamed the on-premises product formerly known as Stash to Bitbucket despite being a completely different code base to Bitbucket.com. I think they are talking about Bitbucket.com.

Thanks for that. I'll look into everything you've mentioned here.

As for nibs, I bought a load of different ones but the only one I got good results with was Gillot 303. Are the Leonardt Principal ones like that?

Definitely this. The majority of people I've worked with over the years have used a keyboard as their main interface but simply do not know how to use it. Learning the keyboard does more than just making typing faster. It enables you to banish the rat and achieve far greater overall efficiency.

I started to get into calligraphy. I got quite good at copperplate/engrosser's script (I was never quite clear on the difference). My script was good enough that people thought it was printed. But I just don't know where to take it from there. I feel like I need a good book on the subject. Like The Art of Computer Programming, but for calligraphy. I've been unable to find such a book, though. Any suggestions on how progress?

Programming: I've spent the longest on this but I can now use a computer to solve some of my problems.

Guitar: I like being able to make music come out of an acoustic instrument.

If it did it would be annoying to type progn all the time and someone would make a macro...

Come on. You've defined a function inside another function. It's very clear that you've done it so you can pass it to some higher level function. If someone comes along and starts using your inner function willy nilly in the outer function without anyone noticing then you've got much bigger problems that multiline lambdas are not going to help you with.

You do realise you can define a function inside another function in python, right?

I've used Lisp extensively and I've used closures extensively. In Python you can simply define the function on the line above where you plan to use it. I really don't see the need. Lisp needs lambda because you can't just randomly introduce new variables everywhere (you have to use flet, which actually is a lambda).

Why does it need that, though? What's wrong with just naming the function?

Lambdas aren't single expression functions in Lisp.

I guarantee this will not increase kernel quality, nor will it increase the number of contributions from women.

It doesn't necessarily have to come from a subwoofer. Dolby specifically states that the LFO channel does not have to correspond to a physical speaker. The LFO channel only exists to ease retrofitting a subwoofer into old cinemas (in that case they would simply wire the LFO to a subwoofer and be done). But any other channel can contain bass information and in practice a new cinema will use a bass management system to route bass from all channels into their subwoofers. In theory a cinema could also have no subwoofers at all and send all bass to the mains and drop the LFO. It all works.