3 ms·

Did software engineering exist back then.

ptx 7y ago
COBOL was created in 1959. The term software engineering was coined in the 1960s. So it existed for most of COBOL's lifetime.
- freepor 7y ago
  The term teleportation was coined awhile back too.
  - eesmith 7y ago
    The term "software engineering", at least as used by Margaret H. Hamilton in the 1960s, was used to describe existing practices. "Teleportation" was not.
PunksATawnyFill 7y ago
Yes, it did. In fact, CASE tools were going to be all the rage: computer-aided software engineering. One of them was METHOD/1 from Andersen Consulting (now Accenture). If you wanted to create a variable to hold, for example, a part number... you'd create an entry in the CASE tool for it and from then on, everyone was supposed to use that one. It would have validation rules, like 30 characters, alphanumeric, whatever. The CASE tool would do code generation for screens and forms and whatnot. And.... that's about as much as I remember at the moment.
- ztjio 7y ago
  CASE tools are widely used today, but, you will see them scoped very specifically the databases in systems where everything is built around the massive pillar of a major db implementation. I worked for a company for little while that made extremely effective use of this approach allowing hundreds of devs to effectively work simultaneously on a single monolithic system. It was shocking. I was so impressed. I've still never seen any software organization so... organized. And they owed it largely to the protocols revolving around their use of a CASE tool.
Zenst 7y ago
Had source code control, albeit printed manual audited to the nth degree with any production changes having to be fully audited and signed off and compared with original with light boxes twice by separate people level of SCC. Yeah experienced that back in the 80's, it got easier though. As for standards you would see from one company to another - early days and lucky to have separate department use same standards. So payroll would have different standards than marketing, but separate ecosystems and less of an issue, beyond team cultural changes and analysts quirks. But then, standards change over time and become usurped. So could very well ask the same question in 20 years time as the approach is always changing. May even be a call for C programmers then.
varjag 7y ago
Did you ever wonder how Internet was created before the Internet
imtringued 7y ago
That's an incredibly bad argument. If they wrote the programs 40 years ago and still use them they had 40 years to fix the business process. You can't argue that something is broken because it's old and then argue that you didn't have enough time to fix the process.
- Kye 7y ago
  I wouldn't assume the fault is with the people who built the system. There is a reason they're looking desperately for people who know COBOL. Implied: they don't have any, and the systems have been ticking along for decades with the occasional call to a consultant who asked more than they would pay to modernize them. Now management will pay even more because they're desperate and end up with a rushed solution that breaks again in the next crisis.
kjs3 7y ago
No. Nothing existed before you started using Javascript in your moms basement a couple of years ago. Wirth, Booch, Brooks, Neumann, Bachman, Dijkstra, Belady, Parnas and the rest never did anything worth much. Why do some people take joy in wallowing in ignorance. Sad.

ptx 7y ago

COBOL was created in 1959. The term software engineering was coined in the 1960s. So it existed for most of COBOL's lifetime.

freepor 7y ago
The term teleportation was coined awhile back too.
- eesmith 7y ago
  The term "software engineering", at least as used by Margaret H. Hamilton in the 1960s, was used to describe existing practices. "Teleportation" was not.

PunksATawnyFill 7y ago

Yes, it did. In fact, CASE tools were going to be all the rage: computer-aided software engineering. One of them was METHOD/1 from Andersen Consulting (now Accenture). If you wanted to create a variable to hold, for example, a part number... you'd create an entry in the CASE tool for it and from then on, everyone was supposed to use that one. It would have validation rules, like 30 characters, alphanumeric, whatever. The CASE tool would do code generation for screens and forms and whatnot. And.... that's about as much as I remember at the moment.

ztjio 7y ago
CASE tools are widely used today, but, you will see them scoped very specifically the databases in systems where everything is built around the massive pillar of a major db implementation. I worked for a company for little while that made extremely effective use of this approach allowing hundreds of devs to effectively work simultaneously on a single monolithic system. It was shocking. I was so impressed. I've still never seen any software organization so... organized. And they owed it largely to the protocols revolving around their use of a CASE tool.

Zenst 7y ago

Had source code control, albeit printed manual audited to the nth degree with any production changes having to be fully audited and signed off and compared with original with light boxes twice by separate people level of SCC. Yeah experienced that back in the 80's, it got easier though. As for standards you would see from one company to another - early days and lucky to have separate department use same standards. So payroll would have different standards than marketing, but separate ecosystems and less of an issue, beyond team cultural changes and analysts quirks. But then, standards change over time and become usurped. So could very well ask the same question in 20 years time as the approach is always changing. May even be a call for C programmers then.

varjag 7y ago

Did you ever wonder how Internet was created before the Internet

imtringued 7y ago

That's an incredibly bad argument. If they wrote the programs 40 years ago and still use them they had 40 years to fix the business process. You can't argue that something is broken because it's old and then argue that you didn't have enough time to fix the process.

Kye 7y ago
I wouldn't assume the fault is with the people who built the system. There is a reason they're looking desperately for people who know COBOL. Implied: they don't have any, and the systems have been ticking along for decades with the occasional call to a consultant who asked more than they would pay to modernize them. Now management will pay even more because they're desperate and end up with a rushed solution that breaks again in the next crisis.

kjs3 7y ago

No. Nothing existed before you started using Javascript in your moms basement a couple of years ago. Wirth, Booch, Brooks, Neumann, Bachman, Dijkstra, Belady, Parnas and the rest never did anything worth much. Why do some people take joy in wallowing in ignorance. Sad.