Apple’s Open Office

Managers and bean counters tell themselves all sorts of pretty lies to justify open office plans. It will increase collaboration, they say. Employees will know what the rest of the team is doing and be better able to solve problems, they think. Yet, somehow, despite all the putative benefits, these managers virtually never think it’s a good idea for them. That’s because deep down they know it’s really about being cheaper and they won’t have to endure it so why not?

Sadly, Apple has joined the list of companies that should know better but don’t. Their new headquarters is going to feature open office space for engineers, developers, and other employees. The employees aren’t happy. Some of those employees say they are planning to or considering leaving the company. It’s those engineers and developers that have made Apple the success it is. Inflicting the horror of an open office on them seems like an ungrateful—and ultimately self-destructive—thing to do.

Posted in General | Tagged | 5 Comments

A Little Red Meat for Emacsers

I don’t have anything interesting to say today so here’s a little red meat for Irreal’s Emacs lovers:

Posted in General | Tagged | 1 Comment

A Personal Emacs Package Repo

As longtime Irreal readers know, I don’t worry about my init.el very much. Rather than organize my configuration into separate, function-specific files like my more organized colleagues, I just throw everything into a single init.el. I keep thinking I should at least turn it into an Org file but until then, I’ve settled for converting my package configuration to the excellent use-package.

Dave Pearson is the anti-me. Not only has he broken out his configuration into separate files, he also took all those personal functions that most of us accumulate, packaged them up, and installed them in his own personal package repository. He hosts the repository on GitHub so it’s easy for him to sync his configuration to different machines.

If that sort of thing appeals to you, Pearson has written a how-to on building your own personal repository. It’s a straightforward procedure. The hardest part is probably building the packages that hold your functions. The nice thing is that once you’ve set up the archive on GitHub (or your favorite such place) you can start converting your functions to packages and uploading them at your leisure. Again, if this sounds like something you’d like to do, take a look at Pearson’s how-to for the details.

Posted in General | Tagged | Leave a comment

Note Taking with Org Mode

Heikki Lehväslaiho has a nice series of 4 blog posts on how he takes notes with Org mode. He lists the first three posts in each entry but not the fourth; it’s here.

The last two posts are particularly interesting. He talks about how he takes notes from his Elfeed buffer and from his phone. Elfeed has some built-in methods for capturing links but Lehväslaiho’s method makes it speedy and easy. If, like me, you’re more interested in forming Org mode links, it would be easy to slightly modify his elfeed-link-title function to make the link and perhaps query you for the link description instead of using the title.

If you’re using an Android phone, Lehväslaiho shows how to get notes from the phone into an Org file using a package he wrote. Sadly, it doesn’t appear to work for iPhones

Posted in General | Tagged , | 1 Comment

WeChat

Those of you who been following Irreal lately know of my fascination with the WeChat mobile app and its use in China where it serves as a wallet and messaging service. Chinese users pay for practically everything with it, use it to access government services, and for more mundane things like haling a cab or texting a friend.

I love this idea and wish we has something similar in the West. I don’t care so much about having every function in a single app but I would like to have something like Apple Pay that worked everywhere. If I have to use the Uber app to get a ride, that’s okay. The MIT Technology Review has an interesting article asking if WeChat can thrive in the U.S.

The answer so far is maybe not. Just as Western companies often have difficulty penetrating Chinese markets, Tencent, the maker of WeChat, has had limited success in penetrating markets outside of China and what success they have had is mostly with ethic Chinese traveling abroad. Part of that is that although I can download the WeChat app, I can’t link it to my bank account so I can’t use it to pay for things. On the other hand, there are already lots of successful social and messaging apps available so it doesn’t make a lot of sense to start using WeChat. That is, the network effects of the incumbent players inhibit Tencent from gaining traction in the West just as WeChat’s dominance in China would prevent, say, Facebook from succeeding in China were the Chinese government to cease blocking it.

If you’d like to learn a bit more about WeChat, take a look at my two previous posts about it. WeChat or something like it is in our future and it can’t come too soon for me.

Posted in General | Tagged | Leave a comment

Magit Bisect Tutorial

The other day, I wrote about Guowei Lv’s two very nice tutorials on using Magit rebase. Now Lv has another tutorial out on using Magit bisect. When you’re trying to track down which commit introduced an error, the Git bisect function can greatly reduce your work (\(\log n\) versus \(n\)). I’ve used it from the command line a few times and it really helped.

I’ve never used it from Magit because I wasn’t sure how to do it and in the heat of the moment, it just seemed easier to use the command line. Lv shows, that was just silly. As usual, Magit makes using Git easier and you can do it right from Emacs.

Lv’s tutorial looks at a toy bug and first runs through the bisect process from within Magit manually. That’s pretty nice but of course you can automate the process further if you can test the commits with a script. Lv reruns the bisect process using a script for testing the commits and the process is almost completely automatic.

As with rebasing, bisecting might be something you don’t use that often. If that’s the case, it probably makes sense to bookmark Lv’s tutorial so you can refresh your memory as needed.

Posted in General | Tagged , | Leave a comment

Fence Edit

There are, I suppose, reasons that an Emacs user might need or prefer to use Mardown rather than Org mode. A popular reason is that some blogging platforms want their input in Markdown and writing directly in it rather than Org mode, saves the extra exporting step. One very nice feature of Org is the ability to write code snippets in a separate buffer that has the mode of the language you’re writing in.

This is an example of the org-edit-special functionality, which is actually more powerful than just conveniently editing code; take a look at its documentation to see what else it can do. Aaron Bieber, whom I’ve written about before, has brought this functionality to Markdown with his Fence Edit package. Actually, it’s a little more general than merely being a code editing facility for Markdown: you can specify—with regular expressions—the beginning and end of a code snippet and Edit Fence will bring up an appropriate editing buffer for you. Take a look at the README file for the details.

This is really nice. At first it doesn’t seem like much but once you start using org-edit-special you don’t want to go back. Bieber’s package brings the same functionality to Markdown and other situations where it’s convenient to edit a code block in a larger document.

UPDATE [2017-08-12 Sat 19:50]: Fixed link to Fence Edit.

Posted in General | Tagged | 2 Comments

Tips for Writing LaTeX documents

Speaking of \(\LaTeX\) —as we were yesterday—Diomidis Spinellis, who’s the Editor and Chief and IEEE Software and who has written hundreds and papers and books in \(\LaTeX\) has a nice set of tips for writing LaTeX documents.

He has the usual advice about using the \(\LaTeX\) language but also mentions such things as source control, make files for building documents, style files, and recommended third-party packages. If you are writing with LaTeX, it is well worth your while to take a look at Spinellis’ advice. It’s relatively short and mentions all those little things that I, at least, always forget—do footnote indicators go before or after punctuation, for example.

Posted in General | Tagged | 8 Comments

Finding Unbalanced LaTeX Delimiters in Emacs

Here’s a handy tip from John Cook’s \(\TeX\) Tips Twitter feed (see here):

Posted in General | Tagged | Leave a comment

Lisp Runtime Redefinition

One of the things I love most about programming in Elisp is what I (and others) call interactive programming. You can write a little snippet of code—even as small as an expression—and try it out immediately without having to build any special test scaffolding. Working this way, you can incrementally build up to your final code by adding more and more snippets to it and trying things out as you go. This previous post of mine points to two brilliant examples of this. In terms of Emacs itself, you can change one of it’s core functions and have the new version take effect immediately without restarting Emacs or doing anything other than a Ctrl+x Ctrl+e.

I recently stumbled upon an old post by Tibor Simko in which he expands upon that idea by talking about runtime redefinition in Common Lisp. It’s a really great post and helps explain why Lisp languages are so much fun to program in. Even when you get a run-time error, you get dumped into the debugger where you can fix the error and take up the computation exactly where it left off except with the corrected code.

Simko illustrates this and more in his post. Even though it’s almost 15 years old, it’s as relevant and interesting today as when it was first written. If you have any interest at all in Lisp languages, be sure to take a couple of minutes to read it.

Posted in General | Tagged , , | 1 Comment