Looking back at that, and at your comment, some things come to mind:
* the tool Linus is pushing, greatly facilitates the idea of frequent, easy merges, and Linus mentions that a tool with great, fast merges, helps you merge early and often.
* on the other hand, your comment is about "you need to control when and how often [branches] are made...", while a big point of distributed SC tools is the opposite of that control: these tools make the power of the tool fully available to all users. A "main" repository may (and probably should) have permissions/hooks set to enforce some policy about what happens to what branches. Individual users can always create local quasi-branches by simply not checking things in; with a tool like they can can create real (local) branches too, which can then be promoted to official status (i.e. on a blessed central repository) if needed.
The deductibility of the expense of the car, isn't some magic that makes it free. It just means that, as with the cost of the phones and the paper and all the other stuff a businss uses, the dollars spent on those things are not profit, and thus are not taxed.
Most likely, assuming they win, he'd declare bankruptcy, give up most of his (likely very few, if he is as "kid"-list as other seem to say) assets, and thus pay only a tiny slice of whatever amount they win. This would be a major setback, but unfortunately not all that uncommon of one.
There are certainly some smart folks at the FCC... perhaps they could up with a policies to throw away the top few sources of complaints (just as statisticians sometimes throw away a few outliers), and make decisions on what matters to pursue, based on what's left.
Re:Getters/setters bad?
on
Holub on Patterns
·
· Score: 2, Insightful
I usually say something like this:
Map someMapINeed = new HashMap();
so that the implementation chosen (HashMap, the Java 1.2+ expression of the general idea of a hash table) is present only at that one spot, the rest of the code doesn't care about the Hashness of it, it just uses it as a Map.
It is a common "smell" in Java code, to refer to something specific (HashMap) in a parameter list (most commonly) when you only need the generic.
Regardless of who wins the presidency tomorrow, the next vacancy(s?) on the supreme court will be vacant for a long time; perhaps as long as several years. I wouldn't be surprised to see an extended period of time with only 5 justices, should they leave the court at a rate of more than one every few years.
Witness how effectively the minority Democrats in the Senate have held up federal judge nominations; will they be any less vigorous for the supreme court? Or if Kerry wins, consider that the Republicans in the senate (with a majority) could be even more effective in holding back any supreme court nomination.
Here is a point of view on this seems ideally balanced, to get flamed from both sides:
For a person to get to a high, constant level of drinking, is an act of great irresponbility and foolishness, a wrongdoing against oneself and everyone around.
Having gotten there, the enormous physiological difficulty in stopping, appears to be a bona fide disease.
Actually you'll also pay a lot because your car was parked in a large city when you weren't driving it. It's more likely to be stolen there than out in the middle of nowhere.
The power company would have to offer me more than "a couple bucks a month", to turn off my air conditioning during the periods when I need it most, which is to say during peak power use, which happens when it's really really hot outside.
Power companies are (apparently) in the business of selling power. When people want to buy a lot of it, they should be celebrating and happily vending, not looking for ways to get their customers not to buy so much.
I don't think you'd even need to look to the government to find this. Having all this data sounds potentially useful for the airlines and airports themselves, for marketing and whatever other purposes. It seem inevitable that that someone will notice that disk space is really cheap, and decide it would be convenient and helpful to go ahead and store the data in the airlines and airport's databases in addition to on the card. They may even offer this as a service you can pay for, to restore the data from a lost card.
It's a basic principle of information system design - remember all the data that come through the system by default, you can always decide to stop remembering it later, but if you build a system to discard some data, you can't un-discard it later.
When you do work for large firms, you learn that getting them to actually write a check for services rendered can be quite tedious. It really doesn't surprise me that all that a bill for domain renewal just sits there. It won't get paid until a "champion" makes sure it gets paid.
(As an aside, I find that we can't help but provide better, more responsive service, going the extra mile, for clients that pay their bills promptly without extra work on our part.)
The link/site above appears to be down. BitTorrent is quite remarkable, but it does require that the.torrent itself be hosted somewhere that stays up;-)
Been there, done that. There is certainly no need to be a jerk about it, nor to even mention how much easier it would be if you had admin rights on your own box. After the Nth time of coming over to your machine, someone sees the light.
It's really just a financial decision - it's too expensive to keep paying an IT guy to spend many minutes on something a developer could do in 1 minute, and way too expensive to pay the developer to sit idle from time to time waiting for someone else to come make some config change, etc.
As a customer, I wouldn't hire a firm/team based on their methodology talk, whether they're talking XP or RUP or whatever. I'd hire them based on their demonstrated ability to get useful software out the door, then hope they keep doing whatever they'be been doing.
That said, as a customer I'd want frequent delivery of working code, regardless of the specific process the team will be using to delivery it.
I second the Ecco recomendation. They're a little pricey, but quite comfortable (much more so than the lesser shoes that I replaced) and they don't set of metal detectors. In fact the last time I went through the security check, I took them off, and the guy said "ah, Ecco. These don't set off the detector, don't bother to take them off in the future".
My experience is that every application is mission critical to the company that owns it. They wouldn't be paying me to work on it if it wasn't data they want to not lose.
I personally wouldn't be upset if Slashdot lost a few comments here and there, but I'd guess that the folks who run slashdot.org take data loss pretty seriously.
[backing up your replication server? That's a pathetic solution]
In a way, it's pathetic that this is the only way to do it; in another direction, though, it's a very smart thing to move any activity that doesn't need to happen on the primary (bottleneck) server to a secondary server instead.
A similar practice is commonplace in the MS SQL Server world, running lengthly reporting queries on a secondary reporting database instead of on the primary.
As a potential buyer, I'd much prefer they drop the prices, discount them heavily, whatever.
But standing back and looking at Apple, I am impressed. They have created sufficient value (via a combination of product design and marketing) in the mind of the consumer that they can sell their product for the price they ask; they don't need to sell on price.
The answer is DVI. I have two 19" Samsung LCD monitors. With analog they were a little disappointing; with DVI they are fantastic. The image quality is excellent.
[most of it's components are a pain to try and extend.]
Indeed - most of the nicer third party controls (of which there are a great number) start "from scratch" rather than extend the corresponding built in control.
[Delphi has stack object creation (like C++), Java does not.]
This is not correct. Delphi can create records (structs) on the stack, but all objects are on the heap, like Java. As a result, Delphi code needs a lot of try/finally statements to make sure things get cleaned, lacking both the garbage collection of Java and the auto-free-when-out-of-scope of C++ (via smart pointers or heap allocated objects)
At they are now (private) they can grow and shrink as the market changes, making the founders ever richer (though not mega-rich) for years on end.
After an IPO, they either have to grow tremendously, or they'll likely end up bought or bankrupt (from the massive expenditures and risky choices taken in the process of trying to get huge)
Offhand, it seems like staying private would be a good choice. It's a choice between a high chance of being quite wealthy, and a low chance of being bill-gates-wealthy.
It's tremendously more feasible to do that with financial aid. The student, if of typical student age, will need parents (guardians, whatever) to fill out the forms to qualify for financial aid; so parents who refuse to fill out the forms, and also won't pay, can be a substantial obstacle to attending college. Not impossible to overcome, though - apparently it's possible to get some kind of legal separation from parents to get around that. I imagine there are some hurdles to clear with that, and that relatively few people in that situation have the saavy to go that far.
Re:Java's not exactly pining for the fields just n
on
Java vs .NET
·
· Score: 1
Yes, of course. In the talk (and probably in the slides I pointed to), I made the point repeatedly that Java is a platform and a market, with lots of vendors offering products like IDEs etc..NET is a market, but to a lesser extent, in the sense that Microsoft does (and will continue to) dominate the.NET market much more than Sun dominates Java.
Slashdot Mirror
I wrote about Linus's talk a few weeks ago:
b uted/
http://kylecordes.com/2007/05/17/linux-git-distri
Looking back at that, and at your comment, some things come to mind:
* the tool Linus is pushing, greatly facilitates the idea of frequent, easy merges, and Linus mentions that a tool with great, fast merges, helps you merge early and often.
* on the other hand, your comment is about "you need to control when and how often [branches] are made...", while a big point of distributed SC tools is the opposite of that control: these tools make the power of the tool fully available to all users. A "main" repository may (and probably should) have permissions/hooks set to enforce some policy about what happens to what branches. Individual users can always create local quasi-branches by simply not checking things in; with a tool like they can can create real (local) branches too, which can then be promoted to official status (i.e. on a blessed central repository) if needed.
The deductibility of the expense of the car, isn't some magic that makes it free. It just means that, as with the cost of the phones and the paper and all the other stuff a businss uses, the dollars spent on those things are not profit, and thus are not taxed.
Most likely, assuming they win, he'd declare bankruptcy, give up most of his (likely very few, if he is as "kid"-list as other seem to say) assets, and thus pay only a tiny slice of whatever amount they win. This would be a major setback, but unfortunately not all that uncommon of one.
There are certainly some smart folks at the FCC... perhaps they could up with a policies to throw away the top few sources of complaints (just as statisticians sometimes throw away a few outliers), and make decisions on what matters to pursue, based on what's left.
I usually say something like this:
Map someMapINeed = new HashMap();
so that the implementation chosen (HashMap, the Java 1.2+ expression of the general idea of a hash table) is present only at that one spot, the rest of the code doesn't care about the Hashness of it, it just uses it as a Map.
It is a common "smell" in Java code, to refer to something specific (HashMap) in a parameter list (most commonly) when you only need the generic.
A prediction:
Regardless of who wins the presidency tomorrow, the next vacancy(s?) on the supreme court will be vacant for a long time; perhaps as long as several years. I wouldn't be surprised to see an extended period of time with only 5 justices, should they leave the court at a rate of more than one every few years.
Witness how effectively the minority Democrats in the Senate have held up federal judge nominations; will they be any less vigorous for the supreme court? Or if Kerry wins, consider that the Republicans in the senate (with a majority) could be even more effective in holding back any supreme court nomination.
Here is a point of view on this seems ideally balanced, to get flamed from both sides:
For a person to get to a high, constant level of drinking, is an act of great irresponbility and foolishness, a wrongdoing against oneself and everyone around.
Having gotten there, the enormous physiological difficulty in stopping, appears to be a bona fide disease.
I have this image as wallpaper, spanned across two 19" LCDs.
Yes, it does fix the aspect ratio problem (almost, I intentionally leave off Antarctica to show the rest larger), and it makes fastastic "wallpaper".
Actually you'll also pay a lot because your car was parked in a large city when you weren't driving it. It's more likely to be stolen there than out in the middle of nowhere.
The power company would have to offer me more than "a couple bucks a month", to turn off my air conditioning during the periods when I need it most, which is to say during peak power use, which happens when it's really really hot outside.
Power companies are (apparently) in the business of selling power. When people want to buy a lot of it, they should be celebrating and happily vending, not looking for ways to get their customers not to buy so much.
I don't think you'd even need to look to the government to find this. Having all this data sounds potentially useful for the airlines and airports themselves, for marketing and whatever other purposes. It seem inevitable that that someone will notice that disk space is really cheap, and decide it would be convenient and helpful to go ahead and store the data in the airlines and airport's databases in addition to on the card. They may even offer this as a service you can pay for, to restore the data from a lost card.
It's a basic principle of information system design - remember all the data that come through the system by default, you can always decide to stop remembering it later, but if you build a system to discard some data, you can't un-discard it later.
Well, yes, companies do "forget" :-)
When you do work for large firms, you learn that getting them to actually write a check for services rendered can be quite tedious. It really doesn't surprise me that all that a bill for domain renewal just sits there. It won't get paid until a "champion" makes sure it gets paid.
(As an aside, I find that we can't help but provide better, more responsive service, going the extra mile, for clients that pay their bills promptly without extra work on our part.)
The link/site above appears to be down. BitTorrent is quite remarkable, but it does require that the .torrent itself be hosted somewhere that stays up ;-)
Been there, done that. There is certainly no need to be a jerk about it, nor to even mention how much easier it would be if you had admin rights on your own box. After the Nth time of coming over to your machine, someone sees the light.
It's really just a financial decision - it's too expensive to keep paying an IT guy to spend many minutes on something a developer could do in 1 minute, and way too expensive to pay the developer to sit idle from time to time waiting for someone else to come make some config change, etc.
I'm fairly pleased with XP myself.
But....
As a customer, I wouldn't hire a firm/team based on their methodology talk, whether they're talking XP or RUP or whatever. I'd hire them based on their demonstrated ability to get useful software out the door, then hope they keep doing whatever they'be been doing.
That said, as a customer I'd want frequent delivery of working code, regardless of the specific process the team will be using to delivery it.
I second the Ecco recomendation. They're a little pricey, but quite comfortable (much more so than the lesser shoes that I replaced) and they don't set of metal detectors. In fact the last time I went through the security check, I took them off, and the guy said "ah, Ecco. These don't set off the detector, don't bother to take them off in the future".
My experience is that every application is mission critical to the company that owns it. They wouldn't be paying me to work on it if it wasn't data they want to not lose.
I personally wouldn't be upset if Slashdot lost a few comments here and there, but I'd guess that the folks who run slashdot.org take data loss pretty seriously.
[backing up your replication server? That's a pathetic solution]
In a way, it's pathetic that this is the only way to do it; in another direction, though, it's a very smart thing to move any activity that doesn't need to happen on the primary (bottleneck) server to a secondary server instead.
A similar practice is commonplace in the MS SQL Server world, running lengthly reporting queries on a secondary reporting database instead of on the primary.
As a potential buyer, I'd much prefer they drop the prices, discount them heavily, whatever.
But standing back and looking at Apple, I am impressed. They have created sufficient value (via a combination of product design and marketing) in the mind of the consumer that they can sell their product for the price they ask; they don't need to sell on price.
The answer is DVI. I have two 19" Samsung LCD monitors. With analog they were a little disappointing; with DVI they are fantastic. The image quality is excellent.
[most of it's components are a pain to try and extend.]
Indeed - most of the nicer third party controls (of which there are a great number) start "from scratch" rather than extend the corresponding built in control.
[Delphi has stack object creation (like C++), Java does not.]
This is not correct. Delphi can create records (structs) on the stack, but all objects are on the heap, like Java. As a result, Delphi code needs a lot of try/finally statements to make sure things get cleaned, lacking both the garbage collection of Java and the auto-free-when-out-of-scope of C++ (via smart pointers or heap allocated objects)
Yes, exactly.
At they are now (private) they can grow and shrink as the market changes, making the founders ever richer (though not mega-rich) for years on end.
After an IPO, they either have to grow tremendously, or they'll likely end up bought or bankrupt (from the massive expenditures and risky choices taken in the process of trying to get huge)
Offhand, it seems like staying private would be a good choice. It's a choice between a high chance of being quite wealthy, and a low chance of being bill-gates-wealthy.
Indeed, lots of people have paid their own way.
However...
It's tremendously more feasible to do that with financial aid. The student, if of typical student age, will need parents (guardians, whatever) to fill out the forms to qualify for financial aid; so parents who refuse to fill out the forms, and also won't pay, can be a substantial obstacle to attending college. Not impossible to overcome, though - apparently it's possible to get some kind of legal separation from parents to get around that. I imagine there are some hurdles to clear with that, and that relatively few people in that situation have the saavy to go that far.
Yes, of course. In the talk (and probably in the slides I pointed to), I made the point repeatedly that Java is a platform and a market, with lots of vendors offering products like IDEs etc. .NET is a market, but to a lesser extent, in the sense that Microsoft does (and will continue to) dominate the .NET market much more than Sun dominates Java.