Not having had the advantage of a formal education (I have a GED and otherwise I am self taught) I've had to resort to, in some cases, drastic means of career as well as technical information acquisition. I have found the following to be consistently true.
1. You are rarely given additional responsibility (i.e. new projects, new technologies, "hard" stuff) at a job without first proving that you can do it. This usually involves doing things that "aren't my job" without getting paid for it for a certain amount of time and then being your own advocate after the fact. No one deserves anything on their own word. Find new things going on at work and put yourself square in the middle of it. Nothing interesting going on? Start analyzing the development process and environment and propose ways of making it better (and ofter to execute said plan).
2. Read. A lot. I highly recommend O'Reilly's Safari Bookshelf thingie. Some people don't like to read on line and prefer "real" books. I think that's cool, but you can't let that be a reason why you don't read. If you can't afford to buy all the new tech books you want to read, get a library card. Live in some strange place with no libraries? Find a way. You will if you want it.
3. Read non-technical articles and resources about the development process, software design and architecture, intergration methods. You know, "sciencey" type stuff. I find that I like certain authors more than others. For instance, Martin Fowler (http://www.martinfowler.com/) is the author of many excellent books and is known for his work in design patterns and architecture. If you read nothing else, read his work. Remember there's a much bigger world than writing guest book "scripts" 10,000 times (and thank insert-deity-here that's true).
4. Talk to other people. Anyone. Everyone. Project managers, developers, system administrators, architects, analysts, QA folk, telco employees, and anyone else that will give you the time of day. Learn what they do, how they do it, why they do it that way, and how it effects what you do and why. You'll have a much better understanding of distributed computing if you understand network and security principals and how they apply (and you might just not open up yet another SQL inject bug because of it).
5. Commit yourself to improving your craft by practicing it. Constantly. I find that being involved in open source development is 100% free peer reviewed experiance. Additionally, the open source work I've done in the past has won me a job or two. You never know when you might meet someone important to advancing your life.
6. Consider everyone you meet a student who may benefit from you, but more importantly, a teacher no matter how much smarter you think you are. Discuss, debate, learn, integrate new knowledge, repeat.
7. Find a mentor. Someone willing to take you under their wing (whether they know it or not) and soak information from them like a sponge. Don't know one? That's why I said *find* one. Very few people learn things themselves. Most people are taught by others, if by written or spoken word, code, IRC, or otherwise. I can't stress the mentor thing enough. Find two. Three is better. Find mentors that don't agree with one another and compare ideas. Learn from everyone.
This is what has worked for me. I dropped out of high school, got a GED ("good enough diploma"), and got really lucky in meeting the people I did. I do software architecture and design for a living in addition to mentoring and "grooming" developers. I learn more from them in a single day than I learned from any book (give or take).
Good luck. If you're trying to figure out why you aren't where you want to be or why you haven't attained what you want, you're already a step ahead of everyone else. You'll be fine.
They could be 450s... can't recall at the moment. No matter, the thing throws digital audio around like a rag doll in Digital Performer and ProTools. It serves its purpose well.
I have a G4 Dual 400 (mirrored drive door) and had a similar problem. After numerous games, and since it was still under warranty, I brought it in. Four visits to my local Apple store later, it works. They replaced the power supply, memory, ram, processor, and finally after I demanded it, the motherboard (or "main logic board" in Apple lingo. It was the motherboard.
Turns out there's a known Apple TechNote on the mirrored drive door boxes that produces a power on, but unexpected results type problem. Here's the technote (iirc) or at least one similar: http://docs.info.apple.com/article.html?artnum=950 38
I HIGHLY recommend making a list of technotes that directly refer to and explain the problem in detail. Do what you can yourself. Go to an Apple store (make it a road trip if there isn't one near you - I'm in NY, US so it wasn't a problem), walk up to the "Genius Bar" and make them work for their famed support reputation. I've owned macs since sometime prior to the Quadra and when it doubt, Apple *will* save you should you ask the right way. Be nice. Beg. Your warranty is an intangible and can be extended by the manufacturer if it is a known problem and you plead your case correctly.
This is usually related to a bit more than the power supply and is absolutely a known issue.
Good luck. Chin up... and beg if you're out of warranty.
Re:Let me get this straight...
on
Hotmail Hacked
·
· Score: 1
unfortunately, most username / password authentication systems are built *more* for the purposes of maintaining user information (like preferences and such) then for true security. you can look at many systems used by many sites and the username and password info is put in very obvious places (like hidden html input fields and in the query string of http requests) thus making security a secondary issue. is this right? no, of course not. is it the current state of how many people view user information, maybe. it is a problem? yes.
Slashdot Mirror
Not having had the advantage of a formal education (I have a GED and otherwise I am self taught) I've had to resort to, in some cases, drastic means of career as well as technical information acquisition. I have found the following to be consistently true.
1. You are rarely given additional responsibility (i.e. new projects, new technologies, "hard" stuff) at a job without first proving that you can do it. This usually involves doing things that "aren't my job" without getting paid for it for a certain amount of time and then being your own advocate after the fact. No one deserves anything on their own word. Find new things going on at work and put yourself square in the middle of it. Nothing interesting going on? Start analyzing the development process and environment and propose ways of making it better (and ofter to execute said plan).
2. Read. A lot. I highly recommend O'Reilly's Safari Bookshelf thingie. Some people don't like to read on line and prefer "real" books. I think that's cool, but you can't let that be a reason why you don't read. If you can't afford to buy all the new tech books you want to read, get a library card. Live in some strange place with no libraries? Find a way. You will if you want it.
3. Read non-technical articles and resources about the development process, software design and architecture, intergration methods. You know, "sciencey" type stuff. I find that I like certain authors more than others. For instance, Martin Fowler (http://www.martinfowler.com/) is the author of many excellent books and is known for his work in design patterns and architecture. If you read nothing else, read his work. Remember there's a much bigger world than writing guest book "scripts" 10,000 times (and thank insert-deity-here that's true).
4. Talk to other people. Anyone. Everyone. Project managers, developers, system administrators, architects, analysts, QA folk, telco employees, and anyone else that will give you the time of day. Learn what they do, how they do it, why they do it that way, and how it effects what you do and why. You'll have a much better understanding of distributed computing if you understand network and security principals and how they apply (and you might just not open up yet another SQL inject bug because of it).
5. Commit yourself to improving your craft by practicing it. Constantly. I find that being involved in open source development is 100% free peer reviewed experiance. Additionally, the open source work I've done in the past has won me a job or two. You never know when you might meet someone important to advancing your life.
6. Consider everyone you meet a student who may benefit from you, but more importantly, a teacher no matter how much smarter you think you are. Discuss, debate, learn, integrate new knowledge, repeat.
7. Find a mentor. Someone willing to take you under their wing (whether they know it or not) and soak information from them like a sponge. Don't know one? That's why I said *find* one. Very few people learn things themselves. Most people are taught by others, if by written or spoken word, code, IRC, or otherwise. I can't stress the mentor thing enough. Find two. Three is better. Find mentors that don't agree with one another and compare ideas. Learn from everyone.
This is what has worked for me. I dropped out of high school, got a GED ("good enough diploma"), and got really lucky in meeting the people I did. I do software architecture and design for a living in addition to mentoring and "grooming" developers. I learn more from them in a single day than I learned from any book (give or take).
Good luck. If you're trying to figure out why you aren't where you want to be or why you haven't attained what you want, you're already a step ahead of everyone else. You'll be fine.
Represent, my Gentoo brethren. ...and, for the record, my wife and I are not punk, nor goth despite the reports. ;)
Uhh... You're 100% correct. I think I was thinking of the Sun 250 dual proc box - an obvious difference.
The days are getting longer when you're feeling this loopy...
They could be 450s... can't recall at the moment. No matter, the thing throws digital audio around like a rag doll in Digital Performer and ProTools. It serves its purpose well.
I have a G4 Dual 400 (mirrored drive door) and had a similar problem. After numerous games, and since it was still under warranty, I brought it in. Four visits to my local Apple store later, it works. They replaced the power supply, memory, ram, processor, and finally after I demanded it, the motherboard (or "main logic board" in Apple lingo. It was the motherboard.
0 38
Turns out there's a known Apple TechNote on the mirrored drive door boxes that produces a power on, but unexpected results type problem. Here's the technote (iirc) or at least one similar: http://docs.info.apple.com/article.html?artnum=95
I HIGHLY recommend making a list of technotes that directly refer to and explain the problem in detail. Do what you can yourself. Go to an Apple store (make it a road trip if there isn't one near you - I'm in NY, US so it wasn't a problem), walk up to the "Genius Bar" and make them work for their famed support reputation. I've owned macs since sometime prior to the Quadra and when it doubt, Apple *will* save you should you ask the right way. Be nice. Beg. Your warranty is an intangible and can be extended by the manufacturer if it is a known problem and you plead your case correctly.
This is usually related to a bit more than the power supply and is absolutely a known issue.
Good luck. Chin up... and beg if you're out of warranty.
unfortunately, most username / password authentication systems are built *more* for the purposes of maintaining user information (like preferences and such) then for true security. you can look at many systems used by many sites and the username and password info is put in very obvious places (like hidden html input fields and in the query string of http requests) thus making security a secondary issue. is this right? no, of course not. is it the current state of how many people view user information, maybe. it is a problem? yes.