You know,
As someone who has to use a cell phone for business quite a bit (I travel at least one week a month) having the features of a cell phone combined with my PDA would be a god-send. For me personally, the only reason I don't have one is cost. I can't bring myself to spend $500 on something for 'work.'
I don't know about 'Mommy and Daddy' giving cell phones to thier kids, and, I don't really care. But, for a business user, more choices lead to lower prices.
My favorite part of the article: But for the choices to appear, software developers must write programs "so that they can register here," he said. When no third-party middleware installed, Microsoft software would appear in the list.
I'd be interested to see how difficult Microsoft makes it to register your program. And, I also find it interesting that they won't simply pick a different.exe file to use. You can only pick one from "the list."
I didn't, and I'm doing ok. (Well, better than ok.) But most of that was cause I was lucky.
I don't say this purely from a professional perspective, but from a social one. I would have rather spent my late teens and early 20's going to class and meeting chicks than working in a group home or unloading trucks on the overnight shift.
There are still plenty of places where you can do just fine without a degree. And those places won't really go away 100%.
But, a degree gives you a (small) edge, and you might as well party and get laid while you can. It's a whole lot harder to be a professional loafer when you're working 50 hours a week than it is to be one when you spend 15 hours a week in class, and maybe, that much on homework.
Unfortunately, that's only going to work for a little while. I know that here in MA, the licenses are changing over from a magnetic strip to a bar-code. Can't run a bar-code over a magnet to kill it.
You know if a company goes out of business, then the Director of Business Development evidently wasn't developing enough business. So, not only did he have a pretend job, but it could look like he wasn't even good at it.
I hope the cartoons work out, as he's found something he's good at.
As another consultant, I can tell you that spec changes always happen, after a customer has signed off on a project, and accepted the spec and the project plan. What's then done is a 'change request' or 'spec change'. (terminology varies)
You formalize the changes, provide an impact to the current project, and additional hours required produce the requested change.
If the entire process is as formalized as possible, it is quite possible for projects to be completed on time, or close to on time. Invariably, some projects will be done in less time, and some will be done in much longer than estimated time. But, experience and formalization of procedures leads to more accurate estimates over time.
If your most junior employee is writing project time estimates, you are going to have bigger problems than missing your milestones.
On that note, is Romulus really only 4 days at warp 4 from Earth? I don't remember the warp to km/sec ratio (or rather, I never knew it,) but that just seems really close.
One would think that if it only takes 4 days to get back and forth between the two planets, that the Klingons would have come to visit, long before this episode.
Any one with the (pseudo-)facts want to set me straight?
Re:XSL isn't the problem.
on
XML in a Nutshell
·
· Score: 3, Informative
I spend most of every day working with XSL and XML, and continually have to listen to people complain how hard XSL is. It's not. Though it's a different meathod of writing code than some people are used to, most people I work with, have no problem with it, once they break out of the C-type syntax of coding. Once you comprehend the template concept of development, XSLT is actually rather easy.
Don't get me wrong, there are limitations to the language, and hopefully, we'll see those limitations removed in 2.0.
But, if you can make the conceptual jump in coding styles, it can be very effictive.
But,
if you learn XSLT, it's quite easy to generate an style sheet that will output XHTML from your XML document. Also, if you ensure that your HTML is well formed, you can handle it as if it were XML.
Here in the greater boston area, it's quite common for houses to sell in less than a week and for apartments to rent in less than 24 hours. I current;y live in an apartment the we rented the first day it was listed. My roommate is moving to an apartment that was available for less the 24 hours.
By searching on-line, especially at Boston.com, you can see listings the day they go live, often prior to finding them in the paper. As you need to act fast if you want a good apartment here, searching on-line is a must.
Because the majority of apartments in town are rented through an agency, you still need to contact a realtor, however, it's much easier to approach a realtor with a list of places you want to see, that they had listed, than it is to sit down in thier office, to go through the listings.
As for buying on-line, the majority of people I know who have bought property in Metro Boston in the past two years have found their new home some how utilizing the Net.
As I stated above, people around here are still going to the realtor to see the place, prior to making an offer. (Though a $400k triple-decker house around the corner from me sold last summer, sight unseen in less than a week.)
Perhaps an AOLTW employee could tell us if they are getting AOL.com email addressed, in which case looks like everyone's going to have email addressed like BernardShaw666@aol.com, or is there some plan to use.net. It seems reasonable that AOL would have set aside some sort of mechanism to separate employees from customers, like any reasonable ISP. I know that when I worked at a company that offered email addresses, we used.net for the customers and.com for the employees (though most places seem to do the opposite.) Why wouldn't AOL just do the same? That way there would be significantly less chances of name collisions.
What was they're preexisting policy toward user addresses vs. employee addresses?
Oh, wait, AOL isn't a reasonable company...
According to the article, or at least to my limited understanding of it, each 'record' needs to be represented simultaneously on 'modulator.' Wouldn't this then cause a restriction on the size of your computer, based on the size of the modulator?
As a 'dreaded' consultant, I often have to talk with co-workers and sometimes even customers via an IM client. While I would prefer to use Jabber, it's really not possible to expect someone who can't make the Office Paperclip guy disappear, to install a client other than "the one I use at home."
Slashdot Mirror
You know,
I don't know about 'Mommy and Daddy' giving cell phones to thier kids, and, I don't really care. But, for a business user, more choices lead to lower prices.As someone who has to use a cell phone for business quite a bit (I travel at least one week a month) having the features of a cell phone combined with my PDA would be a god-send. For me personally, the only reason I don't have one is cost. I can't bring myself to spend $500 on something for 'work.'
My favorite part of the article:
.exe file to use. You can only pick one from "the list."
But for the choices to appear, software developers must write programs "so that they can register here," he said. When no third-party middleware installed, Microsoft software would appear in the list.
I'd be interested to see how difficult Microsoft makes it to register your program. And, I also find it interesting that they won't simply pick a different
Not very modular.
I didn't, and I'm doing ok. (Well, better than ok.) But most of that was cause I was lucky.
I don't say this purely from a professional perspective, but from a social one. I would have rather spent my late teens and early 20's going to class and meeting chicks than working in a group home or unloading trucks on the overnight shift.
There are still plenty of places where you can do just fine without a degree. And those places won't really go away 100%.
But, a degree gives you a (small) edge, and you might as well party and get laid while you can. It's a whole lot harder to be a professional loafer when you're working 50 hours a week than it is to be one when you spend 15 hours a week in class, and maybe, that much on homework.
Unfortunately,
that's only going to work for a little while. I know that here in MA, the licenses are changing over from a magnetic strip to a bar-code.
Can't run a bar-code over a magnet to kill it.
You know if a company goes out of business, then the Director of Business Development evidently wasn't developing enough business.
So, not only did he have a pretend job, but it could look like he wasn't even good at it.
I hope the cartoons work out, as he's found something he's good at.
Actually the international date line is in the Pacific because it's 180 from Greenwich England, which at the time was used as an arbitrary 0 point.
3) Go and code it, no spec changes allowed.
As another consultant, I can tell you that spec changes always happen, after a customer has signed off on a project, and accepted the spec and the project plan. What's then done is a 'change request' or 'spec change'. (terminology varies)
You formalize the changes, provide an impact to the current project, and additional hours required produce the requested change.
If the entire process is as formalized as possible, it is quite possible for projects to be completed on time, or close to on time. Invariably, some projects will be done in less time, and some will be done in much longer than estimated time. But, experience and formalization of procedures leads to more accurate estimates over time.
If your most junior employee is writing project time estimates, you are going to have bigger problems than missing your milestones.
On that note, is Romulus really only 4 days at warp 4 from Earth? I don't remember the warp to km/sec ratio (or rather, I never knew it,) but that just seems really close.
One would think that if it only takes 4 days to get back and forth between the two planets, that the Klingons would have come to visit, long before this episode.
Any one with the (pseudo-)facts want to set me straight?
I spend most of every day working with XSL and XML, and continually have to listen to people complain how hard XSL is. It's not. Though it's a different meathod of writing code than some people are used to, most people I work with, have no problem with it, once they break out of the C-type syntax of coding. Once you comprehend the template concept of development, XSLT is actually rather easy.
Don't get me wrong, there are limitations to the language, and hopefully, we'll see those limitations removed in 2.0.
But, if you can make the conceptual jump in coding styles, it can be very effictive.
But,
if you learn XSLT, it's quite easy to generate an style sheet that will output XHTML from your XML document. Also, if you ensure that your HTML is well formed, you can handle it as if it were XML.
Here in the greater boston area, it's quite common for houses to sell in less than a week and for apartments to rent in less than 24 hours. I current;y live in an apartment the we rented the first day it was listed. My roommate is moving to an apartment that was available for less the 24 hours.
By searching on-line, especially at Boston.com, you can see listings the day they go live, often prior to finding them in the paper. As you need to act fast if you want a good apartment here, searching on-line is a must.
Because the majority of apartments in town are rented through an agency, you still need to contact a realtor, however, it's much easier to approach a realtor with a list of places you want to see, that they had listed, than it is to sit down in thier office, to go through the listings.
As for buying on-line, the majority of people I know who have bought property in Metro Boston in the past two years have found their new home some how utilizing the Net.
As I stated above, people around here are still going to the realtor to see the place, prior to making an offer. (Though a $400k triple-decker house around the corner from me sold last summer, sight unseen in less than a week.)
Perhaps an AOLTW employee could tell us if they are getting AOL.com email addressed, in which case looks like everyone's going to have email addressed like BernardShaw666@aol.com, or is there some plan to use .net. It seems reasonable that AOL would have set aside some sort of mechanism to separate employees from customers, like any reasonable ISP. I know that when I worked at a company that offered email addresses, we used .net for the customers and .com for the employees (though most places seem to do the opposite.) Why wouldn't AOL just do the same? That way there would be significantly less chances of name collisions.
What was they're preexisting policy toward user addresses vs. employee addresses?
Oh, wait, AOL isn't a reasonable company...
According to the article, or at least to my limited understanding of it, each 'record' needs to be represented simultaneously on 'modulator.' Wouldn't this then cause a restriction on the size of your computer, based on the size of the modulator?
As a 'dreaded' consultant, I often have to talk with co-workers and sometimes even customers via an IM client. While I would prefer to use Jabber, it's really not possible to expect someone who can't make the Office Paperclip guy disappear, to install a client other than "the one I use at home."