timroy

1. The overall pace of the video - animations and narration - seems pretty slow. People today are used to very fast video editing.

2. You don't start to say what the product actually does until 31 seconds in ("filing cabinet in the cloud"), with further details coming about 45 seconds in, and then the rest of the video to explain yet further features.

3. There are a lot of features, which is very cool - but naturally that does make your one-sentence punch line hard to craft. Example: "HR Partner serves as your digital filing cabinet to effortlessly organize all your employee information, lets your employees keep up-to-date on office memos, and integrates payroll information." That's not that great a sentence, but some soundbite upfront would tell us that more features are coming over the course of the video.

4. Ditto on numbers 5 and 6 above. The "h with an h" caught my ear as well, as I'm US rather than Australian.

Thanks for posting this, and how you did it - we've thought about making a cost-effective video as well so this is really helpful. I'm surprised at how good this looks and sounds (unfair advantage with in-house talent!).

You might also check out spaced repetition software. I've started putting anything I want to remember for the long haul into org-drill, an SRS package for Emacs, though Anki and Mnemosyne are more well known. I even schedule articles that I want to return to.

To be fair to the book author, on page 22 he writes, "often there will be complex non-linear relationships between the parts of a biological chemical pathway."

Still, I found alex's comment very informative, a good addition to the book on that topic.

I work only with Clojure and ClojureScript (including a simple DSL which lets me write HTML in Clojure-syntax).

Error reporting in Clojure is bad - no two ways about it. Once I got used to scanning the JVM stack trace, it wasn't so bad. But it could be better.

I really prefer writing ClojureScript to JS: using one language, with the same data structures, is a seamless experience. I like writing HTML in Clojure data structures, as it makes manipulating the data much easier.

But your mileage may vary here! Clojure won't be my last language. :-)

Calculus and chemistry.

I used this book to get started with Clojure, and I can't imagine learning Clojure any other way. I still refer to it, most recently for multimethods. I used to search the website for updates before they were officially released (like core.async, iirc). Vividly and clearly written, and very funny.

I'm also an Emacs guy, but I agree with the post's assessment of the complexity of starting out with Emacs vs. another editor.

I prefer Emacs because it is so easy to switch between buffers holding different files, or different places in the same file, because it has keyboard macros, its infinite customizability, Org-Mode, etc., etc.

But that's a lot to learn, and if you are trying to learn Clojure, you should use whatever allows you to focus on the language itself.

I finished my job three months ago, and my wife and I are working on a startup together. I'm learning to code, she's about to start, and we're planning the business together. Since we're both lawyers, we're also planning our law firm together (extend our runway).

I figure cofounders are practically married anyway. You might as well actually be married.

Suppose we were both in the same company, but only one of us in the company leadership. It would be a little funny, maybe, to have an "in" with the person in the leadership. I like that my SO is also my co-founder. Fewer lines of influence to keep track of. Larry is now CEO of Google, but they'll always be Larry and Sergei - the cofounder relationship never goes away.

I've heard people say to "keep your money and your honey separate", but sex isn't magic and girls don't have cooties. Lots of friends aren't suitable to work together, lots of couples aren't suitable to work together. We met on a project in law school, which was a hint we'd be cool working together.

I've met at least one other couple who runs multiple enterprises together and has done for many years. I find that encouraging.

Right now, I'm further along with coding. She's got great networking skills. We're enjoying the advantages of seeing each other a lot. When the startup takes over our lives, I think it'll be helpful that we share it. We have a very calm, open way of communicating, so I think we'll do okay with all the stresses of high-speed, low-info decision-making and other crap that comes with starting a company.

I dunno, don't really have any negatives, but to be fair it's early days. We like it though. Good luck!