meaty

Agree with Apache/nginx etc, but that is nowhere anyone needs to piddle around these days.

The accumulation of abstraction layers is an architectural problem, not a result of statically typed languages. The issue here is the author plainly doesn't understand the unit of work pattern and has made an awful technology choice (EF).

In the case provided, the whole thing was just an architectural mess.

There should be one abstraction which is the transaction and unit of work boundary in the form of a service layer so the application looks like:

controller <--> service <-> model/repository

The transaction and unit of work boundary above is inside the service. This should be entirely controlled by framework/container or chucked in there manually (see example below).

The model/repository should pretty much be whatever the native ORM interface is. it ain't worth abstracting it for shit as you're not going to change it, ever. In the case of NHibernate, which I'd recommend over anything else, your code would look like:

   class UserService {
       // ... DI crud here.
       public BooleanResult AddUser(UserTransferObject userTransferObject) {
           // Validate shit here

           // Create shit
           using (var session = sessionFactory.OpenSession()) // UOW boundary
           using (var trans = session.BeginTransaction()) // Transaction boundary
           {
               var user = User.CreateFromTransferObject(userTransferObject);
               session.Add(user);
               trans.Commit();
               return BooleanResult.Success();
           }
       }
   }

This model can be applied to pretty much everything from API endpoints, web app endpoints, message bus endpoints, queue endpoints, SMTP endpoints. You name it, without having to piss around and let your abstraction leak into the controllers.

You can add a repository abstraction in there as well if you really fancy it but I wouldn't bother.

Today, yes. Tomorrow?

We're 3 days from no food at any time.

You hit the nail on the head.

Except they also have the "back to work scheme" which means they don't even have to pay them to stack shelves in safeway (or Morrisons as it now is).

That's still twice the size of everything else.

Agreed but its the one way which requires little headspace when solving a problem.

Yes I know. We use the JVM as well and EJBs and toplink and JMS and glassfish and all sorts of hellish enterprise stuff.

People smoke. It doesn't mean its good.

This is advice. We sold 9 apps at £2.49 each.

Actually Go GC is quite easy to control. If you know your butt from your elbow you can write code that doesn't GC at all.

I really don't have a problem with GC though. Its easier to optimise a GC than to fix memory and reference counting bugs. Memory management is not a problem I want to be dealing with after 60-odd years of computers being around.

Because it requires an entire JVM of baggage, is terribly complicated and doesn't really give any benefits over anything else.

Its like a Swiss army knife with a million blunt obscure tools rather than 5 useful sharp ones, or a crazy girlfriend who has three violent ex husbands who keep coming round to your house and lives with a crackhead.

Go is a trip to your Volvo dealer - uneventful but you get what you want at the end of the day and get where you want to go and when you're done, you're done.

You might be lucky enough to break even if you charge for your app. Don't expect miracles from the win 8 app store.

Sheer arrogance makes these people think they are immune.

Plenty of people are starving today even probably less than a mile away from anyone eating well.

The system does not serve everyone equally and ultimately we may all suffer one day.

Actually some of us do it as a context switch and a tie to our roots.

Some of us, myself included consider it to be a valuable skill in an unstable world and some insurance against the fuckwits we have to trust in society.

Also the stuff tastes better.

I don't have a farm but I have a quarter acre of land in london on which I spend a fair amount of time growing vegetables (there are actually 5 of us). We don't have any grass to give you an idea.

The skills are definitely transferrable , particularly time and planning skills. Mathematics and engineering skills are almost vital for success as well.

However the most important things it gives me are peace, tranquility and space to think. I can go for a wander and come back with a fully modelled system and some potatoes :)

All skills gained are valuable in an uncertain future.

This instantly reminded me of:

http://www.gburnett.unisonplus.net/Perma/indexp2.htm

(The Industrial Cup Of Tea)

I'm not surprised.

I know no one who has upgraded to windows 8. I got 5 free copies with my MSDN sub and one got claimed before I deleted the VM. Considering I work for a Microsoft partner with 180 staff, we have one windows 8 machine and its an RT Surface used by QA. We have 4 VMs for testing as well which never visit the www at all. We have more Macs in the office!

Chrome I find to be slightly obtuse and buggy. Constant tab crashes and hangs and I'm really not sure its that fast. Friends seem to have the same opinion. One complaint I hear is that people are constantly prompted to sign into chrome. We're pretty much all back on Firefox and IE.

Meh.

A promising start is when they sell them and lots of them and people start dropping good reviews.

With Firefox OS around and with a brand name more people recognise, I doubt they will get anywhere.

I mean even Microsoft have had to work hard to get their stuff on the market.

And I was hoping for a small surface to air missile system :)

I'm considering spending some time on an anti drone technology startup. I have some ideas.

I hope they do close it - its useless unless you are dredging for comedy.

Citation for the downvoters: http://answers.yahoo.com/question/index?qid=20110910190628AA...

good. There is nothing I hate more than having to sign in to yahoo for something such as a support group for a bit of software or freecycle. Its just horrid from end to end.

He's none of Been - he just knows when he's beaten :)

I think this sort of story is surprisingly common. Most of our knowledge of such things is derived from films and books written by the victors (don't forget the UK government had a propaganda wing for WWII until the 1970s). These promote the nazis as well organised and ruthless.

In fact, much as most design by committee systems are, the nazi regime was a bit of an incompetent mess with holes left right and centre.

If you ever meet a Jew who is willing to discuss it, they usually have a relative or two who escaped to a more friendly country.

IBM are just as bad now. UK surveillance, supplying massive US defence companies. You name it. Nasty bunch.

I think the worst bit and the bit which may have lead to a lot of deaths was the shitty handling of the camps by the US and European allies.

A relative of mine, a German civilian but not a sympathizer was employed to deliver supplies to the camps. According to him, after the war supplies were cut by the allies and people were left to starve to death. People were so hungry they were eating their clothes. Those camps by then contained both nazi and civilian prisoners mixed together as well resulting in murders, violence and factions of prisoners.

There's as much evil on both sides if you ask me. The whole thing was a complete mess from end to end.

Only the victors get to put pen to page. The victors also pretty much legislated against debating anything other than the official stories.

Note: I'm not denying anything, but some things have gone unsaid. When you're not allowed to talk, faith is required and faith is inadequate in this day and age.

We usually refer ours to a Dilbert strip that defines the exact problem. Fortunately he has a sense of humor :)

Yeah and that's pretty much good enough for most people.

That's what we do for our internal dev systems.

As follows:

1. Read the vulnerability description.

2. Ask yourself if you are vulnerable.

3. No? Don't worry about it.

4. Yes? External mitigation where possible or patch ourselves and commit back to debian (we a project member on our team).

We've not got to 4 yet, but have committed loads of fixes anyway.

From extensive experience, debian testing is way more stable than Ubuntu's current LTS release even.

Yes I think you are correct.

Nil/null/nothing is different to zero. The former is the lack of anything and the latter is an integer with no magnitude. This is something I'm always having to hammer into our developers' heads over and over again.

First thing that came into my head as well.