Once they're comfortable in their current state they can work on improving it. You can't focus on learning new skills or searching for a job if you have to find a blanket for tonight or you'll freeze to death. Almost everyone isn't going to hire a homeless bum, so they need enough stuff to make themselves not look homeless. They get those things as handouts on the street, from picking through the trash, or from robbing people.
The problem is that when we give them money for begging, they go use that money for a little bit of food and a whole lot of whatever it is they are self medicating with. Change is uncomfortable and doubly so for someone who is a substance abuser. There are charities who help people who want to get off the street and your money is much better spent there since they can help more effectively by providing food, clean clothing, a place to stay and help for whatever emotional problems or mental illness that made them end up on the streets to begin with.
Actually it's worse than that, by giving them money you are making them comfortable in their current state and that keeps them from getting the actual help they need.
Here is the flaw with that thought: Vaccinations are down in some areas but there have been no reductions in the Autism diagnosis rates so the anti vaccination crowd have inadvertently disproved their own theory.
That attitude is everything wrong with your country right now. Just because he disagrees with you about what is best does not mean he is less worthy to be American.
As a Canadian, I can tell you that most provinces have a few months wait between the time you take up residence and the time you can get health insurance.
If you've ever met anyone from Cuba they will tell you that the outside world is nothing like what they are told on the news. How is that not propaganda?
This statement always hits me as mind numbingly stupid. In general try / catch and other error managing statements are for the lazy that don't want to understand the environment and inputs well enough to write the proper code to manage them. You want rock solid code that will last for years, eliminate the errors, don't "handle them gracefully". The only exception to this rule should be when the native environment forces it upon you or there is a lack of some proper check "doesThisReallyExist()".
By errors I meant where paths and files don't exist, the user or external software sends bad info or someone runs or the machine runs out of resources. Case in point: someone edited one of our databases in a place I used to work and some software crashed hard when it grabbed a NULL value from the database leaving me to check the core dump to discover the problem.
2. Only reinvents the wheel when there is a measurable benefit in doing so..
I learn more reinventing the wheel and there is no substitute to working with code you are sure of and know how it's going to perform.
I agree with the rest.
I can see wanting to learn.. I can't see duplicating system libraries in a project. Some libraries (Libc in particular) have whole groups of programmers who are rather good at squeezing every last drop of speed out of the implementation, there are also things such as leap year handling that look simple but end up being harder than they look.
Library bugs would equate to a "measurable benefit" to reinventing the wheel. I am not saying you should never replace a library function only that it shouldn't be your first reflex. I would only suggest that you document why you created your alternative routine in your code somewhere so someone (or possibly you years down the road) can easily spot why it was used instead of the existing library function so there is not time wasted later rediscovering the bug.
I strongly disagree with this. While I admit that elegant code can have ugly portions refactoring will often be an improvement but the trick is to learn when refactoring will help and when it will be a waste of time. The worst programmers I know are the ones who say that "I don't have time to go back through my code". I have cleaned projects where the original coder did the same thing three different times or reinvented the wheel when there were better libraries. In fact, I have been also guilty of this and even in my own projects I have come across places where the requirements changed out from under me mid project or I simply see better ways of doing things as I gain experience.
Elegant code: 1 Handles errors gracefully 2. Only reinvents the wheel when there is a measurable benefit in doing so. 3. Has consistent naming conventions. 4. Has comments around ugly code explaining why it is ugly. 5. Compiles (or runs if interpreted) without warnings.
Groupe Telecom used to be like that since they considered themselves too big to fail (or rather too big to be taken down). I had a decent job until the final months of the job where my boss (Leo Kuvayev before his infamous spammer days) decided to team up with Alan Ralsky and Spam the crap out of some porn sites. Before they started they were assured by their account manager that all complaints would be ignored. After trying to talk them out of it I quit and moved on to another job.
A few months later I ran into my replacement in an elevator while he was searching for new hosting. It seems Group "Were a billion dollar company" Telecom were forced to change their policy thanks to multiple blacklists that did a lot of damage to their business.
Non smart Samsung phones. I actually just got burned by this a few months ago when I grabbed something cheap to last me the month between when my old phone was stolen and when my new one arrived.
In reality, Google only offers 99.9% per month (99% for "reduced availability", I'm not sure what these prices are for) and the value of the guarantee is pathetic: they credit (not even refund) you a maximum of half your bill that month if availability is =95%. They could be down a full day and only knock 25% of you bill next month. That can barely be considered an SLA.
In my experience that is even better than most SLAs I've seen. Standard is to prorate the month and reduce that month's bill or add a credit to the next for the amount down so if you are paying $1000 monthly and you are down a day you get $33.40 back (assuming 30 days in the month).
Germany does it by being a lot more picky about what courses they cover and they only allow as many students as the job market will allow for into the programs.
This has nothing to do with internal combustion vs electric and everything to do with the fact that Tesla is removing the car dealers from the chain and the middlemen want to keep their share.
He didn't say spoofing, he said transiting, so they are people who have their own IP blocks assigned and are using those. The advantage is that you can have multiple uplinks and use the second as backup if your primary goes down and all of the ips never change.
Not exactly, they want Google to qualify as a telecom or cable provider when, in fact, they don't qualify as either since they only provide internet access and not phone or TV broadcasts,
Desktop are more ergonomic and tend to have larger screens and (sometimes) better keyboards. I spend 8 to 10 hours a day on the computer and I can tell you that it really matters if the screen is at the right height and the keyboard at the right angle.
If I had to guess, I'd guess that the website uses the password to authenticate to a mainframe somewhere and is just a front end for some EDBIC based protocol so cracking the website wouldn't get access to the actual list.
Not that it excuses the short limit, but then I'm hard pressed to find something better considering our banks all got together and designed a PayPal competitor that A. Is designed not to compete with their credit card processing system. B. Is designed around clicking links in emails.
Not all of my passwords can be that long. My bank password (the one I care about the most) has a 5 char limit and and I hate random passwords. I came across a good method a few years ago for generating passwords that need to be short: Take a song and chose a line then take the first character of each word and you have an easy to remember but hard to guess password.
Ubuntu tries to allow you to do major upgrades in place, but after a year or two you have to reinstall to clear out the crud.
Say what? Unless something has really changed between Debian and Ubuntu there really shouldn't be much crud being built i`since it provides a remove feature for obsolete dependencies. I have been running Debian for over a decade and I only reinstall for server replacement or corrupted drives.
Slashdot Mirror
You're wrong.
Once they're comfortable in their current state they can work on improving it. You can't focus on learning new skills or searching for a job if you have to find a blanket for tonight or you'll freeze to death. Almost everyone isn't going to hire a homeless bum, so they need enough stuff to make themselves not look homeless. They get those things as handouts on the street, from picking through the trash, or from robbing people.
The problem is that when we give them money for begging, they go use that money for a little bit of food and a whole lot of whatever it is they are self medicating with. Change is uncomfortable and doubly so for someone who is a substance abuser. There are charities who help people who want to get off the street and your money is much better spent there since they can help more effectively by providing food, clean clothing, a place to stay and help for whatever emotional problems or mental illness that made them end up on the streets to begin with.
Actually it's worse than that, by giving them money you are making them comfortable in their current state and that keeps them from getting the actual help they need.
Here is the flaw with that thought: Vaccinations are down in some areas but there have been no reductions in the Autism diagnosis rates so the anti vaccination crowd have inadvertently disproved their own theory.
That attitude is everything wrong with your country right now. Just because he disagrees with you about what is best does not mean he is less worthy to be American.
As a Canadian, I can tell you that most provinces have a few months wait between the time you take up residence and the time you can get health insurance.
I'm not American, and as someone who knows a few Cubans, I can tell you most of the country isn't like the tourist zones.
Depends what part of the US you are from. The Americans I talk to from red states seem to have more problems with that then the rest.
If you've ever met anyone from Cuba they will tell you that the outside world is nothing like what they are told on the news. How is that not propaganda?
1 Handles errors gracefully.
This statement always hits me as mind numbingly stupid. In general try / catch and other error managing statements are for the lazy that don't want to understand the environment and inputs well enough to write the proper code to manage them. You want rock solid code that will last for years, eliminate the errors, don't "handle them gracefully". The only exception to this rule should be when the native environment forces it upon you or there is a lack of some proper check "doesThisReallyExist()".
By errors I meant where paths and files don't exist, the user or external software sends bad info or someone runs or the machine runs out of resources. Case in point: someone edited one of our databases in a place I used to work and some software crashed hard when it grabbed a NULL value from the database leaving me to check the core dump to discover the problem.
2. Only reinvents the wheel when there is a measurable benefit in doing so..
I learn more reinventing the wheel and there is no substitute to working with code you are sure of and know how it's going to perform.
I agree with the rest.
I can see wanting to learn.. I can't see duplicating system libraries in a project. Some libraries (Libc in particular) have whole groups of programmers who are rather good at squeezing every last drop of speed out of the implementation, there are also things such as leap year handling that look simple but end up being harder than they look.
Library bugs would equate to a "measurable benefit" to reinventing the wheel. I am not saying you should never replace a library function only that it shouldn't be your first reflex. I would only suggest that you document why you created your alternative routine in your code somewhere so someone (or possibly you years down the road) can easily spot why it was used instead of the existing library function so there is not time wasted later rediscovering the bug.
I strongly disagree with this. While I admit that elegant code can have ugly portions refactoring will often be an improvement but the trick is to learn when refactoring will help and when it will be a waste of time. The worst programmers I know are the ones who say that "I don't have time to go back through my code". I have cleaned projects where the original coder did the same thing three different times or reinvented the wheel when there were better libraries. In fact, I have been also guilty of this and even in my own projects I have come across places where the requirements changed out from under me mid project or I simply see better ways of doing things as I gain experience.
Elegant code:
1 Handles errors gracefully
2. Only reinvents the wheel when there is a measurable benefit in doing so.
3. Has consistent naming conventions.
4. Has comments around ugly code explaining why it is ugly.
5. Compiles (or runs if interpreted) without warnings.
Groupe Telecom used to be like that since they considered themselves too big to fail (or rather too big to be taken down). I had a decent job until the final months of the job where my boss (Leo Kuvayev before his infamous spammer days) decided to team up with Alan Ralsky and Spam the crap out of some porn sites. Before they started they were assured by their account manager that all complaints would be ignored. After trying to talk them out of it I quit and moved on to another job.
A few months later I ran into my replacement in an elevator while he was searching for new hosting. It seems Group "Were a billion dollar company" Telecom were forced to change their policy thanks to multiple blacklists that did a lot of damage to their business.
Non smart Samsung phones. I actually just got burned by this a few months ago when I grabbed something cheap to last me the month between when my old phone was stolen and when my new one arrived.
In reality, Google only offers 99.9% per month (99% for "reduced availability", I'm not sure what these prices are for) and the value of the guarantee is pathetic: they credit (not even refund) you a maximum of half your bill that month if availability is =95%. They could be down a full day and only knock 25% of you bill next month. That can barely be considered an SLA.
In my experience that is even better than most SLAs I've seen. Standard is to prorate the month and reduce that month's bill or add a credit to the next for the amount down so if you are paying $1000 monthly and you are down a day you get $33.40 back (assuming 30 days in the month).
I already have a 2 TB nas stuffed with movies bit this has the advantage that it is off site.
If your house burns down your NAS goes with it. At least this way I have off site recovery.
Germany does it by being a lot more picky about what courses they cover and they only allow as many students as the job market will allow for into the programs.
This has nothing to do with internal combustion vs electric and everything to do with the fact that Tesla is removing the car dealers from the chain and the middlemen want to keep their share.
The real issue here is that you were filtering at the wrong point. It should have been your customers doing egress filtering in this case.
He didn't say spoofing, he said transiting, so they are people who have their own IP blocks assigned and are using those. The advantage is that you can have multiple uplinks and use the second as backup if your primary goes down and all of the ips never change.
Not exactly, they want Google to qualify as a telecom or cable provider when, in fact, they don't qualify as either since they only provide internet access and not phone or TV broadcasts,
Desktop are more ergonomic and tend to have larger screens and (sometimes) better keyboards. I spend 8 to 10 hours a day on the computer and I can tell you that it really matters if the screen is at the right height and the keyboard at the right angle.
A Neutrik PowerCON seems better thought out than that design. I've used it and it's easy to work with.
If I had to guess, I'd guess that the website uses the password to authenticate to a mainframe somewhere and is just a front end for some EDBIC based protocol so cracking the website wouldn't get access to the actual list.
Not that it excuses the short limit, but then I'm hard pressed to find something better considering our banks all got together and designed a PayPal competitor that
A. Is designed not to compete with their credit card processing system.
B. Is designed around clicking links in emails.
Not all of my passwords can be that long. My bank password (the one I care about the most) has a 5 char limit and and I hate random passwords. I came across a good method a few years ago for generating passwords that need to be short: Take a song and chose a line then take the first character of each word and you have an easy to remember but hard to guess password.
Ubuntu tries to allow you to do major upgrades in place, but after a year or two you have to reinstall to clear out the crud.
Say what? Unless something has really changed between Debian and Ubuntu there really shouldn't be much crud being built i`since it provides a remove feature for obsolete dependencies. I have been running Debian for over a decade and I only reinstall for server replacement or corrupted drives.