304 karma · joined October 10, 2007
meet.hn/city/us-Memphis
Job Specific Information: We are looking for a forward-thinking, innovative, and technology savvy professional who will help developed the next generation of FedEx solutions. The successful candidate will understand emerging technology, both software and hardware, and how to translate technology into tangible world-class solutions.
Experience in One or More of the Following is Considered a Plus:
- Innovation, startup, or R&D background with focus on development of products employing new technology
- Embedded programming experience
- High-level understanding of electronics design
- Experience with machine learning libraries (TensorFlow, Keras, PyTorch, scikit-learn)
- Experience working with large data sets and distributed computing tools (MapReduce, Hadoop, Cassandra, Spark)
- Android or iOS application development experience
- Web development: LAMP, Javascript/jQuery, DHTML, Apache Tomcat, Weblogic
- Java, Shell and high-level (Python, Perl, R, SQL) scripting language experience
Full write-up at https://careers.fedex.com/services/jobs/RC36471-4?lang=en-US
If you have specific questions reply or send me a note and I'll try to answer.
I know at least one sysadmin who used GIMPS as a burn-in program for new servers.....
I wonder how many people select tech videos based on length? Surely YouTube / Vimeo etc. has studied this? I wish there was a search option that let me filter content based on length.
https://phys.org/news/2016-03-ornl-low-cost-carbon-fiber.htm...
"Researchers at the Department of Energy's Oak Ridge National Laboratory have demonstrated a production method they estimate will reduce the cost of carbon fiber as much as 50 percent and the energy used in its production by more than 60 percent."
I also worked for a retailer that used SCO Xenix for Point of Sale and other applications. 386/16s and 386/20s with 16, 24 or 32 port serial boards running serial printers and dumb terminals. Fun times.
Alternating on blue / green as the 'live' side works, too.
That is, either they didn't properly assess you or they changed the situation into one where you were setup to fail.
http://hbr.org/2013/12/how-google-sold-its-engineers-on-mana...
Fun parts: There were a fixed number of variables. All variables were global. There were two control structures: if/then and goto
Imagine a Point-Of-Sale application written in such. A 100,000+ line Point-of-Sale program. Imagine the fun of chasing down re-use of a variable with no debugger.
EZ-C was supposed to be a simple language with built-in screen handling (via curses) and data file handling (with variant records and multiple indices). The theory was that you wrote code in EZ-C and debugged it, since the simpler syntax would reduce errors. EZ-C came with a program that would comple your source and link against EZ-C libraries. The best of all possible worlds - a nice interpreted language that compiled for blazing fast speed!
That was the theory. In practice, the compiler was broken, and so all programs ran via an interpreter called 'dparse'.
So (and I can hear you saying) I started to do what many of you would do: I started to write my own parser with the idea of building a compiler for the language. And that's when Mike, one of the older developers/admins/jack-of-all-trades/wise elders, stopped me. "Don't do that," he said, "because if you do that, we'll never stop writing in EZ-C."
And so I stopped immediately.
Background: the mother of all translations:
[ http://daringfireball.net/2007/02/macrovision_translation ]
Afterwords we remained periodically in touch, though I never saw him face-to-face again. I would usually write after hearing of his involvement in some new conference or having seen mention of him in some publication.
I am sorry to hear of his passing. He will be missed.