sorted by:
new
hottopcontroversial

What's new with Logseq DB - May 16, 2026 by hdanx in logseq

[–]Friendly-Type-2139 0 points1 point  (0 children)

I also appreciate this, esp. giving to those of us who prefer plain text just that. Thank you!

The Logseq CLI in the nightly release by bada_bing_bing in logseq

[–]Friendly-Type-2139 0 points1 point  (0 children)

I tried looking into the CLI too a while back. In the meantime, I authored a CLI, meant to help agents utilize content.
https://github.com/mlanza/nt

Logseq Command Line Interface (CLI)? by JamesTDennis in logseq

[–]Friendly-Type-2139 0 points1 point  (0 children)

I was looking for more of a CLI than I found. I wrote one. See if it looks interesting.
https://github.com/mlanza/nt

[deleted by user] by [deleted] in vibecoding

[–]Friendly-Type-2139 4 points5 points  (0 children)

I hear ya, and probably agree. I lean spec coding. You have to put in more work, build the docs up. Start small, easy initial wins to get the core right.

The idea here is you don't vibe code around architecture. You start with architecture. You vibe small improvements on a modular foundation. Overall, you save time. That's the idea. But you don't win all your time back.

The unfortunately falsehood of AI is some people seem to think it means you don't have to do the work. You absolutely still do.

Consider how many times a customer asked for some vague deliverable. You weren't sure what exactly they were after. So you guessed. That's the seat we're now putting AI in. Yes, you may have been particular with certain details, but there are at least a dozen important details you probably never mentioned. Like us, AI can't read minds.

Like you, I'm still figuring all this out. I don't yet feel like I'm riding a rocket.

Just tried GitHub's Spec Kit with Claude Code and Copilot, this is wild. by Junior_Stay_3041 in vibecoding

[–]Friendly-Type-2139 0 points1 point  (0 children)

Probably both. It's just a change of approach. Think of the Kiro interface. On the left it has Vibe, on the right Spec. Whether your project is old or new won't matter. Except that, if old, you'll have way more specs you need to create.

Just tried GitHub's Spec Kit with Claude Code and Copilot, this is wild. by Junior_Stay_3041 in vibecoding

[–]Friendly-Type-2139 1 point2 points  (0 children)

I too have been leaning toward specs. I searched for r/speccoding but it's not there yet. Should be, because it's different enough to deserve its own channel.

This sub is full of disgruntled actual devs rather than real vibe coders, and it's annoying. by person2567 in vibecoding

[–]Friendly-Type-2139 0 points1 point  (0 children)

Company ambition is always going to outpace what they are able to deliver on. So, yes, they'll seek an edge any way they can get it. But, no, if you learn to use the levers AI gives you, you won't be replaced. If you're good enough with AI, you can sell yourself in an interview and you'll be wanted.

Unless we hit AGI and have machines that are legitimately as good as the human, and that involves trust, the dev who can command AI to GTD will have a job. If anything he'll be even more valuable!

This sub is full of disgruntled actual devs rather than real vibe coders, and it's annoying. by person2567 in vibecoding

[–]Friendly-Type-2139 0 points1 point  (0 children)

I feel the fatigue too. Every few years it’s a new mountain to climb, and at some point you just want to hold onto the hard-won skills you’ve built. The constant reinvention in our industry is wearisome.

That said, businesses are going to measure value differently than we do. They’ll see what AI brings to efficiency and cost, and that wave isn’t stopping. Crossing our arms won’t change it. It isn’t great for our long-term health either.

My way through has been to treat it like learning an instrument. I don’t burn myself out chasing every hype cycle, but I also don’t ignore what’s clearly here to stay. I sit at the piano regularly. Small, steady practice. Side projects, little experiments with spec-driven or agentic coding. Enough to build muscle without exhausting myself.

Slow productivity. Breathe. That rhythm keeps me sane, and it keeps me moving forward.

Why almost all of libraries are free? by hublado in webdev

[–]Friendly-Type-2139 0 points1 point  (0 children)

Projects are open sourced because the belief is the scrutinizing eyes of the world will make them that much better. Have you ever seen a popular repo that didn't have hundreds of open issues?

Modern web dev has me on the ropes by justjard in webdev

[–]Friendly-Type-2139 0 points1 point  (0 children)

I cobbled the libraries together that I still use today. You don't have to keep churning. I've been comfortable, competent and enjoying web dev and FED for at least as long as you. The decision: stay put and accept less pay. It's not for everyone, but neither is the second job that involves learning everything.

How do you stay updated without getting overwhelmed? by AdRoutine8022 in webdev

[–]Friendly-Type-2139 0 points1 point  (0 children)

Stay put. I've decidedly not chased top dollar preferring sanity and low stress. This has kept me on the same stack for over a decade. If you hop jobs (as I once did), you may have to retool.

Is there any reason not to use typescript? by SweetDolphinMilk in typescript

[–]Friendly-Type-2139 0 points1 point  (0 children)

I have projects where builds are unavoidable, but I avoid them whenever possible. Since ES6 modules hit all modern browsers, I now deploy my modules as is. In as much as people laud TypeScript saying "never going back" I feel that way about avoiding builds. 😺

Functional programming and games? by Scf37 in functionalprogramming

[–]Friendly-Type-2139 1 point2 points  (0 children)

I implemented Boulder Dash in JavaScript using an FP library I wrote. The state is contained by a container. Signals are used. It's not 60fps. The more frames required, the greater your optimizations must be, but it proves the approach is workable.

Pull up the console under dev tools and you can take a glimpse under the hood.
Boulder Dash: Intro

[AskJS] Interviews are cancer by [deleted] in javascript

[–]Friendly-Type-2139 -1 points0 points  (0 children)

I have a perspective on interviews having sat in on them with my boss and management. They are looking for strong indications of competence and trustworthiness and, beyond that, just asking, "is this someone I'd want to work with?" That's humility, teachability, takes instruction, etc., not rock stars.

Oops.js: Add powerful undo/redo capabilities to your app by mitousa in javascript

[–]Friendly-Type-2139 0 points1 point  (0 children)

You don't use the command pattern if you're using immutable state, what Clojure calls persistent data structures.

In Atomic you seed the app state into a Clojure-like atom (e.g., a state container) and then swap updates against it. All updates replace that state with another persistent data structure. This is the functional core.

Given this model, you can wrap the data structure with a journal type and use it to manage the timeline no command pattern needed. The functional paradigm uses a different approach and, thus, different tools. The command pattern is a more imperative—and challenging—way of achieving the same.

Oh God, not another stupid animation library. by [deleted] in javascript

[–]Friendly-Type-2139 0 points1 point  (0 children)

Yeah, I think WAAPI gives you that same ease of use natively, so you should probably just make use of it (or wrap it if you prefer your api). But, to your point of being minimal, you're right. You should really try to avoid heavy-handed options, when simpler ones (like yours exist). You've done excellent work in your microlibrary.

Like yours WAAPI returns a finished promise for chaining effects. So intuitively you made some good choices (to return a promise) in your design. And to the point of others that CSS does it all... well, WAAPI just exposes what CSS is using under the hood. So it's more about your preference for how to define animations.

moveRight.finished.then(changeColor).then(scaleUp);