DSpinellis

6 ms·

1.
Barings, Boeing, and Bots: The Promises and Perils of Delegation(spinellis.gr)
2 points by DSpinellis 2mo ago|0 comments
2.
Why agentic AI needs better experts(spinellis.gr)
3 points by DSpinellis 2mo ago|0 comments
3.
by DSpinellis 4mo ago
Given that AI-generated code is not 100% perfect, we need to take into account the time and cost of reviewing when we discuss the productivity boost AI developers receive from code.
4.
Why reviewing AI-generated code is devilishly hard(spinellis.gr)
3 points by DSpinellis 4mo ago|2 comments
5.
Vibe coding toward the incident horizon(spinellis.gr)
3 points by DSpinellis 7mo ago|1 comments
6.
An initial analysis of the discovered Unix V4 tape(spinellis.gr)
98 points by DSpinellis 9mo ago|4 comments
7.
by DSpinellis 10mo ago
I convinced a software company to use a version control system (RCS on shared disk) back in 1993. To make it work we had to setup a network — Ethernet over (thin) coaxial cable at the time. This was so new to us that we didn't know we
8.
by DSpinellis 10mo ago
Indeed! The repo includes some v4 elements: https://github.com/dspinellis/unix-history-repo/tree/Researc... The provided kernel predates the actual edition by a few months. It is based on https://
9.
by DSpinellis 10mo ago
I don't think the concept of a rebase existed before Bitbucker and Git.
10.
by DSpinellis 10mo ago
30 years ago (1995) open source offerings: mostly CVS for large projects and RCS for smaller ones. On the proprietary side, the aged SCCS was available and used, while Perforce and Microsoft Visual Source Safe were being launched.
11.
by DSpinellis 10mo ago
I published an updated extension of this post's linked article in Empirical Software Engineering. You can read it without a paywall at https://rdcu.be/b7FzE . You may also be interested to see the actual GitHub reposit
12.
by DSpinellis 1y ago
That's the point: non-dependant tasks can run concurrently in Airflow. In sh/BAsh/dgsh dependant tasks can also run concurrently, as in tar cf - . | xz.
13.
by DSpinellis 1y ago
A nicer syntax and a lower probability of deadlocks.
14.
by DSpinellis 1y ago
And, more importantly, assign a name to a process, so that it can appear multiple times in the graph.
15.
by DSpinellis 1y ago
Admiring your multi-tasking!
16.
by DSpinellis 1y ago
I'm curious: what do you mean by "dgsh will use iteration under the hood too"? Dgsh does several things under the hood, but I wouldn't characterize any of them as iteration.
17.
by DSpinellis 1y ago
Manually playing around with fds is definitely unmaintainable. My hope is that a clean syntax can help create maintainable complex pipelines.
18.
by DSpinellis 1y ago
Thank you for the suggestion. This would mean that you'd also then create some mapping from each name (like git_log) to its implementation, right?
19.
by DSpinellis 1y ago
Nice benchmark! This is a (not at all efficient) awk one-liner. awk -F\; ' $2 > max[$1] { max[$1] = $2 } !($1 in min) || $2 < min[$1] { min[$1] = $2 } { sum[$1] += $2; count[$1]++} END { for (n in sum) printf(&quot
20.
by DSpinellis 1y ago
I've found creating pipelines with Python to be messy and intuitive. Other than creating a DSL to express them I can't see how DAGs can be expressed naturally with Python's syntax. Even creating tools in Python that can be c
21.
by DSpinellis 1y ago
I went through two iterations before adopting the current syntax. Truth is neither me nor Doug McIlroy, the inventor of Unix pipes, who kindly and generously provided feedback during dgsh's development, had something better to propose.
22.
by DSpinellis 1y ago
Author of dgsh here. This is definitely not what I had in mind.
23.
by DSpinellis 1y ago
Apache Airflow solves a very different problem. Its DAGs are static dependencies between sequentially executed processing steps, whereas the DAGs of dgsh express live direct data flows.
24.
Choosing Email over Messaging(spinellis.gr)
1 points by DSpinellis 1y ago|1 comments
25.
False authorship: An AI-generated article was published under my name(researchintegrityjournal.biomedcentral.com)
2 points by DSpinellis 1y ago|0 comments
26.
A 50 year retrospective on the first source code control system(computer.org)
4 points by DSpinellis 1y ago|1 comments
27.
by DSpinellis 1y ago
Fifty years ago Marc Rochkind wrote SCCS, the first version control system, which later inspired RCS, CVS, and Git. In the March issue of the IEEE Transactions on Software Engineering he provides a retrospective of SCCS: its innovations, i
28.
by DSpinellis 2y ago
I advocate the following rules for when to write and when not to write a shell script. # Write a shell script: * Heavy lifting done by powerful tool (sort, grep, curl, git, sed, find, …) * Script will glue diverse tools * Workflow resembles
29.
by DSpinellis 2y ago
Pipe-related concepts in various restricted forms were floating around for years. Doug McIlroy indeed proposed them in 1964 and was heading the Bell Labs team when they were implemented in the Third Research Edition of Unix (1973). See ht
30.
Large language models reduce public knowledge sharing on online Q&A platforms(academic.oup.com)
5 points by DSpinellis 2y ago|0 comments

More ›