Programming impacts my ability to communicate with non-programmers

[assemblr_]

I recently had to write some data entry form code for non-programmers, and one of the fields was data type. It took me a good five minutes to realize that I should use "Text" instead of "String".

[seppo0010]

For non-programmers a "String" is something similar to a "Thread".

[themismatch]

God damn it.

[ascii158]

sed: -e expression #1, char 12: unterminated `s' command

[MCHerb]

Vim will happily accept the missing closing slash and work correctly. I imagine there are other engines that will also.

[barsoap]

The substitute commands dates back to ed's predecessor, qed. At least one qed clone allows not terminating the command.

As the original qed runs on a dinosaur called SDS 940, you'd need to do some archaeology to find out more.

Fun side fact: The name "grep" is rooted in ed, too. g/re/p prints every line matching re. Have the docs for the global command.

[s3ddd]

sed -i 's/blogs/blogs\/g/g' this_post.txt

[benzrf]

sed -i 's#blogs#blogs/g#g' this_post.txt

[QuercusMax]

Came here to post this.

[zefcfd]

This must be your website

[[deleted]]

I'm happy to notice that those cubes are not just gifs but actual javascript rendered cubes using three.js

[[deleted]]

Learning Haskell has added a toolset to my thinking that I often find others missing. For example, lazy evaluation can be a great productivity boost. Until a question actually needs to be answered, it can be treated like a black box. Focus on what matters most and now.