i used to always build my own but these days i don't really need the few £ saved by doing so and my latest build has liquid cooling ... im too much of a clumsy muppet to trust myself with a combination of electronic components and liquid i went with cyber-power ... good brand-name hardware, highly customisable, shipped with all manuals, CDs, cables, spares etc and top notch customer service (for example i had ordered some HDD cooling systems that i didn't realise required the drives to go in the larger front bays, i didn't have enough of these free in the case i had chosen so i got a nice friendly call to discuss my options ... went with a refund on the cooling systems)

Pedis ex oris Quidquid latine dictum sit, altum sonatur

smurf themetune ... had that on and off for the past year, at what point does it become a recognised psychological disorder? occasionally i get a break and have either greensleeves or aud lang syne instead (believe me, you get funny looks for humming aud lang syne at any time other than new year)

Pedis ex oris Quidquid latine dictum sit, altum sonatur

IIRC its an extension method so very likely to be the same as it will be using the pre-existing public members unless of course there's some IL magic going on...

Pedis ex oris Quidquid latine dictum sit, altum sonatur

yes. list being the simplest data type in which an order is applied to a set of data Though, judging by your rep scores on here you are more likely to know what you are talking about than I am, so ... am i missing something here, do we work in different languages with different concepts of 'list'? should we be using

list.ElementAt(0)

instead?

Pedis ex oris Quidquid latine dictum sit, altum sonatur

Similar tot he below issue, an example of which was posted on CP about a month ago

if(some very long condition that pushes the right hand side of the statement off the screen) return;
{

//stuffs

}

It is likely the extra return was a temporary debugging thing that got left as a dingleberry ... but a subtle bug none-the-less. I personally always use braces and think it a shame that the above example compiles at all

Pedis ex oris Quidquid latine dictum sit, altum sonatur

she wants you to buy her something shiny

Pedis ex oris Quidquid latine dictum sit, altum sonatur

1. yup 2. yup 3. slightly overweight and breathes a little too heavily after just one flight of stairs 4. chooses to believe that creative styling of whatever hair remains so that the baldness doesn't show counts as 'not balding' 5. nope ... but student girls!, you lucky so-and-so! 6. yup add to that: 7. talks faster than a normal human being 8. has endless time for anyone willing to talk geek 9. has zero time for arty-farty-hippy types ... you tell me i have a chakra, i switch off 10. tendency for fingers to continue 'typing' even when they haven't been near a keyboard for hours 11. complete blindness when it comes to cables covering a lounge to the point that guests have nowhere to sit 12. 'Treasure trove' of PC corpses consisting largely of hardware too old to ever be of any use but not old enough to have any 'antique' value

Pedis ex oris Quidquid latine dictum sit, altum sonatur

There are a few mortgage brokers that have set up deals with the banks that work on CV and current contract, but they'll charge £500 for arranging it

Pedis ex oris Quidquid latine dictum sit, altum sonatur

there were a fair few of them but still a lot of real work going around

Pedis ex oris Quidquid latine dictum sit, altum sonatur

I found the complete opposite, my last contract came to an end in feb and I was bombarded with calls from recruiters. I expect it varies by region but the home counties are going pretty strong atm the continent on the other hand is pretty hard up, my brother contracts in holland and theres very little out there

Pedis ex oris Quidquid latine dictum sit, altum sonatur

thanks to the flat rate vat scheme i make a profit on vat :P

Pedis ex oris Quidquid latine dictum sit, altum sonatur

my advice: Do it! i switched just over a year ago and its the best decision i ever made. 1. in terms of money, i was bringing in £30k at my last perm job, went from that to a 6 month contract that worked out at approx £78k per year and from that to a £100k+ its best to set up your own limited company and put the income through that. you invoice (+vat) then take that income, pay your expenses (including VAT) out of it and what is left (the company profits) gets taxed @ 20%. Then you pay yourself a minimal salary (normally 7-10k) just to make sure the government still gives you a pension and the rest is paid as share dividends (which don't incur NI etc) with the 20% corp tax you pay on your company profits comes a 10% personal tax credit which means you pay 10% less income tax on the money from dividends. income is taxed as 7k tax free, 35k @ 10%, then its 35% until you hit 150k so with the 10% credit you only pay income tax on income above 42k (and thats at 25%) personally i dont need 42k per year so i dont pay income tax and leave the remainder of my profits in the company, these funds are then used to buy property which the company rents out 2. I would suggest you go for the whole 'sit in the office and be part of the team' style, (although you have to be careful with IR35 witht his style on contract). The market is very buoyant in the UK for this kind of work atm, whereas a friend who tried freelancing from home struggled to find work 3. no idea One thing that a lot of people said to me when i was making the move is that they would be concerned about job security, most contracts have 2-4 week notice period so you can find yourself unemployed from a perm job in just as short a time as a contract (i.e. job security is a myth) .. the difference is that, at the rate of my first contract, i only had to find work for 4 months of the year to break even with my last perm position ... frankly, if i cant find more than 4 months in a year, its probably time to change jobs anyway ;) contract took me from 'treat myself to a chocolate bar once every other month' to 'driving a brand new jag' ..... definately do it :D

Pedis ex oris Quidquid latine dictum sit, altum sonatur

if(question == QuestionType.Homework)
{
knowledgeGained = DoItYourself();
}
else
{
you.ProvidedMoreInfo += (sender, args) => { us.ProvideInsightOn(question); }
}

Pedis ex oris Quidquid latine dictum sit, altum sonatur

you don't. think what you are trying to do here, you have a class called MyEvent which owns and exposes an event. That class is solely responsible for managing that event, other classes interacting with it are merely listeners The only point at which an event being null should matter is if you are about to invoke it. The only thing that invokes an event is its owner class and therefore only MyEvent needs to care about SomeEvent being null. Therefore if you want a console output for an attempt to invoke an event for which no event handler has been attached it should go in the OnSomeEvent method of the MyEvent class

Pedis ex oris Quidquid latine dictum sit, altum sonatur

yup that, along with - Star wars : force unleashed (supposedly the successor/replacement for the awesome jedi knight/dark forces series ... rendered practically unplayable by a shoddy port) - Deus ex 2 : as bad as deus ex 1 was good event the battlefield series has some definate console-quirks to it (the quick-voice-command menu is blatantly designed for a thumbstick and requires you to press a button and then move your mouse in 1 of 12 different directions)

Pedis ex oris Quidquid latine dictum sit, altum sonatur

thought i had that issue once, turned out to be a piece of flapjack wedged in the keyboard ... debated eating the bit of flapjack...

Pedis ex oris Quidquid latine dictum sit, altum sonatur

i want it to be a pc ... that way, as a pc gamer, i wont have to suffer through appauling console ports

Pedis ex oris Quidquid latine dictum sit, altum sonatur

ok, i see where my tounge-in-cheek manner of typing up that post may have given that impression. fair enough :) As i stated in another reply, i'm not suggesting a factory for every class. what i was attempting to do with this post was spark a debate over approaches to enforcing/encouraging use of factories where such things are advantageous. i tend to work in dev teams for periods of 6 months, im not around after that to explain how particular classes should be instantiated personally so i aim to make the intended instantiation 'easiest-path' (i do, ofc, write documentation.. the whole last month of my last contract was spent documenting every concept within the code. but i'm the first to admit i don't always reach straight for the docs and things can get overlooked) So, really, rather than trying to write annoying code as you suggest, i am trying to make peoples lives easier by guiding them to the intended use of the code i have written without having to spend hours examining it or reading documentation

Pedis ex oris Quidquid latine dictum sit, altum sonatur

I think we are getting some crossed wires here , i am actually arguing against a factory method in every class and talkign about a common singleton factory providing factory methods for a group of classes with a common association. Also, and perhaps my initial question was a little misleading, i am not suggesting a factory approach for every class, rather, i was trying to spark a debate on how to enforce use of a factory where one is deemed nescessary/advantageous

Pedis ex oris Quidquid latine dictum sit, altum sonatur

I get your point with regards to flexibility of use being restricted by a factory In my most recent implementation using a factory I was implementing a system whereby properties of a viewmodel would be backed by wrapped values to provide additional functionality (history tracking, validation etc).. a lot of the data for these wrapped values was to be declared on a static field definition (thinks such as notification logic, validation rules, unit derivation information etc). Each class would, therefore, have a static field catalog holding a collection of field definitions. From the field catalog an instance 'state manager' object could be created that exposed the value wrappers. It was these value wrappers i didn't want directly instantiated as they would not be tied to a field definition. This could have been achieved, i suppose, by instantiating the state manger and passing ti to the wrapper's constructor, however a lot of the instantiation process is automated by having it performed as part of the statemanager initialization I hope that gives some insight into my thinking in that scenario As for being a java developer, i'm a c# developer but in a previous job (early in my career) i worked for a company that used both java and c# (on the same product, java back end, c# client) and fell under the tutelage of a java dev ... so i will concede i may have picked up a few java-isms along the way ;)

Pedis ex oris Quidquid latine dictum sit, altum sonatur