d0

11 ms·

61.
by d0 13y ago
We didn't really. They, respectively, didn't finish the entire test, over-engineered a few of the other questions and failed the comprehension test (we test the ability to understand requirements as well). The thing is clearly mar
62.
by d0 13y ago
Agreed. It definitely shouldn't be inevitable. I left Go off that list precisely for that reason.
63.
by d0 13y ago
This. This is such a common problem, I added it to our formal code test. We supply an interface, a unit test and a rather broken CSV file and they have to make the test pass by adding the implementation. 22 people failed the test entirely,
64.
by d0 13y ago
Regarding date and time stuff, everyone appears to use Joda-Time: http://www.joda.org/joda-time/ If you want inconsistent, .Net framework's collections and HTTP stuff was the worst for years. They added to the for
65.
by d0 13y ago
COM is different. The interfaces are well defined between components and processes. In .Net, any contracts that break between layers in your dependency chain force a rebuild of all layers above it. This is not unusual in .Net projects as th
66.
by d0 13y ago
Sorry if I came across as condescending. Agree with respect to inheritance. I tend not to find any terrible libraries these days. I think people have developed some clue in the last decade.
67.
by d0 13y ago
Or a singleton that exposes a service locator (which is the pattern I've been using in Cocoa).
68.
by d0 13y ago
I'd say the grass was less yellow :)
69.
by d0 13y ago
You're right. 100% right -- I agree with you. Let me break it down into to separate points which are better described. The problems with the project scaling are primarily down to the infrastructure: MSBuild and the C# compiler are damn
70.
by d0 13y ago
Yes exactly that. The difference is that your Objective-C/iOS application doesn't consist of thousands of threads which require synchronised access to these objects. It's a pretty static thing with an event loop. Possible a c
71.
by d0 13y ago
Well spotted. To be honest, I'd be pissed off if I found out GCHQ had repurposed my project for this sort of thing. Not really possible to fix this situation either as "do no evil" license clauses are pointless.
72.
by d0 13y ago
As a knowledgeable Microsoft basher, you're right. MVC is better but still a long step away from something great. Some of the internals are crazy bad from attribute thread safety to the numerous singleton piles of crud like the ViewE
73.
by d0 13y ago
This. We just blew away 50 licenses because on our project it's a hindrance even on our E5 Xeons with 24Gb RAM and SAS+SSD disks.
74.
by d0 13y ago
Same here. Unfortunately I've been living here for over three decades now...
75.
by d0 13y ago
Excellent point. HashSet<Player> then.
76.
by d0 13y ago
Yes like those cheap plastic thinkpads with roll cages and titanium chassis that last quite happily for over ten years...
77.
by d0 13y ago
That's great - didn't know that. Thanks for posting.
78.
by d0 13y ago
Is it any harder than this? class Team { List<Player> players = new List<Player>(); public void AddPlayer(Player player) { // rule checks here players.add(player);
79.
by d0 13y ago
Much like most things in life, it takes practice and intelligence. The negative aspects are primarily because people haven't practiced enough or are being idiots. TDD is absolutely fine with OO. We have no problems with ~2 million line
80.
by d0 13y ago
Do you actually live in London?
81.
by d0 13y ago
This sort of stuff is why I buy an OS LandRanger map of the area in question before I rent/buy. Waterways, reservoirs and elevations are really quite important! London isn't that well protected either despite much fanfare about it
82.
by d0 13y ago
Although if you argue in the Apple store for long enough and loud enough about how shitty their kit is, they usually replace it anyway to get you to shut up. This is a powerful tool :)
83.
by d0 13y ago
Problem is that all my customers are consumers and want repairs. And 3-4 years is if you are lucky. Macs are pretty reliable but when they do go wrong, it's always expensive and catastrophic. A good friend of mine worked in an Apple St
84.
by d0 13y ago
Yeah they end up with a Samsung 840 (Pro if they can afford it) and if a Mac a copy of TRIM Enabler is used. Usually results in repeat customers when they see the difference :)
85.
by d0 13y ago
Couldn't agree more. Not many of us can afford to put down £65/month on a device that lasts a couple of years though. If it lasts 4 years, that's £33/month. Much better. Edit: I expect 5 years daily 8 hour usage from any
86.
by d0 13y ago
Very good question. The only thing I can think of, at least in the EU, is get them to consider repairs in electronic waste legislation. If a device is not repairable, it becomes waste. I know people are going to chip in here and crow about
87.
by d0 13y ago
I'm always fixing stuff. Simply because I hate throwing away tech due to some shitty design flaws or a minor component break. So far in the last 12 months: MacBook Pro disk failure (easy), Nokia 820 glass (easy), Sony Vaio VPCJ1 overhe
88.
by d0 13y ago
That's more expensive and they need to other bits to be shitty to help the war-driven economy.
89.
by d0 13y ago
It was until the day it was down last year. At which point it was hopeless for nearly a week. I was on the end of a down system deployed to Azure as the technical contact. Not fun.
90.
by d0 13y ago
I will be reasonable. However I would have said that face to face. Apologies if I have offended anyone.

More ›