martinnormark

I've done this a little less quantitative using LLMs. Ask it to roast your API spec, give it a score. Could be expanded by more elaborate few-shot prompting: https://x.com/MartinHN/status/1775530951138746715

The awesome Brian Roemmele announced this on Quora two weeks ago: http://acceptingpayments.quora.com/Quora-News-Before-It-Happ...

Exciting times, to see what unfolds in this payment war. Apple will certainly get there soon: http://acceptingpayments.quora.com/Apple%E2%80%99s-iWallet-A...

http://acceptingpayments.quora.com/Confirmed-Apple-iPhone-Ev...

http://acceptingpayments.quora.com/Apple-Patent-Shows-How-Pa...

Thanks! I always thought it was Über :)

I'm available for remote projects.

I have previous experience with Parse. I published this app: http://itunes.apple.com/us/app/80-Mileage-Book/id873847566?m... two months ago.

I have web app experience from both business and consumer products.

Feel free to contact me: m@martinnormark.com

I only test against the final result, that I expect any public method to produce. The unit test should pay no consideration to the implementation details such as private methods.

If you want to test the fragments in isolation, split it out into a separate class that you use as a dependency. Your desire to do so is often a good indication that you should split up the responsibility.

You could say that. What I'm saying is that splitting up a function into smaller functions with good names, is way better documentation than comments.

Perfection is a trap during the early stage of a product. Get it out there, in hands of paying customers!

Perfection is the enemy of execution.

Honestly, how proud would perfect icons make you if your product didn't resonate with anyone, and you didn't get any customers within the first month? 2 months? 3 months?

Remember that you can improve week after week after week, once you've launched and you get feedback that indicates what customers want. Then you can improve the right things, which is very important.

Interesting stats.

Another advantage for cyclists is "right on red". Even though it's illegal, a lot of people does it. Sometimes the car lane to turn right is packed and you have to wait several intervals for you to turn right, and the cyclists just pass by.

The roads are small, especially compared to the US. And there're just too many cars!

Ever heard about traffic? A bike in the center of Copenhagen would beat a car at any day.

And with the car you have a parking problem as well.

Amazing. Thanks, I didn't know of him specifically but I do remember seeing his book somewhere.

This reminds me of how Microsoft added specific code to Windows 95 to ensure SimCity would run.

This is from Joel Spolsky's Strategy Letter II: Chicken and Egg Problems http://www.joelonsoftware.com/articles/fog0000000054.html

So Windows 3.x on Intel 80386s was the first version that could run multiple DOS programs respectably. (Technically, Windows 386 could too, but 80386s were rare and expensive until about the time that Windows 3.0 came out.) Windows 3.0 was the first version that could actually do a reasonable job running all your old software.

Windows 95? No problem. Nice new 32 bit API, but it still ran old 16 bit software perfectly. Microsoft obsessed about this, spending a big chunk of change testing every old program they could find with Windows 95. Jon Ross, who wrote the original version of SimCity for Windows 3.x, told me that he accidentally left a bug in SimCity where he read memory that he had just freed. Yep. It worked fine on Windows 3.x, because the memory never went anywhere. Here's the amazing part: On beta versions of Windows 95, SimCity wasn't working in testing. Microsoft tracked down the bug and added specific code to Windows 95 that looks for SimCity. If it finds SimCity running, it runs the memory allocator in a special mode that doesn't free memory right away. That's the kind of obsession with backward compatibility that made people willing to upgrade to Windows 95.

You're making a valid point, thank you very much for the feedback.

I added "Keep track of your driving and export your trips when you need to file expense reports, do your taxes or other deductions", instead of the secondary "sign up" message.

They do have pre-authorization: https://www.paymill.com/en-gb/documentation-3/reference/api-...

It says you can trigger the capture to fire a bit later, though you'd probably want that to happen when you ship an order -- which you can do with the API by creating a new Transaction from your preauthorization: https://www.paymill.com/en-gb/documentation-3/reference/api-...

Damn, what happened to the browser version?

Update It's still there: http://gettingreal.37signals.com/toc.php

Yer, they don't really say what policy Visa changed, what it involves etc.

I have this feeling that they're trying to stop the likes of iZettle, because they're working on their own payment solution -- which I don't hope!

Campaign Monitor is pretty awesome: http://www.campaignmonitor.com/api/

I see what you mean. Good point.

I agree. Never ever lose customers who are trying to throw money at you. Not only will you lose that one sale where they get the errors, they'll probably never return.

I am totally embarrassed right now. What a stupid thing to forget. Thanks for the heads up...