# Monday, 01 March 2010
Friday, 03 May 2013 22:55:23 (GMT Daylight Time, UTC+01:00)
Thanks for spending time on the computer (wtriing) so others don't have to.
Sunday, 05 May 2013 08:00:37 (GMT Daylight Time, UTC+01:00)
strangely this post is now revmoed I have no idea how to say this nicely, but to be frank, if you go to his website, there's a post about his brother dying and how he'll stop trolling the web community. Perhaps that is the answer to what you find strange.
Sunday, 12 May 2013 05:03:24 (GMT Daylight Time, UTC+01:00)
otTHZi , [url=http://chcutholsglx.com/]chcutholsglx[/url], [link=http://ddhzhcmorgdo.com/]ddhzhcmorgdo[/link], http://ymbbnlvqcwvt.com/
Tuesday, 14 May 2013 07:10:45 (GMT Daylight Time, UTC+01:00)
TRANSFORMER PRIME?!??!?! HAAAA HAAAAA! YOU SURELY JEST.I just returned a prime AND dock for the random shut downs, the graphics tearing, the random screen item “jumps”, the GPS never working EVEN after a major update that was the supposed MESSIAH update, did I mention that they actually pulled GPS from one of the feature listings of the prime? The wifi is spotty and weak… their answer was to release the TF700T with upgraded backing (PLASTIC VS SPUN ALUMINUM. HAAA!). In order for you to get anything done with your product (repairs or warranty work.) your device has to be sent in so they can look at it. They won’t give a quote, they give you part numbers to see if you can find a price (none can be found) and I was told that glass only can not be replaced! THEY WANT 400 US DOLLARS TO REPLACE GLASS, SCREEN, AND DIGITIZER. THAT’S 100 USD SHY OF A BRAND NEW TABLET! I am actually looking at buying the 32 gig vers. of tab 7.0 plus as from every spec I have seen the plus has a 1.2 Ghz processor and the tab2 has only 1Ghz. I have seen too many problems with ICS mixed with TF201. I’m not risking it again with another company where the only thing different is a slower Processor and an OS I already know has issues. You take the risk yourself. But before you do look as the XDA Forums and Transformerforums.com. They are riddled with complaint posts and empty promise updates!

Wednesday, 15 May 2013 07:58:10 (GMT Daylight Time, UTC+01:00)
I held out for 8% on my latest startup, but then again I am a seasoned entrepreneur, not just a regular first hire. I actually met with the Founder and investors beforehand and the investor had the nerve to say that if I wanted equity I should pony up money. This blew my mind, how is a massive salary cut (about $80k) not ponying up money? Yes, there is the fact that I have the option to bow out at any time, but I get exactly nothing if no shares have vested. Luckily the Founder saw my value and agreed to my terms. The problem with giving away equity is that too many people aren’t motivated by it. I am very motivated by equity, and the Founder knew this from my past ventures. The truth is that most developers just aren’t that motivated by equity. When I founded a company 7 years ago and raised $500k I gave my first developer 2% and a salary maybe 25% less than what he might command otherwise. But he was right out of school, and this was an incredibly opportunity for him to learn about startups and get some excellent experience on a variety of technologies. The equity didn’t motivate him though, and he eventually left to make more money. That is very often the case (I have several more examples), so I don’t think you can’t be too hard on founders that are stingy with options. If you want the options then you need to command them. If you don’t get what you are worth then it isn’t the right choice.

Friday, 24 May 2013 07:08:16 (GMT Daylight Time, UTC+01:00)
Just advise people to block xbox live by going to their router homepage usualy default 192.168.1.1 set port blocking for ports 3074 and 88 this prevents the use of xbox live and it means you can still play online but you will have to use alternative methods for live play eg.xlink kai this is a software which allows online play via the system link option in the game.This may satisfy some people temporarily until the fix is complete just don't unblock the ports until the fix is here and applied you should be fine to go back online by unblocking the ports once you apply the fix they are working on.The router homepage address may vary depending on your router's initial setup so google it if it seems complex.This is a method used for playing banned 360's and none banned 360's online without xbox live subscription although the number of online players are limited.You would also need to allow port forwarding for xlink kai else you may find it is unable to connect so just google it.

Sunday, 26 May 2013 06:34:51 (GMT Daylight Time, UTC+01:00)
As a Hitachi user, and recently the proud owner of an XGD3 Lite-On burner, I'm just waiting. My box is already banned, I don't care about Live. I appreciate everything c4eva does and has done over the years. I like every other Hitachi owner just want a little bit of a ballpark. "Around Thanksgiving," or "the first of December," just some sort of idea. I understand the testing phase isn't finite but at the same time, giving some sort of idea of how things are going doesn't seem that difficult. Joking about skynet, could have easily been followed up by a quick message like "Hitachi testing going well, not too long now…" But, I will continue to wait like everyone else. I just wanted to say that I do appreciate the work he does, and I'm not going to bash the man because I have to wait a couple extra weeks. If it was that important I could always, oh I don't know, go to the store???

Wednesday, 29 May 2013 07:50:29 (GMT Daylight Time, UTC+01:00)
Having founded a start-up, raised money, hired, let’s just be clear. Your first employees are pretty much working as hard as the founders. Additionally, the founders may bring nothing but a raw demo that can be put together in very little time and some hustle to show it to/talk to the right people. Their great idea, like the million+ other ideas kicking around, are worthless without execution.I’ve been on both side of the equation, and the current standards for equity for early employees are disproportional to the investment those companies want you to make. When you are the first employee, it’s often the case that you’re freeing up one of the founders from doing the job you will be doing. If you take that tact, then that first employee is providing the same value the founder was until the founder hired themselves into another role.I’m not saying a first employee is taking the same risk as the founders, but to give them a significantly below-market-rate salary on top of a tiny (1%) bit of equity for putting that much skin in the game early on is a bit insulting.

Wednesday, 29 May 2013 07:50:31 (GMT Daylight Time, UTC+01:00)
Having founded a start-up, raised money, hired, let’s just be clear. Your first employees are pretty much working as hard as the founders. Additionally, the founders may bring nothing but a raw demo that can be put together in very little time and some hustle to show it to/talk to the right people. Their great idea, like the million+ other ideas kicking around, are worthless without execution.I’ve been on both side of the equation, and the current standards for equity for early employees are disproportional to the investment those companies want you to make. When you are the first employee, it’s often the case that you’re freeing up one of the founders from doing the job you will be doing. If you take that tact, then that first employee is providing the same value the founder was until the founder hired themselves into another role.I’m not saying a first employee is taking the same risk as the founders, but to give them a significantly below-market-rate salary on top of a tiny (1%) bit of equity for putting that much skin in the game early on is a bit insulting.

Saturday, 01 June 2013 07:47:20 (GMT Daylight Time, UTC+01:00)
Congrats! This blog is awesome. I wouldn’t write that better. Well done!|Congrats! This blog is so interesting and catching.|Congrats! This is one of the best blogs I have ever come across!|Congrats! This is one of the best blogs I have ever read!|Congrats! This is one of the most catching blogs I have ever read! Well done!.|Congratulations! This blog is great. I wouldn’t write that better.|Congratulations! This blog is one of the best I have ever come across.|Congratulations! This is one of the most catching blogs I have ever found.|Congratulations! This is one of the most interesting blogs I have ever come across.|Does anyone think that this blog could be better? I don’t!|Due to the way the blog is written, it is difficult to take the eyes off it.|Due to this blog I broadened my horizons. Thanks a lot!|Due to this blog I finally found out what I was looking for. Thanks a lot!|Due to this blog I had a chance to find a lot of interesting things. It is definitely worth recommending.|Due to this blog I had a chance to learn a little bit more.|Due to this blog I learnt a lot. I appreciate every minute spent on writing this webpage.

Friday, 07 June 2013 07:33:08 (GMT Daylight Time, UTC+01:00)
I guess there are a couple of things here.First of all, there’s no point in simply migrating to Mongo if you keep the same data models and schema as you would with RDBMS. This may be a big part of the White Houses decision. To make such a drastic change in storage, you need to play to the strength of the vendors solution, which is clearly the document model. A row in a table can easily be moved to a document in a collection, but you have to wonder why you would do that, unless you couldn’t optimise your current I/O.The second question about lifecycle is much bigger, but taking a similar approach as you would to RDBMS may be important if automation is integral. In my experience, the only time I’ve ever needed to start running migration scripts is when things haven’t been thought through from the offset – such as casting integers via an ODM / ORM when you know you’ll only have those types stored – which obviously improves index performance and reduces call complexity. The paradigm of a shifting schema should in my opinion be accounted for in application logic. Where possible, avoid it, but where you can’t (or won’t) run a series of updates, a few conditional statements won’t overly bloat your application. But if you do start bloating, that may the tipping point to try and achieve a higher level of data consistency.

Friday, 07 June 2013 07:33:09 (GMT Daylight Time, UTC+01:00)
I guess there are a couple of things here.First of all, there’s no point in simply migrating to Mongo if you keep the same data models and schema as you would with RDBMS. This may be a big part of the White Houses decision. To make such a drastic change in storage, you need to play to the strength of the vendors solution, which is clearly the document model. A row in a table can easily be moved to a document in a collection, but you have to wonder why you would do that, unless you couldn’t optimise your current I/O.The second question about lifecycle is much bigger, but taking a similar approach as you would to RDBMS may be important if automation is integral. In my experience, the only time I’ve ever needed to start running migration scripts is when things haven’t been thought through from the offset – such as casting integers via an ODM / ORM when you know you’ll only have those types stored – which obviously improves index performance and reduces call complexity. The paradigm of a shifting schema should in my opinion be accounted for in application logic. Where possible, avoid it, but where you can’t (or won’t) run a series of updates, a few conditional statements won’t overly bloat your application. But if you do start bloating, that may the tipping point to try and achieve a higher level of data consistency.

Friday, 07 June 2013 07:33:09 (GMT Daylight Time, UTC+01:00)
I guess there are a couple of things here.First of all, there’s no point in simply migrating to Mongo if you keep the same data models and schema as you would with RDBMS. This may be a big part of the White Houses decision. To make such a drastic change in storage, you need to play to the strength of the vendors solution, which is clearly the document model. A row in a table can easily be moved to a document in a collection, but you have to wonder why you would do that, unless you couldn’t optimise your current I/O.The second question about lifecycle is much bigger, but taking a similar approach as you would to RDBMS may be important if automation is integral. In my experience, the only time I’ve ever needed to start running migration scripts is when things haven’t been thought through from the offset – such as casting integers via an ODM / ORM when you know you’ll only have those types stored – which obviously improves index performance and reduces call complexity. The paradigm of a shifting schema should in my opinion be accounted for in application logic. Where possible, avoid it, but where you can’t (or won’t) run a series of updates, a few conditional statements won’t overly bloat your application. But if you do start bloating, that may the tipping point to try and achieve a higher level of data consistency.

Friday, 07 June 2013 07:33:10 (GMT Daylight Time, UTC+01:00)
I guess there are a couple of things here.First of all, there’s no point in simply migrating to Mongo if you keep the same data models and schema as you would with RDBMS. This may be a big part of the White Houses decision. To make such a drastic change in storage, you need to play to the strength of the vendors solution, which is clearly the document model. A row in a table can easily be moved to a document in a collection, but you have to wonder why you would do that, unless you couldn’t optimise your current I/O.The second question about lifecycle is much bigger, but taking a similar approach as you would to RDBMS may be important if automation is integral. In my experience, the only time I’ve ever needed to start running migration scripts is when things haven’t been thought through from the offset – such as casting integers via an ODM / ORM when you know you’ll only have those types stored – which obviously improves index performance and reduces call complexity. The paradigm of a shifting schema should in my opinion be accounted for in application logic. Where possible, avoid it, but where you can’t (or won’t) run a series of updates, a few conditional statements won’t overly bloat your application. But if you do start bloating, that may the tipping point to try and achieve a higher level of data consistency.

Friday, 07 June 2013 07:33:10 (GMT Daylight Time, UTC+01:00)
I guess there are a couple of things here.First of all, there’s no point in simply migrating to Mongo if you keep the same data models and schema as you would with RDBMS. This may be a big part of the White Houses decision. To make such a drastic change in storage, you need to play to the strength of the vendors solution, which is clearly the document model. A row in a table can easily be moved to a document in a collection, but you have to wonder why you would do that, unless you couldn’t optimise your current I/O.The second question about lifecycle is much bigger, but taking a similar approach as you would to RDBMS may be important if automation is integral. In my experience, the only time I’ve ever needed to start running migration scripts is when things haven’t been thought through from the offset – such as casting integers via an ODM / ORM when you know you’ll only have those types stored – which obviously improves index performance and reduces call complexity. The paradigm of a shifting schema should in my opinion be accounted for in application logic. Where possible, avoid it, but where you can’t (or won’t) run a series of updates, a few conditional statements won’t overly bloat your application. But if you do start bloating, that may the tipping point to try and achieve a higher level of data consistency.

Friday, 07 June 2013 07:33:13 (GMT Daylight Time, UTC+01:00)
I guess there are a couple of things here.First of all, there’s no point in simply migrating to Mongo if you keep the same data models and schema as you would with RDBMS. This may be a big part of the White Houses decision. To make such a drastic change in storage, you need to play to the strength of the vendors solution, which is clearly the document model. A row in a table can easily be moved to a document in a collection, but you have to wonder why you would do that, unless you couldn’t optimise your current I/O.The second question about lifecycle is much bigger, but taking a similar approach as you would to RDBMS may be important if automation is integral. In my experience, the only time I’ve ever needed to start running migration scripts is when things haven’t been thought through from the offset – such as casting integers via an ODM / ORM when you know you’ll only have those types stored – which obviously improves index performance and reduces call complexity. The paradigm of a shifting schema should in my opinion be accounted for in application logic. Where possible, avoid it, but where you can’t (or won’t) run a series of updates, a few conditional statements won’t overly bloat your application. But if you do start bloating, that may the tipping point to try and achieve a higher level of data consistency.

Friday, 07 June 2013 07:33:16 (GMT Daylight Time, UTC+01:00)
I guess there are a couple of things here.First of all, there’s no point in simply migrating to Mongo if you keep the same data models and schema as you would with RDBMS. This may be a big part of the White Houses decision. To make such a drastic change in storage, you need to play to the strength of the vendors solution, which is clearly the document model. A row in a table can easily be moved to a document in a collection, but you have to wonder why you would do that, unless you couldn’t optimise your current I/O.The second question about lifecycle is much bigger, but taking a similar approach as you would to RDBMS may be important if automation is integral. In my experience, the only time I’ve ever needed to start running migration scripts is when things haven’t been thought through from the offset – such as casting integers via an ODM / ORM when you know you’ll only have those types stored – which obviously improves index performance and reduces call complexity. The paradigm of a shifting schema should in my opinion be accounted for in application logic. Where possible, avoid it, but where you can’t (or won’t) run a series of updates, a few conditional statements won’t overly bloat your application. But if you do start bloating, that may the tipping point to try and achieve a higher level of data consistency.

Friday, 07 June 2013 07:33:39 (GMT Daylight Time, UTC+01:00)
I guess there are a couple of things here.First of all, there’s no point in simply migrating to Mongo if you keep the same data models and schema as you would with RDBMS. This may be a big part of the White Houses decision. To make such a drastic change in storage, you need to play to the strength of the vendors solution, which is clearly the document model. A row in a table can easily be moved to a document in a collection, but you have to wonder why you would do that, unless you couldn’t optimise your current I/O.The second question about lifecycle is much bigger, but taking a similar approach as you would to RDBMS may be important if automation is integral. In my experience, the only time I’ve ever needed to start running migration scripts is when things haven’t been thought through from the offset – such as casting integers via an ODM / ORM when you know you’ll only have those types stored – which obviously improves index performance and reduces call complexity. The paradigm of a shifting schema should in my opinion be accounted for in application logic. Where possible, avoid it, but where you can’t (or won’t) run a series of updates, a few conditional statements won’t overly bloat your application. But if you do start bloating, that may the tipping point to try and achieve a higher level of data consistency.

Friday, 28 June 2013 18:14:17 (GMT Daylight Time, UTC+01:00)
cheap car insurance quotes online qxz online colleges in pa 3289 mail order 50mg viagra cvzm purchase cialis on the internet >:] auto insurance reviews %OOO
Friday, 28 June 2013 18:14:18 (GMT Daylight Time, UTC+01:00)
accutane 9597 degrees online veterinary surhx marine biology distance learning 299 buy cialis :-OO new york car insurance pczgg Acheter Du Viagra %-]]
Thursday, 04 July 2013 18:18:19 (GMT Daylight Time, UTC+01:00)
ordering cialis online ayakkt viagra generics %[[[ cheapest car insurance thhld AUTO INSURNACE :[ insurance for imported car 8PP
Friday, 05 July 2013 21:29:11 (GMT Daylight Time, UTC+01:00)
purchase viagra online 62034 buy viagra with prescription 76041 cards insurance auto ouaggk generic cialis =]] buy tadafil =[[ viagra online duju
Monday, 08 July 2013 02:51:36 (GMT Daylight Time, UTC+01:00)
diabetic impotence 5398 generic cialis lxo generic cialis 225 cheap car insurance ftrmd auto insurance quotes online in California :-[[[ generic cialis juj cheapest viagra online =]]
Wednesday, 10 July 2013 20:22:07 (GMT Daylight Time, UTC+01:00)
nj car insurance quotes 181 viagra prescription 275 viagra price 8-D nsw car insurance =[ cialis pills for men >:-((
Friday, 12 July 2013 14:44:41 (GMT Daylight Time, UTC+01:00)
sildenafil >:[[ auto insurance quotes 135 auto insurance independant %-))) viagra online rkga cheap auto insurance 9115
Friday, 12 July 2013 14:45:38 (GMT Daylight Time, UTC+01:00)
cialis perscription xpqkr florida car insurance odqjuv buy cialis 83441 cheap auto car insurance in arkansas lcn i want to use my mastercard to purchase generic viagra 032049 car cheap insurance ylmqc
Thursday, 18 July 2013 22:46:24 (GMT Daylight Time, UTC+01:00)
no prescription brand cialis 4360 medicare supplement insurance companies 498 japanese auto insurance IN 668483 car insurance quato fhpowt car insurance quotes xdzrrw florida car insurance %-]]] cheapest auto insurance rates 8-))
Sunday, 21 July 2013 14:08:19 (GMT Daylight Time, UTC+01:00)
car insurance quotes :-OO car insurance =PP accutane non presciption :(( car insurance islbi free car insurance IN 3870 cheap car insurance you can buy online 913784 cheap insurance quotes ilbut
Thursday, 25 July 2013 08:46:07 (GMT Daylight Time, UTC+01:00)
purchase viagra in america wwithout prescription zpvqa car insurance premiums 430210 PA best car insurance quotes zvenu public liability insurance definition of 736061 affordable car insurance quotes free >:-]]]
Sunday, 28 July 2013 23:30:57 (GMT Daylight Time, UTC+01:00)
buy viagra =))) NC az insurance car eqex cheap accutane qmr levitra cost per pill =[ really cheap car insurance companies PA lsbtdv sildenafil ejka cheep car insurance >:O
Saturday, 03 August 2013 01:03:14 (GMT Daylight Time, UTC+01:00)
buy viagraonline 62957 buy viagra online %[[ life insurance quotes 3208 247 Meds Online Order Cialis Black Online cjgtf in young men impotence =DDD
Monday, 05 August 2013 21:57:46 (GMT Daylight Time, UTC+01:00)
Auto insurance quotes in Texas >:-D car insurance rates in nj 06741 erections hkc pictures accutane + patients 353
Wednesday, 07 August 2013 13:15:05 (GMT Daylight Time, UTC+01:00)
auto insurance quotes online =P SC auto insurance for teens elm Florida payless auto insurance 46677 cheapest viagra or cialis 264379 agency auto insurance 216452 levitra faq =-]] discount auto insure qmm
Saturday, 10 August 2013 06:34:07 (GMT Daylight Time, UTC+01:00)
buy cialis online with no prescription 27167 top auto insurance rates >:OOO viagra no prescripion lss cialis online 482 prednisone 577
Sunday, 11 August 2013 12:54:57 (GMT Daylight Time, UTC+01:00)
viagra online >:-[ cilias msfuch life insurance rates =-O viagra online 10169
Tuesday, 13 August 2013 09:22:57 (GMT Daylight Time, UTC+01:00)
new jersey low car insurance 617559 buy cialas on line vjs chronic obstructive pulmonary disease :-]]] buy viagra jur
Thursday, 15 August 2013 13:18:10 (GMT Daylight Time, UTC+01:00)
online auto insurance 08013 viagra online znuupm OK really really cheap car insurance :)) car insurance lawyers >:] Buy Discount Cialis Best Online 8-)) car insurance quotes 0339
Friday, 16 August 2013 19:13:49 (GMT Daylight Time, UTC+01:00)
guitar online courses 993 free auto insurance udjpc dental insurance pacificare >:OOO cheap car insurance tmeze Charlotte compare car insurance uxelqy
Thursday, 22 August 2013 00:31:22 (GMT Daylight Time, UTC+01:00)
online degree programs accredited =-[[[ online cialis no prescription 376919 online celis >:-]]] viagra %) buy cialis 469352 get car insurance quotes 9485
Thursday, 22 August 2013 00:31:22 (GMT Daylight Time, UTC+01:00)
cialis to buy jjqhst cialis purchase on line 5175 purchase car insuranec 585 auto 479 Charlotte car insurance free quotes 8PP inexpensive auto insurance quote Columbus 671043
Thursday, 22 August 2013 00:31:29 (GMT Daylight Time, UTC+01:00)
cheap car insurance quotes online pjpn cheap car insurance quotes in georgia 099118 accutane buy rcllq auto insurance expensive wsu insurance public liability act tiqg cialis online krut
Friday, 23 August 2013 02:10:41 (GMT Daylight Time, UTC+01:00)
womens car insurance for >:DDD cialis generic 4349 buy cialis online =-[[ cialis 213 Order Prednisone without Prescription 6328 viagra in india 8DDD
Comments are closed.