Especially if he wants to get into a "niche" like Android development.
Spoken like someone who has no idea what the job market is like for Andorid developers. Try to fond a qualified one that doesn't already have a job.
That's an oxymoron. If you are qualified in anything on demand, of course you already have a job on that. Also, you are leaving out the context in which he presented that assertion (a willingness to accept an entry level, fresh-out-of-school salary). To be a top-notch Android developer (one who knows the whole stack and who also have the aesthetic sense required for developing professional-looking mobile apps), yes, it is hard to get that job. But entry-level jobs are aplenty, with companies willing to take anyone that can demonstrate general software engineering competency that allows them to land on their feet running (or to be moderately efficient in short time.)
I dare you. And if you aren't qualified, you aren't really an Android developer.
That is a self-full-filling prophecy that can mean anything (and ergo means nothing.) You can say "you are qualified to be an entry-level Android developer" or "you can be qualified to be an expert Android developer". But so say you are (or are not) qualified to be an Android developer (or developer of anything for that matter) is meaningless.
If a person has a certain depth of general software engineering knowledge, that person is qualified to be a developer for a particular stack, at a level of expertise or sophistication. Whether that person gets through the HR filter and get the job, that's another story that has nothing to do with the true nature of qualifications.
And it is mobile application development we are talking about here for Christ's sake. It's not like we are talking about DSP or hardware-software co-design type of jobs to be so smug about it.
Wait a few years... there used to be a slogan (before your time) - "Don't trust anyone over 30." Today, it's "Don't hire anyone over 30 to write code - we can get someone younger, cheaper, and willing to work the extra hours for free, and they will have even worse spelling and math skills than we do. Hiring one of those old farts will just make us look bad by comparison."
The original poster might as well slit their wrists now if they really believe that they can go back to coding after so many years out of it. The first tthree questions would be
Q1 "Why did you get out of it in the first place?
Q2 "So why do you want to get back in now?"
Q3: "Why should we even look at you when you've got no recent experience?"
BTW - the job market is NOT "strong for programmers" unless your definition of "strong" == "willing to work even longer hours for a lot less than the person we used to have before we burned them out." Especially programmers > 50.
I really don't get this posts. I work with lots of software engineers in their 50's who are, quite literally, the hot shit pulling 6-figures (in particular in the enterprise web services area.) And I've known people from other fields (electrical and physics for instance) who decided to jump into software and got hired w/o problems (all over 50.). Yes, it is the internet when people can make shit up. I can only say that I'm not, and that what I'm saying is both real, and common (even as incidents of ageism have increased in the last decade or so).
Also, the willingness to work long hours has always been a given for anyone doing any type of engineering. It's not a recent phenomenon and young and old people before and now have been doing it always. It is funny and ridiculous when people say this to 50-year old professionals trying to get back into coding. What the hell do you people think these folks did in their coding years? 9-5'ers?
Forget it. The idiots in H.R. won't even consider you.
Stick with what you have and retire, then start your own business.
Bad advice. A better advice would have gone as follows:
Be mindful of the H.R. idiots that might not even consider you. Look for small-scale operations in which you get a better chance to be filtered by the software team directly as opposed to being passed by the H.R. filter. Look for moonlight work, part-time coding opportunities done via telecommuting, LAMP development and the like.
Yes, it is though, but not impossible. In particular, if this is what the OP really wants, he should go for it and assess how hard it will be vs how badly he wants it. As Michael Jordan once said : "I can accept failure, everyone fails at something. But I can't accept not trying."
Check at your local bookstore? Somehow, there's always a large selection of very specific mags there that manage to stay in print.
And the majority are about Photoshop and gaming. Those might scratch the 3D Printer itch as the OP puts it, but I hardly see how these are relevant to engineering, coding or sys admin (which is what the OP is asking.)
It's easy to throw together a BASIC interpreter. However, in this day and age, why would you want one?
Why not? Many DSP algorithms were once implemented in BASIC, and for a good reason. Structured, modern variants of BASIC (which resemble nothing of the old GW-BASIC or PickBasic), are very useful and capable for application-level development. I do have my preferences over BASIC (Ada, C or Python come to mind for different tasks), but I find people's aversion to it to be simply misinformed, fan-oriented knee-jerking.
You do realise that despite his rude demeanour - he was right...
The original poster was asking to pay less taxes - the subsequent poster called him selfish for it - you then asked how those two were connected, and the rude fucker called you out for not reading it correctly.
I don't think me or any other taxpayer is going to be hurt too badly if you take less money away.
See - he's suggesting that no-one would be seriously hurt if less money was 'taken away' from them. So implying that he was selfish was at least a logically sound suggestion.
Ah, I see. I miss-read that part. Somehow I read it as "taking more" instead of "taking less" which is what the poster actually wrote.
If you knew how to read you'd realize why he wrote what he wrote you dumbfuck.
Because hurling insults will make your point and show how you care about the world more than what we do. Besides, this is not a matter of how to read (if it were, you would display more articulate counter-arguments above 3rd grade South Park level antics.) It is a matter of interpretation, one that you made on your own and which does not follow from what was written.
But hey, don't let me get in the way of your emoticon antics. I'm not going to be one to expect you to raise your argumentative levels beyond the level of juvenile discourse. Hurl insults away if they help you make your point.
Ummm... lowering taxes is "bad for the United States". How exactly do you backup that comment? I don't think me or any other taxpayer is going to be hurt too badly if you take less money away.
If your own selfish interests are more important than those of your country and your countrymen
How did you get to that sentence from the post you are replying to? How is it that "not minding getting taxed more" qualifies as "being selfish"? I would imagine that being selfish implies wanting to pay less taxes, nor more. Nice strawman btw.
Wait till Emperor Palpatine finds out. Grand Moff Tarkin is gonna blow them the fuck off the spatial plane for orbiting too close to their security perimeter.
I'm about to switch from a position where I did hands on development to one where I will be building and managing technical team. I will be responsible for designing and implementing the company's overall tech strategy. I am excited about this move but also nervous. It will require a different focus than I had up to this point, different skills, and different orientation. What should I be learning,
I think you should have asked this question a bit earlier me thinks:)
Having said that, there are things that you need to learn:
1. The basics of project management if you don't understand them already. I'd say buy Steve McConnell's "Software Project Survival Guide".
Also, be aware that you will lose some of your technical chops. You won't be in the trenches, but that doesn't mean you need to devolve into a pointy hairy boss. The closer you are to the developers, the more often you will need to get your hands dirty once in a while to understand their work and needs (and to keep your chops) - you will need to do that while never forgetting when and how to delegate.
I'd like to hear them explain how, for chips meant to be used in the USA, Samsung decided it would be more practical to build a factory here. But every American company decided it would be cheaper to use factories elsewhere and have them shipped here. It kind of seems like there's nothing impractical about having a factory here. They just want to make sure no American company builds anything.
Offshoring/outsourcing overseas has always been about shifting costs overseas in the name of efficiency, quality or even profit. It has always been about reducing costs to increase the pockets of those who sell the idea of outsourcing, everything else be damned. I know it sounds like a slogan, but that's what makes it terrifying because it is true. That's the type of mercenary mentality that has been cultivated in our business ruling classes for the last 2 decades.
You will not see that in the Toyotas, Mercedes-Benz and Samsungs of the world where the choice to build a factory here or there are actually strategical and tactical, with actual business considerations( quality, cost, ship-to-market, etc) driving these decisions.
The fact that the post I'm replying to (a blatant example of argumentum ad ignorantiam) has been modded up so much is a sad indictment in/. collective intelligence.
"n that case Ireland wasn't a true country for 800 of the last 900 years"
It wasn't. It takes more to make a country than a specific local culture otherwise every tinpot region in europe would be a seperate "country". Is Brittany a seperate country to france? No.
Is Bavaria a seperate country to Germany? No.
"yet we have one of the most unique and vibrant cultures in the world"
If you say so. Personally I can think of 101 other more interesting places.
You were doing great until you wrote that sentence. Now you are just being subjective. A culture's uniqueness and liveliness are not function of a single individual's predilections.
Because microbiology and astronomy totally helped my network admin degree.Because microbiology and astronomy totally helped my network admin degree.
If you wanted a vocational degree, you should have gone to a vo-tech school
Easy there. I can see intro courses in bio or chemistry as part of science requisites for a AS or BS degree conductive to work as a network admin. Requirements specific to microbiology and astronomy, that's another story. If that's what the poster is claiming (what the context hints), then his remark is actually valid and doesn't necessarily mean he wanted a vocational degree (which, ultimately, there is nothing wrong with that, and the country would be best served - using a German or Japanese model as example - if we put more focus on vocational training as opposed to full-blown 4-year college education.)
A four-year degree at an in-state school should not cost more than $15-20,000 including fees. If you went $60k into debt for school, consider that a $40-45k math lesson. Teach your kids that one at home so they don't have to pay for it again.
Bingo. My sister went to a private university (local) all the way to grad school for a STEM degree, and she piled no more than $45K (again, in a private school.) I went to grad school in a in-state university, and my total debt was about $25K. My other sisters went also to in-state schools (biomed, fine-arts, PT) and none racked that much of debt either. The only person I know that justifiably had like $60K in debt was this guy who went to grad school in PT with a lot of specialized training. Medical and law students would be the other camp in which I could see a justification for such an amount of student loan debt.
OTH, people getting into $60K for a degree in History or Social Science is just absolutely retarded. I could understand that debt in those degrees if the student 1) goes to a private Ivy League school, and 2) go all the way for a Ph.D. But for a B.A in those fields?
I mean seriously, I see these shows and interviews with people being burdened with $60K, $80K even $100K and not having a job or a job that pays well to get rid of that debt, and when they get asked what degree they have, we don't hear STEM or law or medicine, we don't hear post-grad education. We hear 4-year degrees in History or Social Sciences.
WTF? WTF? WTF??????
Yeah, universities keep racking up the cost of education, but let's not delude ourselves into blaming these institutions when people rack up student loans on 4-year degrees with no market value. There is a difference between a freshman entering school and not knowing what to study, and that same person cruising around for the next 4 years without ever thinking "shit, how is my education going to get me a job with which to repay by debt?" Living life in cruise control is a stupid and costly way of doing things.
Hmm , not really. A true country has control of its own foreign policy and defense. The US States don't. A federal system is not the same ad a coalition which is what the EU is.
Exactly. Moreover, a true country has the power to regulate commerce with outer countries (even in a retaliatory manner). In the US, states do not have that power as inter-state is a federal power, and anything that interferes with inter-state commerce (or challenges the federal power therein) will have a federal hammer raining on it real fast.
The individual states are no different countries by any stretch of the imagination. The republics within the Russian Federation have a greater deal of autonomy - most have powers to establish local laws that can, to some degree, contravene federal laws, and some republics (like the Tuvan Republic) have the right, within the constitution of the Russian Federation, to secede.
But none of these are considered "countries", so it is kinda funny for some people to say that the individual states within the US are different countries when they exist in a more constrained federal context.
Wouldn't this depend a lot on the type of app, and also on the type of bugs you want information about?
If it's a C++ app, then sure, having a built-in crash reporting mechanism shouldn't be that hard to build in. But what if it's a web app?
Client and server error bundles.
For starters, a web app, even a RIA, is just a web UI and a back end. Moreover, most relevant exceptions in a web app, even a RIA one, occur on the back end. And on the back end, you can do almost anything. A good approach for web app exception handling is to have exception stack traces properly time-stamped and logged in a log file. Additionally, they must be bundled with "context" information such as - user id, url visited, url arguments if any, http session state if any, cookies if any, http method (post/get/etc), hostname and when possible OS/container state (connection pool stats, thread pool stats). All that bundled info then gets send to a log file as well (and possibly via syslog or something else sent as a nonblocking message to another machine, or an error tracking database table.)
On the front end, have the web UI create dynamically a client-side error bundle (a simple json or xml structure containing client information such as browser version, OS version, user id, cookies) whenever the client detects an error, be it client or back-end originated. Then have the web UI
on the web interface, when the error (or an error) occurs, have the web interface (without taking the user away from the page or transaction last visited) create a dynamic pop-up form for the user to log an error report. The web interface should also pull as much information as possible on the client (browser, OS, user id, cookies, etc) and preemptively post that as a client-side error bundle against an error-reporting URL in the application.
In addition to that, the web UI should provide a non-intrusive form (perhaps a dynamic pop-up form/frame thingie) that allows a user to report an error (and which would also include a timestamp, user id and visited URL). Most sites do not do that, which I think is an operational error. The relative time stamps, user id and visited url would provide a mapping from this report to the client-side error bundle to the server-side error bundle.
Implementing this can get hairy very quickly, specially for developers who cannot control over-engineering spams due to acute featuritis and "2nd System Effect". But at the very least, a web app should capture server-side errors coupled with (at least) user id, timestamp and visited URL (and sometimes http session state and cookies.)
Anything less is the operational equivalent of peeling potatoes while blind-folded (ouch.)
It is worth nothing that this is a operational/non-functional architectural feature, and that it should be implemented in the design early on. Trying to shoe-horn it into an application that did not have such considerations in place will be a PITA. Things like this should never be an after-though. They need to be considered early on in any application.
Or some kind of low-level or embedded software?
That's actually (conceptually) easier since a low-level or embedded system does not get most (or all) of its inputs from a human interface. Its inputs and outputs tend to be discrete, and such systems are (at least conceptually) state machines with clear transitions and states. When an error is encountered, you simply write a time stamped error descriptor that is efficient and acceptable in terms of the available resources to an error reporting port, which could be a led display, an internal buffer, or if the resources are available, to a storage device or to a port connected to a cable (ethernet, serial, whatever.) The error descriptor should indicate the state the device was in at the time of the error.
Your comparison is bad because in bars/clubs there are no other way to judge people but on looks and is a competitive environment to begin with and that makes it a poor place to look for a potential date although I can see your real problem seems to be the implied "if I don't take what I can get I will get nothing".
Sure there is. Talk to them. Treat the bar like your own personal, undeclared speed-dating session and talk to the ladies in the bar. Look for signs that what they're saying is too good to be true, and filter those out if you're actually looking for a long-term relationship. Pay attention to the kind of people that they're hanging out with too.
Or, just skip the bar scene and start doing activities that women also like to do. That doesn't mean doing effeminate activities, but it does mean, generally, getting off of the computer. In my case I met my wife when I learned to dance. BTW, dancing is a great way to meet women for non-long-term relationships too. I mean, you get to put your hands all over a woman for three and a half minutes and she thanks you for it when you're done. It can often lead to more intimate contact.
^^^ This. For years I got caught up in the "bar/club scene as the only dating ground on the planet", with predictable results. When I started socializing with women on different contexts (school, working out, and eventually dancing, as in trained dancing in a dancing school as opposed to humping with 50 cent in the background), it was a complete different thing, like night and day. I also met my wife in a dance school. A bar/club is good to play the game and have fun fling style... but to date or looking for a girlfriend there, big mistake, big mistake.
The precedent from the Nuremberg trials is that if you participate in the military aggression against Afghanistan and Iraq, this makes you a war criminal.
No it doesn't. You become a war criminal by committing war crimes. The mere participation as a combatant in an military confrontation - let alone as an auxiliary - does not constitute a war crime, with the Nuremberg trials that you so ignorantly quote as precedent of this fact. There is a very clear definition of what a war crime and a war criminal are under international law. Anything else, including your interpretation, is rhetorical bullshit.
The money isn't worth it if you wind up kidnapped and looking at a video camera while they cut your head off.
Look at working in Europe or if you want to try the language China, even better Australia routinely hires for IT and they speak English (sort of).
Is the money worth it if you're killed in a car accident during rushhour traffic on your way to work in *insert city here* USA?
Life is a risk, death is always a risk, and the statistics about risk are often pretty far off what people estimate in their gut.
Comparing the risk of getting killed in a car accident with the risk of getting (most likely violently) killed in a war zone (in particular in a war zone where foreigners get kidnapped and forced to watch a video camera while their heads get brutishly sawed off with a butcher knife), that's pretty retarded to say the least.
I am actually pretty interested in this. I have been looking in Southeast Asia but I am having a hard time finding job postings... any recommendations? I only speak English and Spanish (which I assume is useless there), is that a problem in finding a job there?
English would do you well in Singapore and the Philippines. Also in Tokyo or Seoul. Spanish would also come in handy in the Philippines as a lot of the Tagalog vocabulary is based/borrowed from Castillian. Spanish and English (and/or Portuguese and English) would also come in handy for many Japanese companies that do business in Latin America. My wife (she is Japanese) used to work for a Japanese company that did a ton of business in Latin America (and a lot of its business was conducted in said languages.)
From an IT perspective, English would help you a lot. And if you want to explore business opportunities, Spanish might prove an invaluable asset depending where you go.
Slashdot Mirror
Especially if he wants to get into a "niche" like Android development.
Spoken like someone who has no idea what the job market is like for Andorid developers. Try to fond a qualified one that doesn't already have a job.
That's an oxymoron. If you are qualified in anything on demand, of course you already have a job on that. Also, you are leaving out the context in which he presented that assertion (a willingness to accept an entry level, fresh-out-of-school salary). To be a top-notch Android developer (one who knows the whole stack and who also have the aesthetic sense required for developing professional-looking mobile apps), yes, it is hard to get that job. But entry-level jobs are aplenty, with companies willing to take anyone that can demonstrate general software engineering competency that allows them to land on their feet running (or to be moderately efficient in short time.)
I dare you. And if you aren't qualified, you aren't really an Android developer.
That is a self-full-filling prophecy that can mean anything (and ergo means nothing.) You can say "you are qualified to be an entry-level Android developer" or "you can be qualified to be an expert Android developer". But so say you are (or are not) qualified to be an Android developer (or developer of anything for that matter) is meaningless.
If a person has a certain depth of general software engineering knowledge, that person is qualified to be a developer for a particular stack, at a level of expertise or sophistication. Whether that person gets through the HR filter and get the job, that's another story that has nothing to do with the true nature of qualifications.
And it is mobile application development we are talking about here for Christ's sake. It's not like we are talking about DSP or hardware-software co-design type of jobs to be so smug about it.
The original poster might as well slit their wrists now if they really believe that they can go back to coding after so many years out of it. The first tthree questions would be
Q1 "Why did you get out of it in the first place? Q2 "So why do you want to get back in now?" Q3: "Why should we even look at you when you've got no recent experience?"
BTW - the job market is NOT "strong for programmers" unless your definition of "strong" == "willing to work even longer hours for a lot less than the person we used to have before we burned them out." Especially programmers > 50.
I really don't get this posts. I work with lots of software engineers in their 50's who are, quite literally, the hot shit pulling 6-figures (in particular in the enterprise web services area.) And I've known people from other fields (electrical and physics for instance) who decided to jump into software and got hired w/o problems (all over 50.). Yes, it is the internet when people can make shit up. I can only say that I'm not, and that what I'm saying is both real, and common (even as incidents of ageism have increased in the last decade or so).
Also, the willingness to work long hours has always been a given for anyone doing any type of engineering. It's not a recent phenomenon and young and old people before and now have been doing it always. It is funny and ridiculous when people say this to 50-year old professionals trying to get back into coding. What the hell do you people think these folks did in their coding years? 9-5'ers?
Forget it. The idiots in H.R. won't even consider you.
Stick with what you have and retire, then start your own business.
Bad advice. A better advice would have gone as follows:
Be mindful of the H.R. idiots that might not even consider you. Look for small-scale operations in which you get a better chance to be filtered by the software team directly as opposed to being passed by the H.R. filter. Look for moonlight work, part-time coding opportunities done via telecommuting, LAMP development and the like.
Yes, it is though, but not impossible. In particular, if this is what the OP really wants, he should go for it and assess how hard it will be vs how badly he wants it. As Michael Jordan once said : "I can accept failure, everyone fails at something. But I can't accept not trying."
Discover magazine. Sky and Telescope. Wired. Architectural Digest. Popular Mechanics and PopSci. Some that I get, on and off.
Wired? You serious?
Check at your local bookstore? Somehow, there's always a large selection of very specific mags there that manage to stay in print.
And the majority are about Photoshop and gaming. Those might scratch the 3D Printer itch as the OP puts it, but I hardly see how these are relevant to engineering, coding or sys admin (which is what the OP is asking.)
It's easy to throw together a BASIC interpreter. However, in this day and age, why would you want one?
Why not? Many DSP algorithms were once implemented in BASIC, and for a good reason. Structured, modern variants of BASIC (which resemble nothing of the old GW-BASIC or PickBasic), are very useful and capable for application-level development. I do have my preferences over BASIC (Ada, C or Python come to mind for different tasks), but I find people's aversion to it to be simply misinformed, fan-oriented knee-jerking.
You do realise that despite his rude demeanour - he was right...
The original poster was asking to pay less taxes - the subsequent poster called him selfish for it - you then asked how those two were connected, and the rude fucker called you out for not reading it correctly.
I don't think me or any other taxpayer is going to be hurt too badly if you take less money away.
See - he's suggesting that no-one would be seriously hurt if less money was 'taken away' from them. So implying that he was selfish was at least a logically sound suggestion.
Ah, I see. I miss-read that part. Somehow I read it as "taking more" instead of "taking less" which is what the poster actually wrote.
If you knew how to read you'd realize why he wrote what he wrote you dumbfuck.
Because hurling insults will make your point and show how you care about the world more than what we do. Besides, this is not a matter of how to read (if it were, you would display more articulate counter-arguments above 3rd grade South Park level antics.) It is a matter of interpretation, one that you made on your own and which does not follow from what was written.
But hey, don't let me get in the way of your emoticon antics. I'm not going to be one to expect you to raise your argumentative levels beyond the level of juvenile discourse. Hurl insults away if they help you make your point.
Ummm... lowering taxes is "bad for the United States". How exactly do you backup that comment? I don't think me or any other taxpayer is going to be hurt too badly if you take less money away.
If your own selfish interests are more important than those of your country and your countrymen
How did you get to that sentence from the post you are replying to? How is it that "not minding getting taxed more" qualifies as "being selfish"? I would imagine that being selfish implies wanting to pay less taxes, nor more. Nice strawman btw.
Exoplanets Spotted Orbiting Dead Star
Wait till Emperor Palpatine finds out. Grand Moff Tarkin is gonna blow them the fuck off the spatial plane for orbiting too close to their security perimeter.
I'm about to switch from a position where I did hands on development to one where I will be building and managing technical team. I will be responsible for designing and implementing the company's overall tech strategy. I am excited about this move but also nervous. It will require a different focus than I had up to this point, different skills, and different orientation. What should I be learning,
I think you should have asked this question a bit earlier me thinks :)
Having said that, there are things that you need to learn:
1. The basics of project management if you don't understand them already. I'd say buy Steve McConnell's "Software Project Survival Guide".
2. Software estimation if you don't have a good grasp of that already. You can start by reading Spolsky's "evidence based scheduling" http://www.joelonsoftware.com/items/2007/10/26.html
3. Learn to delegate.
Also, be aware that you will lose some of your technical chops. You won't be in the trenches, but that doesn't mean you need to devolve into a pointy hairy boss. The closer you are to the developers, the more often you will need to get your hands dirty once in a while to understand their work and needs (and to keep your chops) - you will need to do that while never forgetting when and how to delegate.
I'd like to hear them explain how, for chips meant to be used in the USA, Samsung decided it would be more practical to build a factory here. But every American company decided it would be cheaper to use factories elsewhere and have them shipped here. It kind of seems like there's nothing impractical about having a factory here. They just want to make sure no American company builds anything.
Offshoring/outsourcing overseas has always been about shifting costs overseas in the name of efficiency, quality or even profit. It has always been about reducing costs to increase the pockets of those who sell the idea of outsourcing, everything else be damned. I know it sounds like a slogan, but that's what makes it terrifying because it is true. That's the type of mercenary mentality that has been cultivated in our business ruling classes for the last 2 decades.
You will not see that in the Toyotas, Mercedes-Benz and Samsungs of the world where the choice to build a factory here or there are actually strategical and tactical, with actual business considerations( quality, cost, ship-to-market, etc) driving these decisions.
Yet Samsung's own lawyers couldn't tell them apart. In real life.
And that's because the lawyers were incompetent, not because the products were reasonably indistinguishable from one another.
The fact that the post I'm replying to (a blatant example of argumentum ad ignorantiam) has been modded up so much is a sad indictment in /. collective intelligence.
And your evidence that they ever used it is where? Oh right, you don't have any.
And even if they didn't use CarrierIQ, what's to say that they don't have a homegrown version of software that does the exact same thing?
http://en.wikipedia.org/wiki/Argument_from_ignorance
"n that case Ireland wasn't a true country for 800 of the last 900 years"
It wasn't. It takes more to make a country than a specific local culture otherwise every tinpot region in europe would be a seperate "country". Is Brittany a seperate country to france? No. Is Bavaria a seperate country to Germany? No.
"yet we have one of the most unique and vibrant cultures in the world"
If you say so. Personally I can think of 101 other more interesting places.
You were doing great until you wrote that sentence. Now you are just being subjective. A culture's uniqueness and liveliness are not function of a single individual's predilections.
Because microbiology and astronomy totally helped my network admin degree.Because microbiology and astronomy totally helped my network admin degree.
If you wanted a vocational degree, you should have gone to a vo-tech school
Easy there. I can see intro courses in bio or chemistry as part of science requisites for a AS or BS degree conductive to work as a network admin. Requirements specific to microbiology and astronomy, that's another story. If that's what the poster is claiming (what the context hints), then his remark is actually valid and doesn't necessarily mean he wanted a vocational degree (which, ultimately, there is nothing wrong with that, and the country would be best served - using a German or Japanese model as example - if we put more focus on vocational training as opposed to full-blown 4-year college education.)
A four-year degree at an in-state school should not cost more than $15-20,000 including fees. If you went $60k into debt for school, consider that a $40-45k math lesson. Teach your kids that one at home so they don't have to pay for it again.
Bingo. My sister went to a private university (local) all the way to grad school for a STEM degree, and she piled no more than $45K (again, in a private school.) I went to grad school in a in-state university, and my total debt was about $25K. My other sisters went also to in-state schools (biomed, fine-arts, PT) and none racked that much of debt either. The only person I know that justifiably had like $60K in debt was this guy who went to grad school in PT with a lot of specialized training. Medical and law students would be the other camp in which I could see a justification for such an amount of student loan debt.
OTH, people getting into $60K for a degree in History or Social Science is just absolutely retarded. I could understand that debt in those degrees if the student 1) goes to a private Ivy League school, and 2) go all the way for a Ph.D. But for a B.A in those fields?
I mean seriously, I see these shows and interviews with people being burdened with $60K, $80K even $100K and not having a job or a job that pays well to get rid of that debt, and when they get asked what degree they have, we don't hear STEM or law or medicine, we don't hear post-grad education. We hear 4-year degrees in History or Social Sciences. WTF? WTF? WTF??????
Yeah, universities keep racking up the cost of education, but let's not delude ourselves into blaming these institutions when people rack up student loans on 4-year degrees with no market value. There is a difference between a freshman entering school and not knowing what to study, and that same person cruising around for the next 4 years without ever thinking "shit, how is my education going to get me a job with which to repay by debt?" Living life in cruise control is a stupid and costly way of doing things.
"but on paper we are still different countries"
Hmm , not really. A true country has control of its own foreign policy and defense. The US States don't. A federal system is not the same ad a coalition which is what the EU is.
Exactly. Moreover, a true country has the power to regulate commerce with outer countries (even in a retaliatory manner). In the US, states do not have that power as inter-state is a federal power, and anything that interferes with inter-state commerce (or challenges the federal power therein) will have a federal hammer raining on it real fast.
The individual states are no different countries by any stretch of the imagination. The republics within the Russian Federation have a greater deal of autonomy - most have powers to establish local laws that can, to some degree, contravene federal laws, and some republics (like the Tuvan Republic) have the right, within the constitution of the Russian Federation, to secede.
But none of these are considered "countries", so it is kinda funny for some people to say that the individual states within the US are different countries when they exist in a more constrained federal context.
Wouldn't this depend a lot on the type of app, and also on the type of bugs you want information about?
If it's a C++ app, then sure, having a built-in crash reporting mechanism shouldn't be that hard to build in. But what if it's a web app?
Client and server error bundles.
For starters, a web app, even a RIA, is just a web UI and a back end. Moreover, most relevant exceptions in a web app, even a RIA one, occur on the back end. And on the back end, you can do almost anything. A good approach for web app exception handling is to have exception stack traces properly time-stamped and logged in a log file. Additionally, they must be bundled with "context" information such as - user id, url visited, url arguments if any, http session state if any, cookies if any, http method (post/get/etc), hostname and when possible OS/container state (connection pool stats, thread pool stats). All that bundled info then gets send to a log file as well (and possibly via syslog or something else sent as a nonblocking message to another machine, or an error tracking database table.)
On the front end, have the web UI create dynamically a client-side error bundle (a simple json or xml structure containing client information such as browser version, OS version, user id, cookies) whenever the client detects an error, be it client or back-end originated. Then have the web UI on the web interface, when the error (or an error) occurs, have the web interface (without taking the user away from the page or transaction last visited) create a dynamic pop-up form for the user to log an error report. The web interface should also pull as much information as possible on the client (browser, OS, user id, cookies, etc) and preemptively post that as a client-side error bundle against an error-reporting URL in the application.
In addition to that, the web UI should provide a non-intrusive form (perhaps a dynamic pop-up form/frame thingie) that allows a user to report an error (and which would also include a timestamp, user id and visited URL). Most sites do not do that, which I think is an operational error. The relative time stamps, user id and visited url would provide a mapping from this report to the client-side error bundle to the server-side error bundle.
Implementing this can get hairy very quickly, specially for developers who cannot control over-engineering spams due to acute featuritis and "2nd System Effect". But at the very least, a web app should capture server-side errors coupled with (at least) user id, timestamp and visited URL (and sometimes http session state and cookies.)
Anything less is the operational equivalent of peeling potatoes while blind-folded (ouch.)
It is worth nothing that this is a operational/non-functional architectural feature, and that it should be implemented in the design early on. Trying to shoe-horn it into an application that did not have such considerations in place will be a PITA. Things like this should never be an after-though. They need to be considered early on in any application.
Or some kind of low-level or embedded software?
That's actually (conceptually) easier since a low-level or embedded system does not get most (or all) of its inputs from a human interface. Its inputs and outputs tend to be discrete, and such systems are (at least conceptually) state machines with clear transitions and states. When an error is encountered, you simply write a time stamped error descriptor that is efficient and acceptable in terms of the available resources to an error reporting port, which could be a led display, an internal buffer, or if the resources are available, to a storage device or to a port connected to a cable (ethernet, serial, whatever.) The error descriptor should indicate the state the device was in at the time of the error.
Judging by the question, it's
Sure there is. Talk to them. Treat the bar like your own personal, undeclared speed-dating session and talk to the ladies in the bar. Look for signs that what they're saying is too good to be true, and filter those out if you're actually looking for a long-term relationship. Pay attention to the kind of people that they're hanging out with too.
Or, just skip the bar scene and start doing activities that women also like to do. That doesn't mean doing effeminate activities, but it does mean, generally, getting off of the computer. In my case I met my wife when I learned to dance. BTW, dancing is a great way to meet women for non-long-term relationships too. I mean, you get to put your hands all over a woman for three and a half minutes and she thanks you for it when you're done. It can often lead to more intimate contact.
^^^ This. For years I got caught up in the "bar/club scene as the only dating ground on the planet", with predictable results. When I started socializing with women on different contexts (school, working out, and eventually dancing, as in trained dancing in a dancing school as opposed to humping with 50 cent in the background), it was a complete different thing, like night and day. I also met my wife in a dance school. A bar/club is good to play the game and have fun fling style... but to date or looking for a girlfriend there, big mistake, big mistake.
The precedent from the Nuremberg trials is that if you participate in the military aggression against Afghanistan and Iraq, this makes you a war criminal.
No it doesn't. You become a war criminal by committing war crimes. The mere participation as a combatant in an military confrontation - let alone as an auxiliary - does not constitute a war crime, with the Nuremberg trials that you so ignorantly quote as precedent of this fact. There is a very clear definition of what a war crime and a war criminal are under international law. Anything else, including your interpretation, is rhetorical bullshit.
The money isn't worth it if you wind up kidnapped and looking at a video camera while they cut your head off.
Look at working in Europe or if you want to try the language China, even better Australia routinely hires for IT and they speak English (sort of).
Is the money worth it if you're killed in a car accident during rushhour traffic on your way to work in *insert city here* USA?
Life is a risk, death is always a risk, and the statistics about risk are often pretty far off what people estimate in their gut.
Comparing the risk of getting killed in a car accident with the risk of getting (most likely violently) killed in a war zone (in particular in a war zone where foreigners get kidnapped and forced to watch a video camera while their heads get brutishly sawed off with a butcher knife), that's pretty retarded to say the least.
local women from aphganistan, or Iraq ;-) ????
Good way to get beheaded. Seriously.
I am actually pretty interested in this. I have been looking in Southeast Asia but I am having a hard time finding job postings... any recommendations? I only speak English and Spanish (which I assume is useless there), is that a problem in finding a job there?
English would do you well in Singapore and the Philippines. Also in Tokyo or Seoul. Spanish would also come in handy in the Philippines as a lot of the Tagalog vocabulary is based/borrowed from Castillian. Spanish and English (and/or Portuguese and English) would also come in handy for many Japanese companies that do business in Latin America. My wife (she is Japanese) used to work for a Japanese company that did a ton of business in Latin America (and a lot of its business was conducted in said languages.)
From an IT perspective, English would help you a lot. And if you want to explore business opportunities, Spanish might prove an invaluable asset depending where you go.