Marianne Bellotti

medium.com/@bellmar · Personal blog · on HN since 2018

Marianne Bellotti is an engineer who writes on mainframes, COBOL, TLA+, SRE and engineering teams.

What HN saysHN links it in COBOL and mainframe threads, especially her hello world on z/OS and her piece on COBOL and floating point math.
17HN people shared it
7linked it in comments
32stories submitted
3.6Kstory points
10 months agolast shared
2018people per year2026

Most-shared posts

  1. 1
    Is Cobol holding you hostage with Math?
    6 people · 206 points · first shared 2018 · 115 comments on HN
  2. 2
    Hello World on z/OS
    6 people · 203 points · first shared 2018 · 121 comments on HN
  3. 3
    When Computer Networks Were About Nationalism
    3 people · 4 points · first shared 2019 · discussion on HN
  4. 4
    Introduction to TLA+ Model Checking in the Command Line
    2 people · 178 points · first shared 2019 · 44 comments on HN
  5. 5
    SRE as a Lifestyle Choice
    2 people · 170 points · first shared 2019 · 41 comments on HN
  6. 6
    Heroes and Juniors: Increasing Engineering Team Velocity
    2 people · 98 points · first shared 2019 · 24 comments on HN
  7. 7
    Making AI Better by Making It Slower
    2 people · 15 points · first shared 2020 · 5 comments on HN
  8. 8
  9. 9
    Why is this idiot running my engineering org?
    1 people · 326 points · first shared 2020 · 167 comments on HN
  10. 10
    Old Code Gets Younger Every Year
    1 people · 240 points · first shared 2020 · 188 comments on HN
  11. 11
    A Software Engineer’s Guide to Cybernetics
    1 people · 179 points · first shared 2020 · 59 comments on HN
  12. 12
    People Hacks for Technical Leads
    1 people · 172 points · first shared 2018 · 31 comments on HN
  13. 13
    The Land Before Binary
    1 people · 132 points · first shared 2018 · 29 comments on HN
  14. 14
    The Yang Gang and Its Bots
    1 people · 110 points · first shared 2020 · 179 comments on HN
  15. 15
    Using TLA+ to Model Cascading Failures
    1 people · 98 points · first shared 2019 · 24 comments on HN

What HN people wrote when they linked it

GoblinSlayer · 2019-06-06
isaachier · 2020-04-05
From what I gather, it's an issue of floating point precision. See more here: https://medium.com/@bellmar/is-cobol-holding-you-hostage-with-math-549…
coleca · 2019-09-15
Surprisingly there are reasons why running financial type systems in COBOL makes a lot of sense. Evidently COBOL really excels at foxed point decimal operations more so than other “modern” languages like Python and Java. Porting then off the mainframe isn’t a trivial exercise it seems. https://medium.com/@bellmar/is-cobol-holding-you-hostage-with-math-549…
tyingq · 2019-07-17
A pretty good account of a "new to mainframes" person figuring out how to make their first Cobol program on z/OS: https://medium.com/@bellmar/hello-world-on-z-os-a0ef31c1e87f
floatboth · 2019-05-23
From what I've heard, redundancy and scalability in a single machine (like, you can hot-swap CPUs on a running machine and have lots of redundant RAM, etc.) and being able to run an OS with backwards compatibility all the way to the fscking 1960s or whatever. That OS is… something: https://medium.com/@bellmar/hello-world-on-z-os-a0ef31c1e87f
spc476 · 2018-09-15
There was a link to another article [1] about how COBOL may be better suited to certain mathematical calculations. The article in question presented this iterative function: x[0] = 4 x[1] = 4.25 x[i] = 108 - ((815 - 1500 / x[i-1] ) / x[i-2]) It blew up on iteration 14 using floating point, but COBOL could be programmed to go further (by using more decimal places past the decimal point). [1] https://medium.com/@bellmar/is-cobol-holding-you-hostage-with-math-549…
dredmorbius · 2019-10-08
This article expresses one piece of the problem that's increasingly suggesting to me that it's not hiring or job-hunting that's broken, but the model of employment itself. (For yet another example of broken hiring, see this story, also presently on the HN front page: https://medium.com/@bellmar/sre-as-a-lifestyle-choice-de9f5a82d73d) Skills assessment (and assertion) is difficult. Skills relevance is hard to assess. Incorportion and business as risk-externalising systems has worked rather too well (though the problem's hardly new), with much of employment risk being shifted from employers to employees, and from large employers to small ones (answering the anticipated small-business / startup response). The entities most able to manage risk are those most equipped to shift it elsewhere. There's also the problems of offshoring, outsourcing, and shifting to the modern variants of endentured servitude, generally: employment-contingent temporary visa workers (H-1B in the US, similar equivalents elsewhere). And of gig, contingent, temporary, part-time, and other employment conditions, as well as of the tying of specific benefits (most especially healthcare) to employment status. Don't even get me started on pensions/retirement, professional ethics, whistleblower protections, and labour organisation.

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close