HN user

jh3

414 karma
Posts5
Comments201
View on HN

Wow, so "two bits" is what Roger says in response to Judge Doom in Who Framed Roger Rabbit. I can hear it now, but I never actually knew what was said.

I thought Drupal 6 and 7 were great, but this was about 5-10 years ago. Haven't looked at it since then. It was the first CMS I worked with professionally, so I may be biased, but once I "got it", it became quick to add features (not "Features", which wasn't very fun). This was before everything went headless and javascript :)

Ten years of OP-1 5 years ago

Yeah I can see that. The one I had saw regular use when in my possession, but I had it for less than 6 months iirc. It was still in excellent condition.

Ten years of OP-1 5 years ago

They retain value. You could buy one used and sell it for more, if not the same price you purchased it at. I think the worst case is you'll essentially be renting it for $100-200 if you really don't like it. This was my experience, anyway.

It's a great device even if your job isn't music production. Easy to use, lots of fun, though I didn't enjoy the form factor.

Squash your commits 10 years ago

I still fucking hate rebasing and get tripped up by it on the few times I end up having to deal with it.

When I had no understanding of what was going on, I didn't like it either. Now that I use it frequently, I understand it better, so I don't hate it anymore.

I like running `git rebase <main-branch>`, where <main-branch> is typically master, in my-new-thing branch because it lets me deal with any conflicts from upstream one by one.

I also like running `git rebase -i` in my-new-thing when I have a bunch of commits with redundant messages that I want squashed into a single commit before I push the changes. Basically anything that requires messing around with a range of commits is a good use case for `git rebase -i`.

Why do you hate it so much? There's really not much going on that you should have to hate. To me it's like a bunch of small, compartmentalized merges.

You don't see structural engineers slapping together the first thing that works and patching the building later when parts of it fall down.

That's because if they mess up the first time people can die.

I'm guessing the likelihood of death due to a bug in most web applications is probably much less than that of a bridge :)

Software is great because it's possible to iterate quickly. But ultimately, you have a point. Developers should be willing to fix bugs they've created and/or come across in their projects. We should also try to limit the potential of bugs by releasing small chunks of functional work as often as possible. "Releasing" in this sense can mean to production or just to your qa/test/dev/stage environment. It's just important to have many eyes on the product before it's live.

project_root/sites/example.com

project_root/sites/example.com.a

project_root/sites/example.com.b

project_root/sites/example.com.a.123

project_root/sites/example.com.a.234

Create these directories. Add a settings.php file to each. Add stuff to sites.php if needed. example.com.a and example.com.b should definitely work. Not too sure about the other two because I haven't created a site in a multi-site setup that is 2 subdirs deep, but it is easy enough to try.

You may also need to symlink the subdirectories (e.g. a) in project_root. See "Subdirectory multi-site" here: https://www.drupal.org/documentation/install/multi-site

A Good Vimrc 11 years ago

Here's what works for me:

capslock remapped to ctrl jw for escape in vim

jw is convenient if capslock is used as a control key. I had to pay attention to what I was doing in a vim file in order to remember what I had escape mapped to :)

I remember reading Timeline and Prey in high school. They were amazing books to me at the time. I just couldn't put them down. I never cared too much about how scientifically accurate they were though. That's like complaining about the plot holes in Back to the Future. It's entertainment, so to me he did his job well.

Committing often allows you to remember the small changes you made throughout the feature. If you let a file sit in the staging area for hours, days, weeks, you will most likely have a hard time remembering why you made all the changes.

Is there a way to do this with the staging area? o.O

bdunn on justifying your costs as a freelancer: https://news.ycombinator.com/item?id=8705179

patio11 and the Fair Credit Reporting Act: https://news.ycombinator.com/item?id=7135833

spolsky on detecting toxic customers: http://news.ycombinator.com/item?id=1987223

tptacek on naming your company: http://news.ycombinator.com/item?id=4684845

The journey of Flappy Bird: https://news.ycombinator.com/item?id=7207943

Programming is terrible: https://news.ycombinator.com/item?id=6469360

On being a consultant: https://news.ycombinator.com/item?id=6443135

Why Do So Many Incompetent Men Become Leaders? https://news.ycombinator.com/item?id=6263458

Are designers crazy? http://news.ycombinator.com/item?id=5002262

Why learning to code is so hard: https://news.ycombinator.com/item?id=4933178

"I don't understand": http://news.ycombinator.com/item?id=4930262

death and regrets: https://news.ycombinator.com/item?id=4540459