You do not have the required file permissions

We exchange project files over a shared git repo on remote server and somehow I just lost write access to some files:

Error cleaning build folder

You do not have the required file permissions

Three Applications to Be Released

There are still some minor open issues, like icons, colors, title and writing webpages. Otherwise everything is just fine :) Well, besides releasing the apps, I mean. But that day is getting closer.

"Time" which shows current time and that's pretty much it. Lean, clean and simple on purpose, but I fear it might be too simple for Apple. Might have to add something to get approved, unfortunately.

"Font" application, since I just love fonts. There must be 50 fonts applications in App Store already, but wanted to do my own. Looks good, got some nice features and I have a list of things to add.

"Log" application to display in-device NSLog output. Needed this kind of application in "real work", but couldn't find any with requires features. The first release will be simple on purpose, need some feedback to decide what to add in next version. Too many choises to be made based only on single person's (me) feedback.

Why Would You Ever Need a Fax

When you want to register a new company into Apple Developer Program, you need to fax them some documents.

Fax.

Remember that ancient thingie from history classes in school? Or tech museums? Yes, that's the one. Fax.

The Curse of Version Control

Version control is a MUST for any developer - but that doesn't mean you have to use an external version control system. The importance is in the idea and attitude instead of using any specific tool.

Last week we got a harddisk crash, removing SVN version control and TRAC project management from service. Regardless of that - and summer vacations causing delay in repair - work must go on. Was shocked to realize how much I had started to rely and depend on SVN as part of normal development cycle. Suddenly I was on loose ground!

Version control without a version control tool requires certain kind of routines:

• Think before you start doing anything
• Complete your thinking before you start doing anything
• Test your thinking before you start doing anything
• When thinking is done, start doing - don't procastinate

This time it's all about you. It's all in the mind. It's personal.

• Split the work into small enough parts which you can design, implement, test and release during one cycle
• Never start anything you can't complete during same session
• Make regular backups of your progress, even local ones
• Document what you plan to do and how you think you did it
• Automate anything you can

The less you have to keep in your mind, the better you can focus. The better you can focus, the faster you get results. The faster you get results, the easier it will be to fix them.

Learn iPhone Programming by Example

Best way to learn is by example, at least for some people. Haven't checked these myself, but like the idea: 35 open source application.

ManiacDev.Com: 35 Open Source iPhone App Store Apps – Updated With 10 New Apps!

Looking at titles and descriptions, there are several I wish to check later. Might even use a few!

What would Steve do?

Developer is not "The User". He is biased towards his own comfort zone and all designs, decisions and recommendations are from technical implementation point of view:

• Feature is boring to do: users wouldn't like it.
• Feature is difficult to do: users wouldn't like it.
• Feature changes architecture: users wouldn't like it.
• Feature removes "my code": users wouldn't like it.

The question you really have to ask: What would Steve do?