I couldn't do my job without ack. We have a code base with millions of lines of C/C++ and tons of PHP. I use ack every day to find code and files. I've been looking forward to 2.0 for a long time. Will try to help melt his server right now :)
I worked on the 787 and a derivative of the 747. They use protocols defined by ARINC (google it) that are only used in the airplane industry. Stuff like telnet need not apply.
I used to work on interfaces to all the computers on the latest 747 and the 787 and there is no wireless way to talk to any of the computers or sensors that have any input to controlling the airplane.
I am not making this up.
On the 747-400 I was on a group whose computer got input from all the 70+ computers on the airplane. It was all wired.
On the 787 I worked on a database during the development of the airplane that tracked all the information that flowed between computers. Nothing came to any computer that controlled the airplane that was not by wire or fiber optics.
I also dealt with ACARS. It is a read-only system on the airplane. It gets information from other computers and transmits it via satellite to the ground.
Nothing special. He put his resume on job boards and started getting calls from recruiters. He looked at jobs offered found some he liked, applied to some, and one of those hired him.
I'm not looking right now but I check craigslist from time to time and there are more iOS jobs now than 12-18 months ago when I was looking.
It's a problem with web apps vs apps in general. If I have an app on my laptop/tablet/phone and a new version comes out I don't have to download it if I don't like what I read about in the reviews. But with a web app I am at their mercy, forced to adapt to their every whim.
I'm not as tuned into iOS right now but a guy I work with just got an Android gig. As soon as he started looking he got a ton of calls and found one he liked in less than a week.
The suggestion "Containerize the airline industry" is wrong on so many levels. First of all every air port in the world would have to install new equipment. That would take money and time. Secondly every airline would have to buy new planes. Thirdly it ignores the reality that container ships are bot like airplanes. Airplanes have ventilation, electronics and structural requirements that ships don't have.
I once joined a project that had been going on for 5 years with >100K lines of Python. At any given time we had more than 25 programmers. In my two years on the project I never had a problem reading someone else's code - it was great for maintainability. Our project was used by hundreds of engineers on a critical path of a multi-billion dollar project. Anyone who thinks Python doesn't work for serious development doesn't know what they're talking about.
Cyclists insist on their rights but do not accept their responsibilities. Once I was walking in a crosswalk with the light when the guy zooms through the crosswalk a foot in front of my face face. I swear at him and he stops says "What did you say?" "I said pedestrians have right of over bikes way in a crosswalk" He says "I knew that" I said "Then act like you f*ing know that!"
I have never used lambda in years of programming Python. If I need a one time function I define a function and use it once. To me it is more readable and readability is one of Python's greatest virtues.
I worked on two airplane programs at boeing. The first was a derivative of the 747, the 747-400. The main features of this version that differed from previous 747s were going from analog to digital avionics, a slightly longer body and new (larger) wings. The schedule from project launch to first delivery was about 4 years. We were two weeks late on first delivery.
I also worked on the 787. The difference between the 787 and every previous Boeing plane was almost everything. The schedule from project launch to first delivery was about 4 years. We were two years late.