I hate IDE's because they are "helpful" (not).

I have been programming since 1976 with line editors, then emacs and vi. My muscle memory conflicts with the IDE.

Also, IDE's HIDE STUFF that can take days to find and correct. PITA.

IDE's allow for very long code lines. You can easily lose code at the far right end of a line.

Short version: I HATE IDE's. Yes, I am an old fart. A command line is superior.

I agre that these "points" are just good practice that everybody should follow.

--

--

I had a gig with a French aerospace company. The project bought a configuration management tool (this thing is required by DO-178C). It came with training. I looked at the homework before the training. In the training, I looked at the instructor and said "It's obviouus you eat your own dogfoot." He agreed.

The French guys were very confused. And not for the first time. The cultural differences were interesting, and sometimes astonishing.

--

--

I had a gig on the next design of a medical device. The key function was about 1000 lines of a C state machine. Very few comments. It took me a month to document what it was doing. We made it's replacement table-driven. The new code was under 200 LOC in total (several small functions). Including comments.

--

--

I had an 8266 project. Good board.

I didn't know about using the Arduino IDE (which I LOVE, except for the editor, but it seamlessly allows me to use vim).

I used Lua to write the code. My biggest problem was code space. The Lua tool did not strip out comments. I had a sed script for cleaning out the comments.

--

--

bandit Gangwere

bandit Gangwere

Consulting Embedded Systems Engineer with 40 years of experience with Mission-Critical Projects.