@fixedpointfae TI97 Assembler
Basic
5610 Assembler
Forth
Pascal
Lisp
Prolog
C
Yacc/Lex
awk
sh
68000 Assembler
perl
VB
DXL (if you know this you are working in a regulated environment:-) )
C++
Python
Java
Scala
Erlang
Powershell
C#
This was fun, remembering old times.
Introducing #Google OSV-Scanner - an #OpenSource front-end interface to the Open-Source Vulnerability (OSV) database: https://t.co/19iOVd6HTT
The OSV-Scanner assesses a project's dependencies against the OSV database showing all vulnerabilities relating to the project.
#InfoQ
Back to the official twitter app. The ratio of tweets that I do not actively follow vs. those I do is worse than ever, 8 out of 10 or more. But nowadays those are highly entertaining. And every single day my look at twitter starts with a message from the App owner.
Hey @Twitter, just to let you know: you finally managed to let me abandon your app with your annoying attempt of baiting me in following more people by spamming my timeline with “X follows Y” messages which I am 100% not interested in.
This performance by dancer and coreographer Yoann Bourgeois ("Success isn't linear") is also a good visualization of how potential, kinetic and elastic energy are exchanged
[animated scheme: https://t.co/a4NepKzxcR]
c) And sometimes it is difficult to decide, what should be inside the hexagon and what not. Input validation is my No. 1 example here. This may or may not be part of the hex, but if it theoretically is, it may add a prohibitive level of complexity, if you want to put it there.
i have a question - i've tried explaining #hexagonalarchitecture various times & ways. Still, ppl keep writing articles to explain it, & others go, I'm trying to understand it.
so: where's the sticking point? what needs clarification, or what isn't clear?
thx for help
b) hexarch is a promise: to be able to seperate business from technology, especially those that one can not or want not to control. Imho this promise is easy to be compromised by the leaky abstraction anti-pattern, and there is little discussions about that in the original source
i have a question - i've tried explaining #hexagonalarchitecture various times & ways. Still, ppl keep writing articles to explain it, & others go, I'm trying to understand it.
so: where's the sticking point? what needs clarification, or what isn't clear?
thx for help
a) we live in a time, where re-teaching adds (or is believed to add) market value. I.e. the numerous recent articles on hexarch may have nothing to do with missing explanations in the iriginal source.
i have a question - i've tried explaining #hexagonalarchitecture various times & ways. Still, ppl keep writing articles to explain it, & others go, I'm trying to understand it.
so: where's the sticking point? what needs clarification, or what isn't clear?
thx for help
@allenholub Imho the most prominent issue with tools is the following: „if you only have a hammer, every problem is a nail.“ Hence one-purpose tools (like Jira IMHO) are used for many things they weren‘t designed for in the first place, e.g. planning, requirements engineering, documentation.