https://thenewinquiry.com/the-honeyed-siphon/#:~:text=The%20....
321 karma · joined January 14, 2012
https://thenewinquiry.com/the-honeyed-siphon/#:~:text=The%20....
Agreed, but I don't think this goes broad or deep enough, particularly with respect to the power of iteration and recursion in conversation: the basics of reflection over prior action. The key here is to realize that there's a natural sensemaking process that goes from action to reflection to repetition and that sensemaking process is a collaboration between computer agents and human agents whether it remains implicit or explicit in design and whether the computer agent is programmed to recognize and resolve conflict and consensus in not just subjective but objective fact-or-fiction. Right now, we aren't even at the latter, let alone the former. That will come with time and acceptance of the veracity problem that is writ large in the AI UX currently.
> it mostly boils down to knowing what to ask and actually thinking of asking it to begin with.
Indeed, recognition vs. recall is as old as GUI vs. CLI. However, the key is to realize that some folks will be faster through recall because they've actually built up the knowledge to recall vs the symbolism to recognize.
My argument is that, for me, there's little value in chat because that's not how I prefer to interact with any human or computer agent via writing. It's too slow. I much prefer the batch mode where there is larger latency between question and answer, but that latency provides an emergent cadence to the conversation that is more natural, providing room for listening-and-thought-before-response. This may sound old-fashioned like punch cards, but conversation has been missing from many technical things for years and we've paid the price for that silence.
1) Age
2) BDD-style or what I call a madlib proxy for playing cucumber on TV. Not a fan having used it in an RoR context I can only call hipster-engineering, not what DHH described.
3) I just had the discussion on redux vs. datomic vs. riak with friends yesterday.
4) Ditto the conversation on MVVM and the implied constraint complexity of putting nodejs and chromium in the same deployment package and calling it electron while carrying on how simple it is relative to... a world where everything is actually native all the way down?
5) Me too on the CASE era.
6) Cue Donald Knuth on literate programming. One thing that cucumber is not, but I think taking another iteration at literate programming in light of GPT or LLMs is a good idea since Knuth is never wrong just 50 years ahead of time, but we needed a collaboration of human-computer agents that is patterned on a sensemaking protocol that can resolve subjective truth by consensus of man and machine. How else could you possibly resolve the fact that the SOTA lies to me on a daily basis while defending itself and its lack of veracity with force in what can only be seen as emulating the culture of one's parents.
7) Yes, AI should help on the iterations. Those short design sketch-to-demo we used to do at the design studio with sketch on Monday and demo on Friday should be much easier today to go from breakfast sketch to dinner demo, but I don't think they are. The tooling is radically better but that better has come at the cost of complexity and going sideways, neither of which are being fully felt and accounted for reflectively, i.e. they're not how you get to typing less and having the tools do the work because when they break, the debugging is mind-crushing.
8) I think the thing that's missing in the trivial part is that it's not actually trivial, but particularly because the software is the message and that insight stems from the fact that software has emergent properties such as extensibility, composability, and a resultant rate of change that make it very difficult to compare from decade to decade because software's fundamental disequilibrium stems from the fact that the full stack is in constant flux from a mad hatter's pop culture where we never sing the same song twice. There's value in theme and variations if it can be modeled as improvisational human-computer design pairing rather than yet another orchestration. Joe Beda was as right about improvisation as Knuth is about the art of computer programming.
9) I guess the t-shirt is: I'm not waiting...
10) In the immortal words of Raymond Loewy: Never leave well enough alone.
If there's a set of artifacts in software that achieve what I hope for with AI, it's somewhere between Bret Victor and https://iolanguage.org/
I remember working on OS/2 from my internship in college through the first few commercial software jobs after graduation though we used IBM's C/C++ compiler, which may have been shared with Microsoft but the exact origin I don't recall.
I very much preferred Borland from my days in Turbo Pascal and Turbo C++ though I can't remember if that was just Intel or Atari ST (68K)?
Lots of game-changing software was built on OS/2 at the time because getting that kind of thread performance was nearly impossible since it predated everything else in the late 80's so things like ATM machines, stock trading systems, even things that are still being sold today though I'm sure OS/2 is long gone from the releases:
https://www.broadcom.com/products/mainframe/product-portfoli...
Pretty amazing for the time given there are things we did there that just haven't lived beyond NT or the like.
It's sad that the entire industry seemed to forget about CUA en masse. It would be really useful now with the return of tiling to prominence.
https://www.amazon.com/The-Hypomanic-Edge-John-D-Gartner-aud...
I've found the ability to recognize and self-select for in-office, remote, and hybrid work dynamically at runtime since 1999 to be instrumental in my work from coast to coast.
"Hey Guys, I need to go deep. I'll see you in a couple days."
Followed by a demo 5 days after a napkin sketch of something nascent.
No, not really. All else being equal:
I'd say that today, it's much muddier than it was maybe ten years ago, before the data science explosion and cloud explosion.
That is, turn-key cloud Postgres is not Y2K Postgres, and MySQL post-Maria is not Y2K MySQL. In the former, administration of Postgres has gotten much easier since Heroku got involved and Andy Pavlo started talking about self-driving databases. In the latter, MySQL can do text search well enough that I sat pair programming this with a young engineer around 2016-2017 when I'd have argued prior that you were wasting your time.
In the end, it probably comes down to how you rank your requirements:
usability, performance, suitability for a particular purpose.
Things like postgis and pgrouting may have little equal, so like others, those can be huge differentiators if you need them and see the advantage in db backend computation without invoking the N+1 query problem in aggregate.
I'm biased since I used MySQL before the inefficient backend was deprecated and I used PostgreSQL to do all manner of experimental EAV implementations using bjson including various forms of tuples from Rich Hickey.
All hail Stonebraker.
What I wonder is this: is there a story happening now that has similar good will for the future of AI without having commercial or social computing as its basis?
The reason I love Linux is that Linus started and finished before commercial and social concerns became the raison d'etre in software.
I've crashed and burned startups while never comparing any of them to driving half-blind without my glasses at night.
Human sciences and user research provide excellent solutions to customer behavior. Like F1 cockpits, the risk scales with the domain.
F1 is not just a vector sport. If it were, math may be enough to win. Turns out F1 takes engineering, mechanics, and a driver.
However, viewed through a macroscope, F1 dynamics are closer to a cooperative game, as in software development.
While an unknown in software is competition, much larger unknowns are given by shifts in teams, machines, and their methods.
Turns out that comparing F1 and software development from 1970 to 2020 are remarkably the same story for much the same reason. Neither exist in stasis.
F1 and software development have more in common than is obvious from the grandstand.
"who the world wants you to be" from the OP.
This is toxic positivity.
There's a place for feedback loops whether you label it tldr; GPT, sensemaking, or dislike.
As an old C++ hacker, I'm waiting for the day when modern C++ shops read Accelerated C++ from Koenig and Moo circa two decades ago. Then, I could rejoice in someone anywhere writing C++ code that more closely resembled the python-esque C++ masquerading as pseudo-code in that book.
More sadly, I just keep seeing people emulate bit-twiddling from yesteryear when the compiler likely optimizes a fair bit of this.
The cyclomatic complexity scores in the paper look off by an order-of-magnitude but they may be better than the laugh riot I've measured in the last few years and my math may be failing me at runtime.
I don't know anyone who has done the rotary or diesel conversion, though I have driven the zero and know another designer who built an electric motorcycle from scratch. When I say from scratch, I mean sketches, solid works, chassis - the whole 9. Of course, this gets easier at the edges where wheels, handlebars, exhaust, lights, and batteries are abundant.
My daily awareness of his progress was working close to his desk at work, so I'm not sure where it's at today though I recall he was about to transition from chassis to engine at the time - 2016. He was definitely ahead of the curve. Sadly, my skills are in things that we have the luxury of pretending are not bound by the laws of physics. ;->
"The poet laureate of functional programming" from the guardian:
https://www.theguardian.com/technology/2022/jun/03/richard-b...
and the post on hacker news:
Chronic Type 1 Diabetic here so the things I'm about to describe are high risk and are not endorsed by anyone in my world-class care team. They are aware that I understand and accept the risks having grown up and been educated at Children's Hospital and Joslin. I wear an insulin pump and two Continuous Glucose Monitors (CGM).
It's all about executive function. From a root cause perspective, I'd start there since that's really what determines health.
My fasting started 15 years ago when I read Seth Roberts Shangri La Diet.
https://en.wikipedia.org/wiki/Seth_Roberts
I'm one of those people who can balance empirical and phenomenological despite n-of-1 emergent qualities.
In 2007, I'd fast for 3 days liquid-only roughly once every 90 days. I used Roberts extra light olive oil hack (ELOO) to help. I don't do that anymore though it had no negative effects in my experience. I practiced that cadence until 2020.
In 2019, I stopped eating meat. I like meat but it was the easiest way to get the caloric load and impurities down. From fall 2019 to summer 2020 I lost 50 lbs. Ate plant-based whole foods for two years, then and now vegetarian. Over that time I've varied from 0MAD, 1MAD, and 2MAD while finishing a half and full marathon in 2021 and 2022, respectively. I run mostly daily, varying between 10K and 10 miles with occasional half marathon distances tossed in for good effect.
Post 2022, I've done a series of experiments with some success. Those include emulating Valter Longo's protocol with soup for a Fast-Mimicking Diet (FMD). Also, my current regimen has been eating M-W-F and fasting T-Th-Sat-Sun. I sustained that for a couple weeks and I'm eating once or twice daily now. I'll probably reverse the intermittent binge-ing in new experiments, so 4 days eat, 3 days fast per week; theme and variations.
I'll probably return to a odd-metered cadence of fast-feast weeks as it made meals much easier with the challenges you mention.
For whatever reason, I ate 5-6K calories/day from high school through college and couldn't fast a few hours. At my age now, fasting is easier than eating and could very well be related to delayed gastric emptying or some other complication of disease. I have no evidence.
The less I eat, the better I feel, while benefiting from the anecdotal improvement in cognitive function that comes with ketosis. Like leading ultramarathon runners, I don't practice ketosis as perfection, but rather, a state I hit occasionally without making it an end-goal. Paraphrasing Peter Attia, it's the cycle, not the state that matters.
The limiting factor for me is of course not ketosis, but ketoacidosis. The former is well-managed for me because it's predictable, euglycemic, and easy-to-fix with carbs. The latter was common enough to me as a young person that I know the ketosis flu feeling well and avoid it by testing compulsively. Just like software!
FWIW, I've vomited water in euglycemic ketosis and know enough to avoid the emergency room. This scares my medical team, since there are truly frightening and deadly side effects (refeeding syndrome), but I'm still here.
I've worked in medical devices and healthcare so my learning has been enhanced by those experiences where we treated patients who responded well to coaching around metabolic illness including cancer and diabetes, both of which respond to diet and fasting.
A more evolved process would avoid using such vague words to define problems that are complex, dynamic, interdependent, social, and psychological. Performance and expectations are wicked problems.
Determinations of performance and expectations are often closed and siloed as opposed to being open and transparent. That's a cultural problem arising from "difficult conversations". Organizations often make the mistake of over-simplifying these conversations.
I can think of few chasms between performance and expectations in twenty years that was reflective of reality. Organizations make sense of those situations slowly, poorly, and privately, if at all.
Why? Because if their cultures were reflective, protean, or sensemaking at all, they were closed conversations, ill-defined, informal, and not repeated on a regular basis.
A few examples I've sampled from my work:
- Numerous individuals suffered from self-medication while receiving little care or concern.
- Founders copy emotional traits of Jobs, Gates, Musk, and Torvalds not the intellectual ones.
- Trauma: ill-defined roles, changing expectations, and stack ranking.
Personally, I'll take competent but rough-around-the-edges because my experience has been that my most talented coworkers all fit that description no matter their education and experience while realizing that the edges are where the most important insights occur.
https://abc.xyz/investor/other/code-of-conduct/
Doesn't seem like the transformation from "don't be evil" hit its intended ethics target.
I was outspoken in my interview about snaps. Of course this is the path to success in a monoculture.
It depends on how you count, of course. I've done these statistics using a variety of git tools over the years. Being lazy, I asked various AI interfaces the question since AI seems better at faking SQL than I am at QUEL or the DSL of the week in schemaless databases.
The results vary depending on decade, particularly since Intel have increased their kernel contributions from 2013 onward. However, when ranked over the 30 years from 1993-2023, as of today, assuming no latency in the data, Redhat wins:
- Red Hat: 16.9% of total contributions
- Intel: 12.8% of total contributions
- IBM: 8.4% of total contributions
- SUSE: 6.3% of total contributions
- Google: 4.5% of total contributions
- Linaro: 3.9% of total contributions
- Samsung: 3.2% of total contributions
- Oracle: 2.7% of total contributions
- AMD: 2.1% of total contributions
- Huawei: 1.9% of total contributionsSo while I think regular writing is an important part of thinking, and AI is an important part of our evolution in thinking, it is a mistake to think that we should just "let the AI do the writing" or "get GPT to do it for you" as it will be frequently wrong, particularly when the conversation rises to the complexity of requiring sensemaking, i.e. it's not just objective fact that's not difficult for machines to compute, but rather messy, subjective consensus where the need for the conversation with AI becomes particularly powerful and may, in fact, change our course in ways we could not anticipate. That is, the emergent sensemaking we require is a collaboration of humans and machines that arises just as Kubernetes did, by realizing that the need is for improvisation AND orchestration, not one OR the other.
https://medium.com/@jannaq/the-robot-takeover-is-already-her...
https://www.washingtonpost.com/archive/lifestyle/wellness/19...
Who does that value prop target?
What's the embrace and extend?
None of these are apparent to me.
https://www.sae.org/news/2018/10/2018-yamaha-niken-chassis-t...
I'm just a software engineer, not a mechanical engineer, so any explanation would fall short. However, I've been surrounded by world-class Mech E's for decades, so I can remember these conversations being out of my depth!
I've also done urban commutes on bicycle and motorcycle for decades, so I can say given my experience, this is much easier to feel than reason about. You can tell by watching a person ride at licensing whether a person has integrated this feeling or is still reasoning about it. Hope this helps.
Thus, "define: agile" gives:
Characterized by quickness, lightness, and ease of movement; nimble. Mentally quick or alert.
My personal definition stems from reading a combination of Alistair Cockburn laced with Alan Holub. Combining:
Teams that are alert, light, nimble, and quick.
My experience has been that there were two teams I've been part of that had those qualities:
1) Pre-Y2K teams that arrived at the agile manifesto having no jargon, only action and insight. 2) Teams that had the luxury of agility because they were size-constrained by finance.
I'd emphasize that you don't do agile. Doing agile is part of the problem of cliched cargo cults.
Rather, you either are or not agile as evidenced by your results or outcomes repeated on a regular cycle followed by the gold standard of sensemaking: retrospective.
The problem is not scaling technology. The problem is scaling agile humans since communication does not scale linearly when it leaves a single skull. What we are missing is an order of approximation (Big-O) for teams. The closest I've seen is maybe this:
https://getsturdy.com/blog/2021-11-29-scaling-teams
I find little evidence that there is emergent research around this.
My dad wasn't a plumber though he was a member of the steamfitter's union at one point.
These are similar problems though they may not look alike at a casual glance:
Plumbers make good money, but I'm not sure there's deep meaning in the pipes because, like metadata, pipes go sideways too.
I'm having trouble thinking of a Turing award winner who won because they went sideways. The key is that the data insights of a Turing award winner are durable, unlike the transient nature of most of what we do with data in modern organizations.
Ultimately, this sounds more like Grothendieck in math than computer science:
https://www.psychologytoday.com/intl/articles/201707/the-mad...
Metadata sounds like it's the wrong word as the structure we are looking for isn't the ephemeral structure that most of us discover, but rather, it's closer to special relativity.
The Turing award winner who comes to mind is Leslie Lamport:
https://en.wikipedia.org/wiki/Logical_clock
There may be a better choice that demonstrates the worthlessness paradox of data engineering or metadata or data science in a modern management context.
It's not that metadata are actually worthless as in fitness-for-a-particular-purpose. Rather, it's that the insights that we and our organizations reap from that metadata is increasingly short-term - anything but durable.
https://plus.maths.org/content/stuff-happens-ordering-histor...
The only references I can think of on quality are either Pirsig's MOQ:
https://en.wikipedia.org/wiki/Robert_M._Pirsig
or Wallace's posthumous Pale King:
https://en.wikipedia.org/wiki/The_Pale_King
Your friend's experience working in government sounds exactly like the Pale King to me.
The worthlessness you're referring to seems much more dependent on the fact that management culture has evolved to somewhere between a cargo cult and celebrating short-term things that don't count, both illuminating an illusion of control.
I mean, does anybody, anywhere still get a gold Rolex and actually retire?
I shared an office with the nice, modern gentleman who wrote this:
https://blog.moertel.com/posts/2002-04-25-coders-guide-to-co...
Another of my office mates was a barista. To me, this is like reading, "Shop class is soul craft" because coffee is definitely art in the hands of an experienced aficionado.
After a decade of personal experiments with coffee devices you'd recognize, I've settled on a cheap and simple Mr. Coffee burr grinder and Bodum pour-over. I don't pre-soak my filter, just grind-and-go with a Sumatra bean from Fresh Thyme.
My experience has been that coffee is phenomenological to the point that it seems to resist attempts at empiricism, similar to audiophile pursuits; like software, it's prone to Heisenbugs!
https://dl.fedoraproject.org/pub/fedora/linux/development/ra...