--- we are a startup with almost a year live. None of the employees have ownership/stock and all are salary ---
No one is invested in the future of the company or what happens to the product because no one is going to be rewarded if things go well. Without ownership or profit sharing of some sort, no one who is worth anything will stick around to work 11 hour days unless the work environment is so amazing that they can get compensated other ways. The reality is, without profitability, those alternative means of compensation (extra hardware/software budget, extra flex time/vacation time, etc) won't hold up for long. It sounds like you are working for someone who has read Spolsky but really has no idea what he's on about. Does your SDLC pass the Joel test? (one step builds, testing, source control, bug database, etc etc). Are you working on brand new computers with at least 2 big monitors and more ram and storage space than any reasonable person should ever need? Do you get to set your own schedules as long as you are meeting deadlines/goals/pushes? Are you in offices or cubicles? If cubicles does everyone have a good pair of headphones? Are the cubicles or offices big enough? Is it acceptable for people to take a break and surf slashdot/Youtube/CNN for a few minutes when their brain buffer is blown and they can't concentrate? I'm not talking about come in and surf for 10 hours, but is it an environment where everyone has to be ultra careful about what's up on their screen and makes extra effort to look busy or stressed out enough to be taken seriously or is it the sort of place where people are treated like adults and given the benefit of the doubt as long as they're getting their commits in, QA'd, and past testing by the next milestone/goalpost/sprint/push/whatever?
If you are working for a startup, you really should believe in and be passionate about the product and the company and they should be passionate about you and your team! If it's really such a great idea there ought to be room for ownership and compensation for everyone involved on the ground floor and even the first couple of floors. People are what make a company great. It takes strong leaders, it takes a lot of faith and inspiration in what you are doing and it takes talented and hard working teams who are united in a common goal of making the best damn whatsy-whosit that's ever been dreamed of.
From your post it sounds like you're talking about a half baked company with tolerable but not stellar management and whatever talent the going market rate could buy. Which can be anywhere from pretty good, to so-so to absolutely dismal depending on a lot of factors.
Saying, "I just need a programmer" is a lot like saying, "I could totally get this car running if I just had a tool." What kind of tool were you looking for? An OBD-II reader, a flathead screwdriver? a 9mm socket wrench? A hydraulic lift bay? Not all programmers are created equal, and they are not equivalent cogs that can be removed and replaced at will without regard or consequence. Surely there are programmers that are more valuable than others, just like there are works of art or engineering that are more prized than others. There is a widely accepted myth among the industry that nearly everything is a computer solvable problem. At the same time, the technology professionals who will be expected to solve these problems with the aid of technological tools such as hardware and software are often considered a minor and inconsequential part of the equation, without value or merit beyond performing a specific task. Often we are told not only what problem to solve, but how we are expected to solve it. Usually by people who haven't the faintest notion what they are asking for.
Trying not to repeat earlier suggestions, (though Tesla has always been a personal hero)
How about Chuck Yeager, fighter pilot, test pilot, first person to break the sound barrier.
Any and all of the Mercury Seven astronauts. If your son has any doubts, sit him down in front of a copy of "The Right Stuff", he'll come around.
I actually had DSL in 98-99. Relevant factors = Seattle suburbs, Covad business class DSL that we split a cost of around 300 a month for and for the record it was the best DSL service I ever had (SDSL at that) . They pulled ethernet right up to the house, and put a jack in, we plugged that right into our router (10mb if I remember correctly) and that was that. ran wires to every room of the house and we were all set. I've had most permutations of broadband since then, and I'm currently on cable. Tried ADSL a bunch of times but I can never seem to get the 'good' speeds no matter where I live.
Maybe if 3D actually worked for more people, was used in ways that improved the overall storytelling process and was less expensive, you wouldn't hear so many criticisms of it. It works for me, marginally, but I usually end up with a headache and after a few minutes I lose interest. It ruins immersion for me, whether it's a game, or a movie so it's safe to say I'm not a big fan.
In so many areas of scientific research, who is funding the study says more about the outcome and conclusions than almost anything else. So whether you're talking about climate change and greenhouse gases, whether it's safe to add more ethanol to our gasoline, whether certain products or procedures have medical benefit that outweighs the risks, or just about anything else, keep your eyes open, keep your mind open, and follow the money trail.
Not really true. They can always find *someone* who is ready and willing, but that is a far cry from having any man they desire. Once you get to know a girl or two, you'll probably realize they have to work at it a bit too, and it all evens out in the end.
In the real world, your subjective perception is often all you will EVER have to go on. Make as reasonably informed a decision as you can, and live with those consequences. A lot of so called objective studies especially in technology are quite biased. A DBA whose primary focus is Oracle would end up with completely different results than one who works primarily with DB/2 or PostgreSQL or MySQL. That's because each of these databases has different strengths, weaknesses, idiosyncracies, and yes, SQL idioms that make them perform better when done a certain way. The parsers are different, the optimizers are different, the table structures are different, why are you expecting an apples to apples comparison on features?
Sure, there are companies out there doing it right or at least trying, but there are many who are looking to
1. Replace experienced workers with inexperienced ones at half to 2/3rds salary.
2.Hire architects to design and document complex systems and then hire the equivalent of janitors to do maintenance and upgrade work. Eventually the center cannot hold and you end up with a complex nest of band aids and workarounds worthy only of submission to TDWTF.
3.Replace creative thinking, problem solving and innovation with documentation of procedure whereby routine tasks are accomplished by following rote procedures and recipes that a trained monkey can follow, but which don't really address all the real world failure points in the process or how to even detect them much less correct them. Worse yet, since policy is to follow the procedure, updating said procedure is usually next to impossible to get approved.
Most of this comes from a fundamental mistrust and misunderstanding of the value and role of IT within an organization. IT as a whole is viewed as a sausage grinder into which many companies pour their most critical business problems and hope that what comes out is a solution everyone can stomach. IT doesn't fix business problems, it fixes Information and automation problems. If you make poor decisions and ask IT to implement them, and the whole thing goes up in flames it doesn't mean IT failed you and many companies don't seem to grasp that.
The issue with your argument is that not all cars are created equal. Many cars on the road are equipped to operate well above operating tolerances assumed for these so called 'maximum safe speeds.' That said, the problem isn't the cars, it's the drivers. No matter how awesome your car is, the real limiting factor is the other people you share the road with. If you want to be remotely responsible about it, you have to assume a bare minimum of driving ability from each and every other driver on the road with you.
Your sudden lane change to avoid creaming them while they crawl along in the fast lane, even though you've been approaching them at high speed for the last minute and a half doesn't mean they won't see your front grill in the rear view and immediately swerve into the lane they should have been driving in in the first place. You see, your reasonable expectation that they won't drift into your lane as you attempt to pass goes right out the window when put up against their important cell phone call, while they're trying to pick spinach out of their teeth from lunch and change the DVD for the three kids in the back.
For your safety and theirs, it's always best to drive as conservatively and defensively as possible. No matter how much less fun it is. Find a track, or a truly deserted place to let loose instead of your local interstate.
There are all kinds of different 'coders' these days. They have their own idioms, ideals, tools and culture. You will find people who will try to convince you that Python is the Holy Grail, others will tell you that Ruby is the one true path. (Although usually the story is so over the top, you end up missing the simplicity and beauty of Ruby, all you know is she got "Railed" for three days straight and is now servicing millions of requests, at least when she's not busy batting eyelashes at some Mongrel or really anybody as long as they have a really Fast CGI.)
Most development these days is taking place between all these tubes that make up the interwebs. That means you're usually looking at something that runs on, through or near some sort of web or app server. Set yourself up with a local web server or app server configured with whatever jingles your bells, and get to it. There is no right or wrong way to go about it, and even if you kiss a lot of frogs, you'll eventually find your favorite way to php/jruby/jython/plone/java/flex/lasso/squeak/perl_mod/whatever your way into web programming and Service Oriented Architecture (Which is just a fancy way of saying functions (which are now methods) are actually now web services, that you call remotely (But not like COM or CORBA remotely) but more like REST or SOAP remotely, but at the end of the day they do the same darn thing. Along the way if anyone asks you about relational databases, give them a smug look, shake your head knowingly and walk off muttering something about an impedance mishmash and threaten to hibernate until they propel the conversation elsewhere.
Of course, none of this is going to matter because the world will end tomorrow. Now if you'll excuse me, I need to pack my towel and go get some beer.
The people who are using it to cause damages already know how this is done. The only dangerous part about something like this is that the public might be made aware of just how far from secure most financial transactions are.
There are lots of views on morality, but for me personally, I'd say yes, cheating is ALWAYS bad, because above all, it's dishonest. More than that though, you are cheating yourself, and your professed parter, and even your person on the side out of a chance at a real love relationship.
If you have real and significant problems with your spouse, get those issues out in the air. If they can't be worked on between the two of you, get some counseling, or get some papers filed. It's really that simple. "Staying together for the kids" only teaches the children that abuse and unhappiness are okay as long as you can justify it to yourself. Besides, they learn almost everything about love relationships by watching their parents. If you don't love someone, but you're staying with them anyway, expect your kids will do the same until or unless they learn better.
It's a complex problem to be sure, mainstream media has stressed the fairy tale courtship, where the magic of love is all about finding the right person. Unfortunately most people find out falling in love and living in love can be rather different. If you find the right person though, and you inspire each other to each be the right person for one another then you may wake up every day feeling like you are the luckiest person alive.
I use MySQL and PostgreSQL every day and whenever I have a choice, and if it makes sense for the project, I reach for Postgres. MySQL may have better GUI tools and I'm sure that's important for some people, but PostgreSQL just works more like I want / need a database to work. For the kind of work I do (non trivial queries with a significant degree of write operations), it's as fast or faster than MySQL in any area that matters.
If you don't see any perceived benefit to using a more robust, more compatible SQL implementation, then you probably aren't using a lot of what most RDBMS systems have to offer. And that's fine! There are plenty of places where people are using a database as a glorified storage box for object persistence where any fancy SQL stuff is almost a waste and that's a place where something like Drizzle makes a lot of sense.
Actually, Howell claims he never downloaded any music. According to his testimony, the music files on his PC were ripped from CDs he owns. He used KaZaa to download porn and free e-books which he gave KaZaa the right to "share". At the heart of his defense is the idea that KaZaa searched his hard drive for media that was never intended to be shared and made that available without his knowledge or consent.
While this does weaken the RIAA's case, they still have a decent shot at conviction. All that was denied here was a shot at summary judgement. At issue here is the idea that making a copy of a protected work available is not the same as copying, but may leave the defendant open to contributory liability.
Howell contends he never intended to share, nor authorized KaZaa to share his music files and it may not be possible for the RIAA to prove otherwise.
For what it's worth, he also poked holes in EFF's argument that Media Sentry - as an agent of the RIAA, cannot infringe on their own copyright. He argues that the RIAA / et all never intended to license Media Sentry to authorize distribution or reproduction and therefore the 12 copies Media Sentry downloaded stand up as "unauthorized" copies of the works. The issue remains open as to whether Howell can be held liable for these copies.
1. Surround yourself with people who are good at things that you aren't. When you work together, you can all shine in ways that would be less impressive individually. (P.S. The best place to find these people, is the local inn.) 2. Take on challenges no one else dares to. It could all end badly, but nothing extraordinary ever happens that doesn't begin with taking a chance. (P.S. It will certainly go badly, but with luck it won't end badly.) 3. Respect everyone's religious beliefs regardless of your own. Being on the wrong end of a divine intervention really, really sucks. 4. Never underestimate the importance of luck. There is really almost no situation that a well rolled natural '20' can't get you out of. 5. Search everything no matter how disgusting it is. You'd be surprised where kobolds will decide to hide their treasure.
I use: Solaris, Linux, Mac OS X, Windows (2k3,xp,vista) on a daily basis. Each has their strong points.
In direct comparison to "white box" commodity PC hardware that you build yourself, Macs are more expensive.
In direct comparison to brand name premanufactured computers with identical specs (processor, RAM, storage, I/O, display etc) Macs are competitive.
The biggest Mac Gotcha is that their "Real" Warranty (Applecare) is an optional add-on. This is to keep the prices competitive. Dell does the same thing. However it's not really optional because if your logic board dies on the 368th day after you bought it, you're out a whole lot of money to get it replaced.
That's really it. That's the one big drawback to Macs at this point.
Macs can actually run MORE software than a comparable Windows machine because they can run anything a standard PC can run (in a VM like Parallels or VM Fusion, via WINE, Crossover Office, Boot Camp) plus any specialized Mac Apps that you desire (Logic Pro Audio and Final Cut Studio HD come to mind).
In terms of free software, most everything "just compiles" If you don't want to compile, use Fink for "Debian Style" package management. Installing Support for X is actually very easy. You go back to your OS CD and do an optional install of just X windows. No conf files, no fiddling. It "just works", with multiple video cards, multiple monitors, with whatever.
Macs are generally fast, reliable and come with the only Unix desktop implementation that my mother can use without asking me for help. I'd say that's an accomplishment. Shockingly, they're not for everyone. Just like Linux isn't, just like Windows isn't.
Use what makes you productive and creative. Use what you like and what makes you happy. Over the life of a computer, a few hundred dollars spent or saved is probably a whole lot less important than the experience you have when you use it on a day to day basis.
Diversity is good for everyone. Not all wheels fit all vehicles. Good thing there are thousands of types of them out there. Can you imagine if everyone had to use the same tires for every vehicle? What a mess that would be. There's a difference between standards and monoculture.
Pulled from the actual Report itself (Internet Scurity Threat Report XI) from Symantec -
With the exception of Microsoft, all vendors were affected by longer turnarounds for patches for third-
party components that are distributed with each operating system. Upon examining the sample set
of vulnerabilities during this period, Symantec has observed that vulnerabilities with longer patch
development times generally affected third-party components. The previous issue of the Symantec
Internet Security Threat Reportcommented on the relevance of this issue for commercial UNIX vendors
such as HP and Sun,but it holds true for all vendors of UNIX/Linux-based operating systems.
And of course:
As with previous periods, Microsoft Windows was the operating system that had the most vulnerabilities with
associated exploit code and exploit activity in the wild. This may have pressured Microsoft to develop
and issue patches more quickly than other vendors. Another pressure that may have influenced
Microsoft's relatively short patch development time is the development of unofficial patches by third-
parties in response to high-profile vulnerabilities.
As always, the most secure computer is the one that is turned off, and unplugged from the network.
No security model is perfect, but I'd take any *nix for a web facing server any day.
It only sounds like that if you skip the important parts.
Agile methods are not about skipping requirements, or modeling, nor about coding in a casual or non-deliberate way.
Agile methods are about recognizing that requirements are a moving target, That the more you implement your solution, the better you will understand the model, and possible problems with your model of the problem domain, and that the best program on earth is worthless if it doesn't work for the end users.
So, there's a large collection of techniques that most programming veterans (OO or otherwise) utilize to help get things up and running without having to send anyone "over the waterfall."
If DX were open source.. those who wanted XP support could just fork the project and deal with the technical issues themselves. That said, this is a legitimate business issue, and MS has every right to move forward with a cleaner API and implementation and if that means no backwards compatibility, then so be it.
That's right, all of the best software engineers in the world are working for Sun and everyone else is on crack... and Linux is losing to Solaris in such a big way on Wall St. and Sun have been able to keep using their same old development methodologies, don't change what works right?
You're right. Some of the best software engineers in the world are working for Sun. Sun's been hammered in the market place because it didn't react well to the dot-com bust. No layoffs, no significant restructuring or refocusing for years. Everyone cut margins and moved to commodity hardware, except Sun. (Note - Times have changed, see Galaxy and Coolthreads lines) The fact that Linux is "great" is precisely because it adheres to many of the design principals of a Unix-type Operating System and because it's free -- as in freedom, not beer. I also happen to think the BSDs are great, and that they've contributed a lot to the F/OSS community. But if you can't see all the amazing things coming out of the Open Solaris project that I just wish was in Linux, then there's no use even discussing it with you.
Sun has it's problems, but the engineers there are not one of them, and frankly you seem to be implying that they re somehow trying to impede progress or shut developers out of Open Solaris. On the contrary, they're working with Open Solaris contributors every single day. Let's not confuse high standards with a lack of enthusiasm for community building.
By your logic, Microsoft operating systems must be technically superior to Linux, because of both profit margin and marketshare right?
SuSE and KDE both have some German roots which is probably a big reason for it. Linux is outrageously popular in Germany and that means that (much like here) on any given day there are more Linux admins looking for a job than Solaris admins, which drives costs down.
Slashdot Mirror
---
we are a startup with almost a year live. None of the employees have ownership/stock and all are salary
---
No one is invested in the future of the company or what happens to the product because no one is going to be rewarded if things go well. Without ownership or profit sharing of some sort, no one who is worth anything will stick around to work 11 hour days unless the work environment is so amazing that they can get compensated other ways. The reality is, without profitability, those alternative means of compensation (extra hardware/software budget, extra flex time/vacation time, etc) won't hold up for long. It sounds like you are working for someone who has read Spolsky but really has no idea what he's on about. Does your SDLC pass the Joel test? (one step builds, testing, source control, bug database, etc etc). Are you working on brand new computers with at least 2 big monitors and more ram and storage space than any reasonable person should ever need? Do you get to set your own schedules as long as you are meeting deadlines/goals/pushes? Are you in offices or cubicles? If cubicles does everyone have a good pair of headphones? Are the cubicles or offices big enough? Is it acceptable for people to take a break and surf slashdot/Youtube/CNN for a few minutes when their brain buffer is blown and they can't concentrate? I'm not talking about come in and surf for 10 hours, but is it an environment where everyone has to be ultra careful about what's up on their screen and makes extra effort to look busy or stressed out enough to be taken seriously or is it the sort of place where people are treated like adults and given the benefit of the doubt as long as they're getting their commits in, QA'd, and past testing by the next milestone/goalpost/sprint/push/whatever?
If you are working for a startup, you really should believe in and be passionate about the product and the company and they should be passionate about you and your team! If it's really such a great idea there ought to be room for ownership and compensation for everyone involved on the ground floor and even the first couple of floors. People are what make a company great. It takes strong leaders, it takes a lot of faith and inspiration in what you are doing and it takes talented and hard working teams who are united in a common goal of making the best damn whatsy-whosit that's ever been dreamed of.
From your post it sounds like you're talking about a half baked company with tolerable but not stellar management and whatever talent the going market rate could buy. Which can be anywhere from pretty good, to so-so to absolutely dismal depending on a lot of factors.
Saying, "I just need a programmer" is a lot like saying, "I could totally get this car running if I just had a tool." What kind of tool were you looking for? An OBD-II reader, a flathead screwdriver? a 9mm socket wrench? A hydraulic lift bay? Not all programmers are created equal, and they are not equivalent cogs that can be removed and replaced at will without regard or consequence. Surely there are programmers that are more valuable than others, just like there are works of art or engineering that are more prized than others. There is a widely accepted myth among the industry that nearly everything is a computer solvable problem. At the same time, the technology professionals who will be expected to solve these problems with the aid of technological tools such as hardware and software are often considered a minor and inconsequential part of the equation, without value or merit beyond performing a specific task. Often we are told not only what problem to solve, but how we are expected to solve it. Usually by people who haven't the faintest notion what they are asking for.
Trying not to repeat earlier suggestions, (though Tesla has always been a personal hero)
How about Chuck Yeager, fighter pilot, test pilot, first person to break the sound barrier.
Any and all of the Mercury Seven astronauts. If your son has any doubts, sit him down in front of a copy of "The Right Stuff", he'll come around.
I actually had DSL in 98-99. Relevant factors = Seattle suburbs, Covad business class DSL that we split a cost of around 300 a month for and for the record it was the best DSL service I ever had (SDSL at that) . They pulled ethernet right up to the house, and put a jack in, we plugged that right into our router (10mb if I remember correctly) and that was that. ran wires to every room of the house and we were all set. I've had most permutations of broadband since then, and I'm currently on cable. Tried ADSL a bunch of times but I can never seem to get the 'good' speeds no matter where I live.
Maybe if 3D actually worked for more people, was used in ways that improved the overall storytelling process and was less expensive, you wouldn't hear so many criticisms of it. It works for me, marginally, but I usually end up with a headache and after a few minutes I lose interest. It ruins immersion for me, whether it's a game, or a movie so it's safe to say I'm not a big fan.
In so many areas of scientific research, who is funding the study says more about the outcome and conclusions than almost anything else. So whether you're talking about climate change and greenhouse gases, whether it's safe to add more ethanol to our gasoline, whether certain products or procedures have medical benefit that outweighs the risks, or just about anything else, keep your eyes open, keep your mind open, and follow the money trail.
Not really true. They can always find *someone* who is ready and willing, but that is a far cry from having any man they desire. Once you get to know a girl or two, you'll probably realize they have to work at it a bit too, and it all evens out in the end.
In the real world, your subjective perception is often all you will EVER have to go on. Make as reasonably informed a decision as you can, and live with those consequences. A lot of so called objective studies especially in technology are quite biased. A DBA whose primary focus is Oracle would end up with completely different results than one who works primarily with DB/2 or PostgreSQL or MySQL. That's because each of these databases has different strengths, weaknesses, idiosyncracies, and yes, SQL idioms that make them perform better when done a certain way. The parsers are different, the optimizers are different, the table structures are different, why are you expecting an apples to apples comparison on features?
Sure, there are companies out there doing it right or at least trying, but there are many who are looking to
1. Replace experienced workers with inexperienced ones at half to 2/3rds salary.
2.Hire architects to design and document complex systems and then hire the equivalent of janitors to do maintenance and upgrade work. Eventually the center cannot hold and you end up with a complex nest of band aids and workarounds worthy only of submission to TDWTF.
3.Replace creative thinking, problem solving and innovation with documentation of procedure whereby routine tasks are accomplished by following rote procedures and recipes that a trained monkey can follow, but which don't really address all the real world failure points in the process or how to even detect them much less correct them. Worse yet, since policy is to follow the procedure, updating said procedure is usually next to impossible to get approved.
Most of this comes from a fundamental mistrust and misunderstanding of the value and role of IT within an organization. IT as a whole is viewed as a sausage grinder into which many companies pour their most critical business problems and hope that what comes out is a solution everyone can stomach. IT doesn't fix business problems, it fixes Information and automation problems. If you make poor decisions and ask IT to implement them, and the whole thing goes up in flames it doesn't mean IT failed you and many companies don't seem to grasp that.
The issue with your argument is that not all cars are created equal. Many cars on the road are equipped to operate well above operating tolerances assumed for these so called 'maximum safe speeds.' That said, the problem isn't the cars, it's the drivers. No matter how awesome your car is, the real limiting factor is the other people you share the road with. If you want to be remotely responsible about it, you have to assume a bare minimum of driving ability from each and every other driver on the road with you.
Your sudden lane change to avoid creaming them while they crawl along in the fast lane, even though you've been approaching them at high speed for the last minute and a half doesn't mean they won't see your front grill in the rear view and immediately swerve into the lane they should have been driving in in the first place. You see, your reasonable expectation that they won't drift into your lane as you attempt to pass goes right out the window when put up against their important cell phone call, while they're trying to pick spinach out of their teeth from lunch and change the DVD for the three kids in the back.
For your safety and theirs, it's always best to drive as conservatively and defensively as possible. No matter how much less fun it is. Find a track, or a truly deserted place to let loose instead of your local interstate.
There are all kinds of different 'coders' these days. They have their own idioms, ideals, tools and culture. You will find people who will try to convince you that Python is the Holy Grail, others will tell you that Ruby is the one true path. (Although usually the story is so over the top, you end up missing the simplicity and beauty of Ruby, all you know is she got "Railed" for three days straight and is now servicing millions of requests, at least when she's not busy batting eyelashes at some Mongrel or really anybody as long as they have a really Fast CGI.)
Most development these days is taking place between all these tubes that make up the interwebs. That means you're usually looking at something that runs on, through or near some sort of web or app server. Set yourself up with a local web server or app server configured with whatever jingles your bells, and get to it. There is no right or wrong way to go about it, and even if you kiss a lot of frogs, you'll eventually find your favorite way to php/jruby/jython/plone/java/flex/lasso/squeak/perl_mod/whatever your way into web programming and Service Oriented Architecture (Which is just a fancy way of saying functions (which are now methods) are actually now web services, that you call remotely (But not like COM or CORBA remotely) but more like REST or SOAP remotely, but at the end of the day they do the same darn thing. Along the way if anyone asks you about relational databases, give them a smug look, shake your head knowingly and walk off muttering something about an impedance mishmash and threaten to hibernate until they propel the conversation elsewhere.
Of course, none of this is going to matter because the world will end tomorrow. Now if you'll excuse me, I need to pack my towel and go get some beer.
The people who are using it to cause damages already know how this is done. The only dangerous part about something like this is that the public might be made aware of just how far from secure most financial transactions are.
There are lots of views on morality, but for me personally, I'd say yes, cheating is ALWAYS bad, because above all, it's dishonest. More than that though, you are cheating yourself, and your professed parter, and even your person on the side out of a chance at a real love relationship. If you have real and significant problems with your spouse, get those issues out in the air. If they can't be worked on between the two of you, get some counseling, or get some papers filed. It's really that simple. "Staying together for the kids" only teaches the children that abuse and unhappiness are okay as long as you can justify it to yourself. Besides, they learn almost everything about love relationships by watching their parents. If you don't love someone, but you're staying with them anyway, expect your kids will do the same until or unless they learn better. It's a complex problem to be sure, mainstream media has stressed the fairy tale courtship, where the magic of love is all about finding the right person. Unfortunately most people find out falling in love and living in love can be rather different. If you find the right person though, and you inspire each other to each be the right person for one another then you may wake up every day feeling like you are the luckiest person alive.
I fixed it for you. This is /. after all:
The sooner MS can kill it self off, the better the entire planet will be.
I use MySQL and PostgreSQL every day and whenever I have a choice, and if it makes sense for the project, I reach for Postgres. MySQL may have better GUI tools and I'm sure that's important for some people, but PostgreSQL just works more like I want / need a database to work. For the kind of work I do (non trivial queries with a significant degree of write operations), it's as fast or faster than MySQL in any area that matters. If you don't see any perceived benefit to using a more robust, more compatible SQL implementation, then you probably aren't using a lot of what most RDBMS systems have to offer. And that's fine! There are plenty of places where people are using a database as a glorified storage box for object persistence where any fancy SQL stuff is almost a waste and that's a place where something like Drizzle makes a lot of sense.
Actually, Howell claims he never downloaded any music. According to his testimony, the music files on his PC were ripped from CDs he owns. He used KaZaa to download porn and free e-books which he gave KaZaa the right to "share". At the heart of his defense is the idea that KaZaa searched his hard drive for media that was never intended to be shared and made that available without his knowledge or consent.
While this does weaken the RIAA's case, they still have a decent shot at conviction. All that was denied here was a shot at summary judgement. At issue here is the idea that making a copy of a protected work available is not the same as copying, but may leave the defendant open to contributory liability.
Howell contends he never intended to share, nor authorized KaZaa to share his music files and it may not be possible for the RIAA to prove otherwise.
For what it's worth, he also poked holes in EFF's argument that Media Sentry - as an agent of the RIAA, cannot infringe on their own copyright. He argues that the RIAA / et all never intended to license Media Sentry to authorize distribution or reproduction and therefore the 12 copies Media Sentry downloaded stand up as "unauthorized" copies of the works. The issue remains open as to whether Howell can be held liable for these copies.
1. Surround yourself with people who are good at things that you aren't. When you work together, you can all shine in ways that would be less impressive individually. (P.S. The best place to find these people, is the local inn.)
2. Take on challenges no one else dares to. It could all end badly, but nothing extraordinary ever happens that doesn't begin with taking a chance. (P.S. It will certainly go badly, but with luck it won't end badly.)
3. Respect everyone's religious beliefs regardless of your own. Being on the wrong end of a divine intervention really, really sucks.
4. Never underestimate the importance of luck. There is really almost no situation that a well rolled natural '20' can't get you out of.
5. Search everything no matter how disgusting it is. You'd be surprised where kobolds will decide to hide their treasure.
I use: Solaris, Linux, Mac OS X, Windows (2k3,xp,vista) on a daily basis. Each has their strong points.
The biggest Mac Gotcha is that their "Real" Warranty (Applecare) is an optional add-on. This is to keep the prices competitive. Dell does the same thing. However it's not really optional because if your logic board dies on the 368th day after you bought it, you're out a whole lot of money to get it replaced.
That's really it. That's the one big drawback to Macs at this point.
Macs can actually run MORE software than a comparable Windows machine because they can run anything a standard PC can run (in a VM like Parallels or VM Fusion, via WINE, Crossover Office, Boot Camp) plus any specialized Mac Apps that you desire (Logic Pro Audio and Final Cut Studio HD come to mind).
In terms of free software, most everything "just compiles" If you don't want to compile, use Fink for "Debian Style" package management. Installing Support for X is actually very easy. You go back to your OS CD and do an optional install of just X windows. No conf files, no fiddling. It "just works", with multiple video cards, multiple monitors, with whatever.
Macs are generally fast, reliable and come with the only Unix desktop implementation that my mother can use without asking me for help. I'd say that's an accomplishment. Shockingly, they're not for everyone. Just like Linux isn't, just like Windows isn't.
Use what makes you productive and creative. Use what you like and what makes you happy. Over the life of a computer, a few hundred dollars spent or saved is probably a whole lot less important than the experience you have when you use it on a day to day basis.
Diversity is good for everyone. Not all wheels fit all vehicles. Good thing there are thousands of types of them out there. Can you imagine if everyone had to use the same tires for every vehicle? What a mess that would be. There's a difference between standards and monoculture.
And of course:
As with previous periods, Microsoft Windows was the operating system that had the most vulnerabilities with associated exploit code and exploit activity in the wild. This may have pressured Microsoft to develop and issue patches more quickly than other vendors. Another pressure that may have influenced Microsoft's relatively short patch development time is the development of unofficial patches by third- parties in response to high-profile vulnerabilities.As always, the most secure computer is the one that is turned off, and unplugged from the network.
No security model is perfect, but I'd take any *nix for a web facing server any day.
It only sounds like that if you skip the important parts.
Agile methods are not about skipping requirements, or modeling, nor about coding in a casual or non-deliberate way.
Agile methods are about recognizing that requirements are a moving target, That the more you implement your solution, the better you will understand the model, and possible problems with your model of the problem domain, and that the best program on earth is worthless if it doesn't work for the end users.
So, there's a large collection of techniques that most programming veterans (OO or otherwise) utilize to help get things up and running without having to send anyone "over the waterfall."
Check out Dave Thomas and Andy Hunt, Martin Fowleror the Portland Pattern Repository for a good starting point.
If DX were open source.. those who wanted XP support could just fork the project and deal with the technical issues themselves. That said, this is a legitimate business issue, and MS has every right to move forward with a cleaner API and implementation and if that means no backwards compatibility, then so be it.
You're right. Some of the best software engineers in the world are working for Sun. Sun's been hammered in the market place because it didn't react well to the dot-com bust. No layoffs, no significant restructuring or refocusing for years. Everyone cut margins and moved to commodity hardware, except Sun. (Note - Times have changed, see Galaxy and Coolthreads lines) The fact that Linux is "great" is precisely because it adheres to many of the design principals of a Unix-type Operating System and because it's free -- as in freedom, not beer. I also happen to think the BSDs are great, and that they've contributed a lot to the F/OSS community. But if you can't see all the amazing things coming out of the Open Solaris project that I just wish was in Linux, then there's no use even discussing it with you.
Sun has it's problems, but the engineers there are not one of them, and frankly you seem to be implying that they re somehow trying to impede progress or shut developers out of Open Solaris. On the contrary, they're working with Open Solaris contributors every single day. Let's not confuse high standards with a lack of enthusiasm for community building.
By your logic, Microsoft operating systems must be technically superior to Linux, because of both profit margin and marketshare right?
SuSE and KDE both have some German roots which is probably a big reason for it. Linux is outrageously popular in Germany and that means that (much like here) on any given day there are more Linux admins looking for a job than Solaris admins, which drives costs down.
my 00000010
Nix