Tootfinder

Opt-in global Mastodon full text search. Join the index!

No exact results. Similar results found.
@dougmerritt@mathstodon.xyz
2024-11-19 16:57:30

@…
'A rare copy for sale of "Lisp Style and Design" by Molly Miller and Eric Benson (Digital Press, 1990), a great book cited by Paul Graham in On Lisp that covers often overlooked topics. All the proceeds will be donated to the Medley Interlisp Project.'

@kurtsh@mastodon.social
2024-10-05 07:48:01

IronNet goes bankrupt. Nope, I hadn't heard of 'em either.
"Collapse of national security elites' cyber firm leaves bitter wake" | AP News
apnews.com/article/keith-alexa

@Maurice809@cherprang.xfk48.com
2024-09-16 09:49:24

[Cybersecurity]
Je suis très heureux de vous annonce une nouvelle certification auprès de #IBM #Training
« Cybersecurity Fundamentals »
by #IBM #SkillsBuild
Une étape de plus dans mon cursus dans mon cursus d'Analyste cybersécurité ou de hacker éthique
credly.com/users/moret-thomas

@x_cli@infosec.exchange
2024-10-04 13:32:55

Unpopular opinion on software development
Yesterday, I came across CI cultists.
They were preaching one should merge in main multiple times a day.
Quite frankly, I associate this behaviour to lab rats compulsively clicking the button to get gratifications (please don't do that to rats).
I think developers should refrain from becoming merge junkies. Code review is essential for good code quality. Automated tests suck at detecting logical errors, security vulnerabilities, and even decent code coverage.
Also, I believe pair programming is absolutely not a strategy to allow continuous integration. Everybody involved in the development process is drunk on their own bullshit reasons they made up to justify their poor design. Either the code review should be done by someone else, or the developers should sober up for a fortnight before code reviewing their own code.
PS: I am a software developer. I get drunk on my own bullshit as well.
#software #development #ci #codereview