Mark Richman - Latest Comments

Re: Amazon ECS Deep Dive | Mark Richman

Mark R. — Sat, 25 Sep 2021 07:10:51 -0000

No.

Re: Passing Lists as Parameters to Stored Procedures in SQL Server –Mark Richman – E-Commerce software developer living in South Florida

James Dunne — Wed, 23 Oct 2013 12:11:06 -0000

Actually, SQL 2008 and up supports table-valued parameters, but their overhead is non-negligible and is also intrusive into your schema. You cannot "just use" TVPs without creating named types and granting permissions to those, all of which is rather unfortunate. The same goes for this type of solution as well; one needs to create the function.

Also, I'd like to see a variant involving lists of arbitrary text data with character escaping rules so that commas in the data don't get interpreted as delimiters.

Re: Passing Lists as Parameters to Stored Procedures in SQL Server –Mark Richman – E-Commerce software developer living in South Florida

James Dunne — Tue, 22 Oct 2013 16:13:54 -0000

Yup, I do exactly this type of thing with almost exactly this function code. It works very well.

Re: McDonald’s Response to Ammonia in their Meat

Villaney — Thu, 14 Apr 2011 12:43:54 -0000

Say whatever you want me and my family will never eat at McDonalds.

Re: Installing Git and gitosis on Ubuntu

Mark R. — Sat, 22 Jan 2011 15:14:58 -0000

Issues or questions about Gitosis should be directed here: https://github.com/res0nat0...

Re: Installing Git and gitosis on Ubuntu

tenach — Fri, 21 Jan 2011 18:19:00 -0000

I am getting a traceback error and am not sure what to do with it: http://tlms.pastebin.com/pQ... What would your suggestions be? I have triple-checked to make sure I am following everything properly.

Thank you much for your help.

Re: Rails Custom Authentication using Devise, DataMapper, and a Legacy Database

reedlaw — Thu, 13 Jan 2011 09:15:34 -0000

Thanks! This helped me solve my problem: http://stackoverflow.com/qu...

Re: Installing Git and gitosis on Ubuntu

Jdoerring — Wed, 12 Jan 2011 22:52:35 -0000

I posed this on the scie.nti.st article but they have a comment list a mile long so here it is again.

I'd like to add on one thing that I ran into when installing Git and Gitosis on my Ubuntu 10.10 server which I installed with encrypted home directories.

When I was configuring my server for SSH, I changed my sshd_config to include this entry:
AuthorizedKeysFile /etc/.ssh/%u/authorized_keys

From this you can see that I created a /etc/.ssh directory and a sub directory for each user containing the file authorized_keys. Also, I made the user the owner of their respective folder.

Gitosis uses a post-update hook to update the git user's authorized_keys file to include each of the public keys from the gitosis-admin/keydir. The problem was that the default location that gitosis expected the authorized_keys file to be in was /home/git/.ssh/ but I moved it to /etc/.ssh/git. To remedy this I had to add the following to gitosis.conf:
[gitosis]
ssh-authorized-keys-path = /etc/.ssh/git/authorized_keys

It took me quite a bit of messing around to figure this all out, I hope it will save someone else the pain.

Re: Rails Custom Authentication using Devise, DataMapper, and a Legacy Database

Christian Gambardella — Sun, 05 Dec 2010 06:43:31 -0000

does this work with rails 2.3.10?

Re: Installing Git and gitosis on Ubuntu

Paz — Mon, 29 Nov 2010 18:54:18 -0000

Just tried 3 other tutorials that were not clear on copying my public key from client to server and wasted 30mins. Yours got me there in 2 mins. thanks.

Re: Rails Custom Authentication using Devise, DataMapper, and a Legacy Database

Mark R. — Wed, 24 Nov 2010 07:55:15 -0000

Thanks Jared! This worked like a charm. I've updated the blog to reflect your suggestion and given you proper attribution for the find :-) I wish the Devise documentation, or at least the default devise.rb initializer that gets generated would make this setting clearer. I've paraphrased the code comment from the Devise source code in the article.

Re: Rails Custom Authentication using Devise, DataMapper, and a Legacy Database

jm81 — Tue, 23 Nov 2010 20:49:41 -0000

Mark, Thanks for posting this! I was the one who suggested the workaround at the end of devise.rb and just realized it's not needed. There's a config option I had forgotten about. Add "config.apply_schema = false" to devise.rb. I just tested it out on an app I have and seems to work fine.

Re: Rails Custom Authentication using Devise, DataMapper, and a Legacy Database

Guest — Tue, 23 Nov 2010 20:42:35 -0000

Re: Why I Never Bill by the Hour

Mark R. — Thu, 28 Oct 2010 09:05:55 -0000

Why would you do business with a client who doesn't know what they want? It's okay for them to change their mind, but your response should be a new proposal, not an hourly rate.

Re: Why I Never Bill by the Hour

12ewfgdb — Thu, 28 Oct 2010 03:20:59 -0000

This is software. It's not like renovating a bathroom where only labor is involved (choose a different tile, pay for the costlier tile, but the labor cost is the same). As long as the client is so so so sure of what he/she wants, the fixed price is a great way to go. But in software, things change (understandably so). If the client want's a change today and another 2 days later that completely contradicts the change requested, what are you going to do? Tell yourself, oh heck, now I have to start all over again, or, I know you're a small business, and you didn't know exactly what you wanted, so you know, I really need to charge hourly to make this work for both you and me.

Re: Why I Never Bill by the Hour

Michael Liberty — Wed, 15 Sep 2010 11:01:02 -0000

I agree and the point I always hear against fixed billing is it isn't flexible.

I think it is, you can easily negotiate reduced/increased costs for the client if they are adding/changing features.

Re: Why I Never Bill by the Hour

Michael Liberty — Wed, 15 Sep 2010 10:59:43 -0000

Agreed. I also think that the big argument against fixed billing is "flexibility" and how people relate that to Agile programming, but there's no reason why you can't negotiate fixed extra costs for new features of changes to existing requests that will take more time.