shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

244
active users

#abap

1 post1 participant0 posts today

On the one hand it's nice that #ABAP is programmed on the server, we never have to worry about "continuous integration" or merge conflicts or anything like that, on the other hand code being locked in someone else's transport request (or nowadays increments in addition, for the public cloud) can get kind of annoying ... or today I'm locking myself out from doing an upport because I'm still working on fixing another problematic upport ...

Banks and Social Security are not using #COBOL because it’s so great, but because it’s so hard to migrate to something else.

They should and do migrate away … very slowly and carefully.

(I‘m in banking.)

I don’t dislike COBOL. I program daily in #ABAP, which looks like a COBOL dialect. I don’t mind verbosity, verbosity increases readability and debuggability. No devs? Train some. But COBOL developers tell me it has serious limitations. It’s just old.

Cleaned some old #abap code today so I could see and read it. Why do people comment code with "I was here" comments, that say nothing?

E.g. "for FW254" what's that supposed to mean? I suppose it may have been a ticket number in a long dead ticketing system, but today it's just "I was here"...

Also why comment out code instead of deleting it, some code is now more commented out than live code. Impossible to read.