nephorider

IMHO, and to avoid abuse, singletons in iOS/MacOS should not be considered as a pattern that can replace class methods or simple C utility function. And this in all ways. I have seen piece of code doing everything with class methods while a set of plain C functions would have been more adequate (those were really utilities)

Pretty true! One of the met efficient way to make information go round is still to collect all and make unified report (as a manager). Still tools like internal instant messaging can improve communication.

It's not beautiful but it is likely a fun little cool object

Sure but then if this becomes a "must have simply to have the opportunity to interview" then it loses all the value it can have to reveal what the person can do. And I do believe some people have no time for this. Having worked at Apple for some time, I guarantee my sparse time, when there was some, was more outside of any coding and still I will never show outside a piece of code I have written in this company. This does not mean the coding skills I have should be considered as good or sufficient, they may or not match the one needed for a position. Having been also in the position to be on the interviewer side, especially in startup, seeing the candidate in person reminds often the deciding point.If some code on github exists, it simply can "speed up" a little this part of the process. Personally I found the "Smart and get things done" book by Spolsky a good read on how to conduct interviews

Having created (and failed) a company in Germany, it is true that the bureaucracy and paperwork is especially tough and hard to understand. Administrative German is very hard to ingest. Once started rules of work and leading a company are pretty straightforward

Some part reminded me excerpt of "Do things that don't scale" from Paul Graham in the way to create this "real" relation with the user

Awesome

Very true article. CoreData has a lot of path and legacy behind and thinking it would solve some problem magically because it is vended as "the high level problem solver" is a mistake. More than once I have seen performance problem appearing 2 weeks before release by (mis)using it.

One more would be to never give up even if you may be dead 3 hours later.

More and more scientific confirmation of "mense sane in corpore sano"

Excellent article. Wish I had this when we started working on Nephorider Putting together all in one place and with a clear vision is certainly a non easy task.

By definition C++ is a different language (contrary to Objective-C that was "an extension to C"). It encompasses a lot (nearly all) of C but introduces also new concepts. For example and besides the evident OOP features, all the different types of casting, use of IO stream, default parameters...

the "biological part" in the article is good and seems to be factual. The political conclusion looks however more"cut and paste there".

Certainly not the same, but I do believe that when a computer model is having some kind of math root, it gets its own coherency and can be developed further. By math root it does not imply a math model. but the idea of creating a set of object with given rules and behaviors like for example a vectorial space. Very often it starts with real "computer tries" but the best part are always when there is an underlying model. I tend even to believe that the level of math knowledge in modern programming has grown up in regards to 15 years ago.

I used to go with "theme" name like wine oriented (chardonnay, merlot...) But after a while it gets confusing to remember which machine does what and switch to more "functional" names like "worker01, worker02, db01..."

I usually go down through the "down to to do list way". This gives me a frame for working, and allows me to be in the state of mind of "this is a job, you signed for it, you do it"More than often some joy of working appears a few times after the struggling

Nice interviews. I really enjoyed reading the answer of Alex Haro to the last 2 days worries. It definitely conveys the fact that technical issues are one component of the job, the others being often more human-related. Software engineers often their have strong opinions (and usually for the best) and making all work together, without going in a techie fight, can sometimes be a real juggling act.