|
|
Dan Colasanti wrote:
Yo mama!
Hey now, that one's mine[^]! 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
|
|
|
|
|
Hi guys,
I'm not in the wrong place - this isn't a request for help... it's just a question to XCode developers out there.
If you were in an interview, without access to the internet or any reference manualls, would you be able to convert the following C# code into Objective-C ?
DateTime dt = new DateTime(2014, 12, 25); int nextYear = dt.Year + 1;
I know, it's dumb.
I'm just interested in knowing how many of you could program that in XCode, off the top of your heads.
I've been working with XCode for almost two years, and my reaction to that problem would be to reach for Google. And I'm not alone. 22,000+ readers have read the following CodeProject article, and if I was given this task, that number would increase by one.
iPhone OS: How do I create an NSDate for a specific date?
And extracting the Year from an NSDate variable ? Same thing again. I'd need to ask Google's help.
And don't even get me starting on mistakenly comparing two NSDates using the less-than or greater-than symbol (it'll actually compare the two pointers, rather than the dates..)
I just wonder why Apple doesn't, at some point, just try to make their existing SDK a little more.. finished, rather than adding 4,000 new SDK functions to the forthcoming iOS 8.
UIViews ? Let me set just the height value (yes, yes, I know I can write a category function to write this code myself)
And so on.
Mike
Frustrated (and reluctant) XCode developer
|
|
|
|
|
Asking this kind of question makes sense if you are to write a highly classified application where you can not have privilege to access network (yes, it sounds absurd but that's only reason I can think of). Still, you can have access to basic help material that usually comes along with IDEs and frameworks.
I would simply say I can't do it without even trying. My reason, stupid one, is that I may make a trivial and irreparable mistake. May be interviewer will ignore that if at least the approach is correct. May be he wouldn't.
I would probably ask about the development environment I will be working on after saying I can't so this.
|
|
|
|
|
It's probably easier with Swift. Just guessing here, as I haven't used either.
|
|
|
|
|
People still program for Apple systems? What is this, 1985? 
|
|
|
|
|
Just folks who are interested in making money. Remember, Apple and Samsung make over 95% of the profits in the cell phone industry - and Apple makes the majority of that. It's not market share that's important, it's what you take home.
According to my calculations, I should be able to retire about 5 years after I die.
|
|
|
|
|
Frank Alviani wrote: what you take home
Yes, and making lots of money will help you with that. 
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
MikeGledhill wrote: I'm just interested in knowing how many of you could program that in XCode, off
the top of your heads
Not me, but frankly I couldn't come up with the C# version either without googling, and I spent a few years with C# as the primary language.
|
|
|
|
|
without google and without my gists I would probably be stumbling with Intellisense.
|
|
|
|
|
maybe start out with...
NSDate * newDate = [[NSDate alloc] initWithDate:@"12/25/2014"];
[newDate setYear:[newDate year] + 1];
stuck at work right now so don't have my mac to verify this. I wonder if there is ObjC fiddle web site??
|
|
|
|
|
|
|
|
New job, perusing one of the dozens of databases we use on a daily basis. I found:
0) All of the views in at least one of our databases includes this:
SELECT TOP(100) PERCENT
...
ORDER BY...
Evidently, the first line enables you to trick SqlServer 2008 (and earlier) into allowing the ORDER BY clause in a view. Of course, newer versions of SQL Server ignore both clauses, and IMHO doing ORDER BY in a view is kinda pointless anyway
1) I encountered a view that has 519 OR clauses that evaluate the value of 20 columns. When run in its original form, it took 11 seconds to execute and returns 2900 rows. I modified it to declare a varchar variable and then called CHARINDEX for each column one time, and execution time is now < 1 second.
2) I encountered another view like the one above where execution time was 4 seconds, and using the same technique, I reduced it to < 1 second.
3) Formatting of the SQL I've seen so far is, well, abysmal - and that's me being nice .
I consider my SQL skills to be slightly above the beginner level, but jeeze...
EDIT =======================
I'm surprised nobody has yet pointed out that you can't declare local vars in views (ask me how I know). 
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 20-Jun-14 10:55am.
|
|
|
|
|
If the SQL is at that level, there's a fair chance nothing is indexed either (or the indexing is crap), might be somewhere to look next and win some points!
|
|
|
|
|
0) I agree, a silly practice. I've seen it occasionally.
3) The worst I've seen were obviously created by the designer. 
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
Following a few 'best practices' in MS SQL makes a world of difference vs just getting the job done. Most folks just git 'er done and can't be bothered to spend a little time doing research. On top of that, a lot of companies have DBA's that don't even review the code the developers plug into the DB.
I'm not sure what their real job is... but it involves maintaining the system without being aware of what the system is doing.
|
|
|
|
|
John Simmons / outlaw programmer wrote: I encountered a view that has 519 OR clauses that evaluate the value of 20 columns. When run in its original form, it took 11 seconds to execute and returns 2900 rows. I modified it to declare a varchar variable and then called CHARINDEX for each column one time, and execution time is now < 1 second.
Congratulations - you've just ensured that SQL won't be able to use an index on any those columns to process your query! 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I'm not sure if that's a "Bad Thing" (TM) given the improvment thus far.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Regardless of the improvement seen, is the solution offered the best solution available?
Bear in mind, somewhere down the road, someone will look at the solution offered, decide is was the best option, and use it again (possibly in an area where it doesn't make sense to do so).
|
|
|
|
|
Perhaps not a bad thing per se; but it does suggest that there is room for farther improvement as time permits.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
|
Have you already discovered you need a new DBA? 
As for 0, but I believe you already know that, you can't 'trick' SQL into ordering your views.
When you use a TOP(X) PERCENT SQL needs to know what it need to get the TOP of. The only way to make sure you always get the same records (given none are deleted or inserted) is by ordering the query.
Within the TOP(X) rows order isn't guaranteed. In practice it will be ordered about 100% of the time though (unless you do a TOP(100) PERCENT, because SQL will know that's everything so it won't have to order ).
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
