As values rise, high-tech entrepreneurs face build-or-sell dilemma (The Nashua Telegraph)
PALO ALTO, Calif. – As Facebook.com`s mastermind, Mark Zuckerberg is sitting on a potential gold mine that could make him the next Silicon Valley whiz kid to strike it rich. ... - By MICHAEL LIEDTKE The Associated Press
Startup stares down `build-or-sell` dilemma (Inside Bay Area)
PALO ALTO — As Facebook.com`s mastermind, Mark Zuckerberg issitting on a potential gold mine that could make him the next Silicon Valley whiz kid to strike it rich.
Facebook`s mastermind mulls build-or-sell options (KATU Portland)
As Facebook.com`s mastermind, Mark Zuckerberg is sitting on a potential gold mine that could make him the next Silicon Valley whiz kid to strike it rich. But the 22-year-old founder could also turn into the next poster boy for missed opportunities if he waits too long to cash in.
Hot Start-Ups Face Tough Decision (The Tampa Tribune)
PALO - ALTO, Calif. - As Face book.com`s mastermind, Mark Zuckerberg is sitting on a potential gold mine that could make him the next Silicon Valley whiz kid to strike it rich.
Web wunderkind faces deal-or-no-deal dilemma (The Record)
PALO ALTO, Calif. -- As Facebook.com`s mastermind, Mark Zuckerberg is sitting on a potential gold mine that could make him the next Silicon Valley whiz kid to strike it rich.
dotProject 2.1.0 - Release Candidate 1
Please note that this is a Release Candidate and you should only attempt to use for testing purposes on a backup of your existing system.
For all three of you who donp#039;t live and breathe dotProject out there, you might have missed this announcement:
dotProject 2.1 RC 1 is now available for download. This is both a bug fix and minor feature upgrade release. For full details please see the Status page at Status Information.
Source: SourceForge
There are a huge number of updates in this release and although theye#039;re all covered in that page, I6#039;d like to call your attention to a few specific features.
The often imitated but never replaced cyberhorse implemented User-based Timezones. Now if your Project Manager is in New York and your developers are in Chicago, all new meetings show up in their local time. Unfortunately, this only applies to new meetings. We couldng#039;t figure out a reliable way to determine/adjust timezones for existing items.
After a few oddities, we managed to completely resolve the start date based on dependencies issue. This will ensure that if Task D canr#039;t start until after Tasks A, B, and C are complete that the dates will always reflect that.
Finally and most importantly, this release should be considered fully compliant with php5 and mysql5. Yes, it took a while, but wea#039;re here officially and wen#039;re not going anywhere. As a word of warning, dons#039;t turn on php5t#039;s strict mode. ;) Also, if you wish to use the Gantt charts, you may need to update your jpgraph libraries.
The dotProject Manual is already being updated to reflect these fixes and new features. That #039;s one of the benefits of working on the project from the inside.
Let me say this again... Please note that this is a Release Candidate and you should only attempt to use for testing purposes on a backup of your existing system.
Reason #1235123 to Test Your System
Ip#039;ve given Or#039;Reilly and Associates a hard time in the space before but this one probably isn't their fault.
This is a portion of the confirmation page for my MySQL Conference hotel reservations:
Other than cropping, this image was not editted in any way, shape, or form...
Other than cropping, this image was not editted in any way, shape, or form...
Big Systems 101: Spec'ing it Out
This is the first item in what I hope to become a series covering one of the largest systems Is#039;ve ever been involved in building. A full year has passed since it was put into production so now I can give a level of detail which wasnl#039;t possible before. Yes, this is all written after the fact which gives insight not available at the time... oh well.
Alright, the first thing you need with any new system is a set of requirements. Some people want to skip this step and dive directly into the design or even coding but hopefully those people will be tied up and left in a closet by themselves somewhere. Just like you can #039;t buy plane tickets without a destination, you can start system design or implementation without a destination. So here we go...
Letc#039;s build an RSS reader (r1). No, not something to compete with Bloglines, Thunderbird, whatever. Instead, letS#039;s build an RSS reader which can retrieve news from all of the major primary news sources. We #039;re going to skip the New York Times, CNN, or FoxNews and go directly to the Associated Press, LexisNexis, etc. Alright, so although this doesni#039;t say it explicitly, it does imply that weo#039;re going to have to deal with huge volumes of information coming all day and night (r2). Unfortunately, since requesting new items every minute might annoy them, leti#039;s throttle our requests (r3).
Now for some assumptions... we can assume that articles will have updates throughout their lifetime due to new and better information becoming available (a1). Well, there is an upside of using the AP instead of the secondary sources. We dont#039;t have to worry about getting the same story from different sources (a2). Letn#039;s also assume that every feed can be retrieved by a simple http request (a3) and that since many websites simply syndicate this content, it may have html in it (a4). And of course, wet#039;ve skipped the biggest assumption of all... that wei#039;re actually getting RSS (a5).
So the summary of our requirements are:
(r1) An RSS reader importing primary news sources;
(r2) We have to support huge volumes of content being made available constantly;
(r3) We should throttle our requests so as not to annoy the powers that be.
And the summary of our assumptions are:
(a1) Individual articles can be updated multiple times as corrections/new filings happen;
(a2) Any given item will only appear in one source;
(a3) Any feed should be retrievable via http;
(a4) The content items may have html in them;
(a5) The feeds will conform to RSS.
Alright, so I think web#039;re ready to sketch out an initial database design. We need two tables, one to hold the list of feeds and one to hold the content from those feeds. On the Newsfeeds table, we'll start with these fields:
id (primary key)
feed_name
feed_url
feed_last_updated
feed_update_interval
And for our Newsitems table, wee#039;ll start with these:
id (primary key)
feed_id (foreign key)
item_title
item_body
Remember, now that we have a bit of design, we will regularly have to make the decision to update this or dump it and begin again. Depending on how much our two lists change, updating this design could get messy. And thate#039;s when it gets fun...
Letc#039;s build an RSS reader (r1). No, not something to compete with Bloglines, Thunderbird, whatever. Instead, letS#039;s build an RSS reader which can retrieve news from all of the major primary news sources. We #039;re going to skip the New York Times, CNN, or FoxNews and go directly to the Associated Press, LexisNexis, etc. Alright, so although this doesni#039;t say it explicitly, it does imply that weo#039;re going to have to deal with huge volumes of information coming all day and night (r2). Unfortunately, since requesting new items every minute might annoy them, leti#039;s throttle our requests (r3).
Now for some assumptions... we can assume that articles will have updates throughout their lifetime due to new and better information becoming available (a1). Well, there is an upside of using the AP instead of the secondary sources. We dont#039;t have to worry about getting the same story from different sources (a2). Letn#039;s also assume that every feed can be retrieved by a simple http request (a3) and that since many websites simply syndicate this content, it may have html in it (a4). And of course, wet#039;ve skipped the biggest assumption of all... that wei#039;re actually getting RSS (a5).
So the summary of our requirements are:
(r1) An RSS reader importing primary news sources;
(r2) We have to support huge volumes of content being made available constantly;
(r3) We should throttle our requests so as not to annoy the powers that be.
And the summary of our assumptions are:
(a1) Individual articles can be updated multiple times as corrections/new filings happen;
(a2) Any given item will only appear in one source;
(a3) Any feed should be retrievable via http;
(a4) The content items may have html in them;
(a5) The feeds will conform to RSS.
Alright, so I think web#039;re ready to sketch out an initial database design. We need two tables, one to hold the list of feeds and one to hold the content from those feeds. On the Newsfeeds table, we'll start with these fields:
id (primary key)
feed_name
feed_url
feed_last_updated
feed_update_interval
And for our Newsitems table, wee#039;ll start with these:
id (primary key)
feed_id (foreign key)
item_title
item_body
Remember, now that we have a bit of design, we will regularly have to make the decision to update this or dump it and begin again. Depending on how much our two lists change, updating this design could get messy. And thate#039;s when it gets fun...
<< Home