Software Engineering
There are 43 posts filed in Software Engineering (this is page 3 of 5).
Read: Banks scramble to fix old systems as IT 'cowboys' ride into sunset
If I ever get tired of working in the aerospace industry, looks like there is plenty of need for old COBOL programmers….
737-MAX software update still in progress, Collins Aerospace/UTC is involved
From recent reporting, the FAA is still several weeks away from approving the MCAS software changes relating to the Lionair and Ethopian Airlines crashes. In the industry media I read, I had not seen anything whether this was software created by Boeing or by one of its suppliers. This morning, I decided to do a search, and quickly found that it was my company (Collins Aerospace) involved in MCAS software development, and that Collins Aerospace supplies the computer that runs the software. Hoo boy!
- Washington Post: Boeing’s 737 Max design contains fingerprints of hundreds of suppliers
- The Gazette (Cedar Rapids IA, former headquarters location of Rockwell Collins/Collins Aerospace): United Technologies is parent company of sensor maker under scrutiny for Boeing 737 Max failure
Philip Greenspun makes it sound simple, after the damage has been done. The trick is to figure this out before there is an accident.
Read: Discussing Social Networks, Again
I think that any tool can be a social network, we should start networking with whatever we have!
Read: Java’s Forgotten Forbear
An interesting history of an early Pascal development environment. Turbo Pascal was also an early success for PC software development.
(via Dave Winer) – I used Fortran as my first professional programming, interesting to see that there are still so many users…
How embedded software projects run into trouble
Jack Ganssle has written articles for his top ten list of how embedded software projects run into trouble. Most of this could apply to any software project! Here are the links:
- Unrealistic schedules
- Quality gets lip service
- Poor resource planning
- Writing optimistic code
- Weak managers or team leads
- Crummy analog/digital interfacing
- Bad science
- The undisciplined use of C and C++
- Jumping into coding too quickly
- Not enough resources allocated to a project
When I read this, I decided to start working on the asset that is my weblog. I will strive to post something daily, even if it is only a link….