What I like about objective-c’s error handling approach is that a method that can fail is able to tell if a caller considers error handling or not. If the passed *error is NULL you know that that is no way for a caller to properly handle the error. My implementations usually have this logic:
if error == NULL and operationFailed then log error
Otherwise
Let client side do the error handling (in terms of logging)
I never knew what a difference good pants can make. I usually just bought my pants from H&M/other retailers or Amazon. I usually bought what I considered good value pants for like $30-80. I then, out of curiosity, bought pants that were 2-4 times as expensive (~$150) and it really made a difference. I never really liked the pants I had… they never fit right… they felt very uncomfortable. The new pants I got about 2 years ago (the more expensive ones) were very very different. Very comfy. They also had a lot of nice features that I never knew I needed but that I now want by default…
- A button that just "clicks". Most pants I usually owned had a traditional pants button. Those more expensive ones had buttons that just "clicked". Away goes the worry about a button falling off while you are on the go.
- Pockets with hidden zippers: My pants have pockets and in those pockets are smaller pockets with a zipper. Perfect to store things that are small and easily lost.
There are more "features" but those are the important ones. The most important feature is just the material that is used. I barely feel it. Also the company that makes those pants makes other things as well. I ordered a lot of cloths by now and the amazing thing is that everything they make fits me perfectly. I don't know how they do it… When I usually buy pants I have to try on like 10 pants to find one that fits. Even if I pick the "correct" size.
Never heard of them. I'm always interested in a good value. I rarely buy the cheapest or the most expensive item, so if Rhone is decent then I may give them a try. Thanks for the tip!
> I never really liked the pants I had… they never fit right… they felt very uncomfortable. The new pants I got about 2 years ago (the more expensive ones) were very very different. Very comfy. They also had a lot of nice features that I never knew I needed but that I now want by default…
I managed to get the same experience for free by losing weight.
I lost around ~9-11 kilos over the last year and a half and went two sizes down in pants (went from european size 50 to size 46, with a few more kilos to lose until i can wear 44).
It's incredibly nice to be able to pick pretty much any pair of pants/jeans my size and have it fit pretty much perfectly.
> My pants have pockets and in those pockets are smaller pockets with a zipper. Perfect to store things that are small and easily lost.
I had one with these as well, although probably not of the same quality, and I always feared the zip scratching the screen of my phone when putting it in my pocket.
there are a lot of apps that do this though… eg. git tower. Sketch. Etc. Not saying that I like it or anything. Maybe its the combination of local first + an app that seems to be trivial (I am sure it was not but if you hear "daily planner" I think its reasonable to assume that its less complex than a git client and/or an app like Sketch).
First hand knowledge:
ERGO and MunichRE both have a lot of cobol still doing the core business. You will most likely never run into the system because they just run batch jobs - sometimes configured via a “nice” web UI… you configure your job, submit and the next morning you have your report… that’s why you never actually see COBOL.
For example, Florida Bar Rule 4-1.5(a) prohibits "clearly excessive" attorney's fees, while 4-1.5(f)(4)(B) sets several criteria for contingency fees (typically the sort of fees a plaintiff's firm would charge) that, if not met, renders a fee presumptively "clearly excessive".
if error == NULL and operationFailed then log error Otherwise Let client side do the error handling (in terms of logging)