The connector is an M12 Industrial Ethernet Connector - as seen at http://www.designworldonline.c...
The story description should be updated so that more readers find out that they can connect to their Tesla's on-board computer via a easy to find cable.
Networking is your best way to reenter software engineering. Remember networking is about helping people and developing relationships. Based on your skill set you would be quite value-able to a web design company. Many web designers contract out programming to local programmers. Go to local networking events (chamber of commerce, bni,...). Introduce yourself as a software engineer and ask each person you meet if they know a good web designer then offer to do a short contract project at a competitive price. After completing that contract you now have recent experience.
When it comes to your programming experience, I recommend getting a company name (this is usually pretty cheap) and listing all your recent experience under your company. The person reading the resume won't know that the company is just you until they interview you.
On the resume topic, you might want to leave off your sales experience (and maybe some of your oldest software experience) so that your engineering experience doesn't get diluted and you might want to consider leaving off the dates so that employers don't notice your hiatus and don't guess your age.
P.S. I used most of these techniques to get back into software engineering after a 8 year hiatus as a Network Administrator.
Look for a technical support jobs with companies that you would like to do engineering work for. Only accept the job offers on the condition that they will provide you with Engineering work for you to do on your own time. If you do good work they will eventually promote you to an engineering position.
Avoid the words technical support, call center and first level at all costs. If you accidentally mention these words, try to remember the question that you struggled with then try to prepare a different answer for next time (many employers use the same interview questions...)
Familiarize your self with common interview styles (especially BEI) and interview questions. Then prepare as many answers/stories about your job that don't sound like you would end up dealing with them in a call center.
Look for jobs in a different city/state/country. Local employers will likely know that your current employer runs a call center but other employers probably won't.
Do extensive volunteer that is similar to the work you want to do. Make sure you get a title of Engineer, Analyst or whatever job you are looking for. Start listing the volunteer work above your call center work.
Remember: You don't need to tell the employer the job is a volunteer job unless they ask and volunteering for 5 hours a week as a database administrator for the local office of the American Cancer Society (or another well know charity) looks great on your resume.
Start a business. Its way easier than it sounds (I know because I've done it). Print some business cards and walk into every business in town, introduce yourself say either.
My name is "John Doe", I do computer networking and repairs and I'm wondering if there is anything I can help you with. [When they ask about your experience/training], tell them about your degree and the number of years of experience you have. Then tell them that you won't bill them unless they are happy with the work you do.
Once a few people get you to do work for them, mention a business/charity you do work for. For example, when I did a cold call to Top Drawer furniture (I said, I was just in doing some computer work for simply concrete and I'm wondering if their is anything I can help them with). When I do a cold call at a Doctor's office, I say "Hello, I'm John Doe, I do computer work for Al Hunter's family practice and I'm wondering if there is anything I can help you with"
Once you have a few happy clients, start printing quotes from them on the back of your business card. "John Doe is always professional polite and on time", "If you want it done right the first time, call John Doe".
Join as many clubs (toastmasters, chamber of commerce...) as possible. You will meet people who need small tech jobs done thereby growing your business.
Look for businesses that need both networking/repair work and programming/engineering work. Almost every business (accounting, mortgage brokering,...) has some programming work they need done. Even if its just Macros to automate repetitive tasks/CRM database tweeking...
If you like self employement stick with it. The pay is awesome (I slowly raised my rates from $30/h to $60/h) and you have a lot of flexibility to do the work you like.
Remember Self employment is easier than most people think (once you master your sales skills). I moved to a new city, two years ago and started with cold calls/networking and built a new business very quickly. My first 7 hour day of cold calls got me 6 new clients (4 of whom had me do work that day, 1 of whom had me do 2 full days for the next two days, 1 of who had me call them back to book an appointment, and 1 who called me 18months after I dropped my business card off. 5 of the 6 clients have called me for EVERY computer job since, most of the clients have referred me to other clients. All and all that first day of cold calls lead to at least $2500 in business.)
The purpose of chroot is to change the root directory. Chroot is particularly useful for recovery and diagnostics.
If you system that won't boot due to a boot sector problem Boot from a CD, mount your partitions, chroot to your root partition and run lilo/grub/... to rewrite your boot sector.
If you system that won't boot due to init script problems Boot from a CD, mount your partitions, chroot to your root partition and run run your full init process. If you run into problems, rerun your init scripts rather than rebooting.
Unfortunately, many people think chroot is a security tool so many people don't think it in non-security contexts.
For a few years, I have wanted an apple but needed a system for my consulting business that runs windows natively. I'm now delaying my next notebook purchase until Intel based Apples are available because I hope it will fit my requirements perfectly.
OSS has won some past PR battles. Enough well written emails to Phoenix Technologies along with some good media articles might be enough to make Phoenix technologies change their mind.
Could you tell us a little about the back end of your search eangine. It's extremely fast. What database software do you use? What optimisations have you implemented at the Operating System level (cluster sizes, Raw IO...)? What type of hardware do you use (Disk drives, Raid, CPU(s)...)? How do you handle load balancing/redundancy?
Debian 2.2 uses a 2.2.19 kernel (If you apply the security upgrades). I'm willing to bet the linux kernel PPC support has been improved since 2.2.x. I think the benchmarks would have been a little more fare if they had been run on a 2.4.x kernel.
I don't see the problem with the current Linux development model.
A development kernel series is created. (x.odd.x)
New features are added
The kernel is frozen (hopefully under a year after the development series is started)
The kernel is tested
Bugs are found and fixed
A stable kernel is released (x.even.x)
More people try it(not on production machines)
Bugs are found. They are fixed.
New releases happen frequently
Things start to stabalise
Releases drop to a bi monthly then quaterly rate.
A new development series is started
New features are put in the development series
Bug fixes/device drivers are still added to the stable kernel
Most linux users understand the release cycle and act accordingly. You don't need to run the latest kernel if you don't need the new features. If upgrades have costly downtime don't upgrade to the latest stable kernel until it hits x.x.5 or so.
If you want to advocate BSD. There is a much better way to do it. The BSD attitude to source is MUCH better than that of Linux. If I modify ls. I can cvs up to the latest ls and keep my changes. If I change my makefile (say to Optomize for my prossesor) I can easily upgrade my package without worrying about my Makefile. Another advantage to cvs is it makes it very easy to audit every change. You can have each commit emailed to you. This helps the development team audit the changes. If the BSDs ever catch up with Linux in terms of mainstream hardware feature support (Power Management...) I will switch because of the CVS support.
Slashdot Mirror
The connector is an M12 Industrial Ethernet Connector - as seen at http://www.designworldonline.c... The story description should be updated so that more readers find out that they can connect to their Tesla's on-board computer via a easy to find cable.
Networking is your best way to reenter software engineering. Remember networking is about helping people and developing relationships. Based on your skill set you would be quite value-able to a web design company. Many web designers contract out programming to local programmers. Go to local networking events (chamber of commerce, bni, ...). Introduce yourself as a software engineer and ask each person you meet if they know a good web designer then offer to do a short contract project at a competitive price. After completing that contract you now have recent experience.
When it comes to your programming experience, I recommend getting a company name (this is usually pretty cheap) and listing all your recent experience under your company. The person reading the resume won't know that the company is just you until they interview you.
On the resume topic, you might want to leave off your sales experience (and maybe some of your oldest software experience) so that your engineering experience doesn't get diluted and you might want to consider leaving off the dates so that employers don't notice your hiatus and don't guess your age.
P.S. I used most of these techniques to get back into software engineering after a 8 year hiatus as a Network Administrator.
Remember: You don't need to tell the employer the job is a volunteer job unless they ask and volunteering for 5 hours a week as a database administrator for the local office of the American Cancer Society (or another well know charity) looks great on your resume.
The purpose of chroot is to change the root directory. Chroot is particularly useful for recovery and diagnostics.
If you system that won't boot due to a boot sector problem Boot from a CD, mount your partitions, chroot to your root partition and run lilo/grub/... to rewrite your boot sector.
If you system that won't boot due to init script problems Boot from a CD, mount your partitions, chroot to your root partition and run run your full init process. If you run into problems, rerun your init scripts rather than rebooting.
Unfortunately, many people think chroot is a security tool so many people don't think it in non-security contexts.
For a few years, I have wanted an apple but needed a system for my consulting business that runs windows natively. I'm now delaying my next notebook purchase until Intel based Apples are available because I hope it will fit my requirements perfectly.
Chris
I recommend picking up another RIM 950 from ebay. You know it works for you and good condition 950s seem to cost less than $25.
OSS has won some past PR battles. Enough well written emails to Phoenix Technologies along with some good media articles might be enough to make Phoenix technologies change their mind.
Could you tell us a little about the back end of your search eangine. It's extremely fast. What database software do you use? What optimisations have you implemented at the Operating System level (cluster sizes, Raw IO...)? What type of hardware do you use (Disk drives, Raid, CPU(s)...)? How do you handle load balancing/redundancy?
I saw the keyboard mode google at google labs. Will there ever be a version with vi/emacs style key bindings?
Debian 2.2 uses a 2.2.19 kernel (If you apply the security upgrades). I'm willing to bet the linux kernel PPC support has been improved since 2.2.x. I think the benchmarks would have been a little more fare if they had been run on a 2.4.x kernel.
- A development kernel series is created. (x.odd.x)
- New features are added
- The kernel is frozen (hopefully under a year after the development series is started)
- The kernel is tested
- Bugs are found and fixed
- A stable kernel is released (x.even.x)
- More people try it(not on production machines)
- Bugs are found. They are fixed.
- New releases happen frequently
- Things start to stabalise
- Releases drop to a bi monthly then quaterly rate.
- A new development series is started
- New features are put in the development series
- Bug fixes/device drivers are still added to the stable kernel
Most linux users understand the release cycle and act accordingly. You don't need to run the latest kernel if you don't need the new features. If upgrades have costly downtime don't upgrade to the latest stable kernel until it hits x.x.5 or so. If you want to advocate BSD. There is a much better way to do it. The BSD attitude to source is MUCH better than that of Linux. If I modify ls. I can cvs up to the latest ls and keep my changes. If I change my makefile (say to Optomize for my prossesor) I can easily upgrade my package without worrying about my Makefile. Another advantage to cvs is it makes it very easy to audit every change. You can have each commit emailed to you. This helps the development team audit the changes. If the BSDs ever catch up with Linux in terms of mainstream hardware feature support (Power Management...) I will switch because of the CVS support.