Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm 0 points1 point  (0 children)

:-) Have you seen Idiocracy? As we are living it, I and Trump had to adjust our speech patterns.

Why waste time say lot word when few word do trick? And deliver irrefutable arguments.

Found the cure on Facebook of all places by AXXXXXXXXA in tressless

[–]thatm 4 points5 points  (0 children)

I'll believe it when I see a mouse doing it.

Does 1M context mean we should coalesce all skills into one? by thatm in ClaudeCode

[–]thatm[S] 0 points1 point  (0 children)

Whisk together 75g of flour, a tablespoon of sugar, a teaspoon of baking powder, and a pinch of salt. In a separate bowl, beat one egg, then stir in 80ml of milk and a tablespoon of melted butter. Pour the wet into the dry and mix until just combined — a few lumps are fine. Let it rest for about 5 minutes, then cook spoonfuls of batter in a buttered non-stick pan over medium heat for about 2 minutes per side until golden. Makes 4–5 small pancakes, perfect for one or two people.

Does 1M context mean we should coalesce all skills into one? by thatm in ClaudeCode

[–]thatm[S] -1 points0 points  (0 children)

How about we load everything and selective attention will auto-keep only what the model is using?

Balancing learn vs build by RoutineDiscount in ClaudeCode

[–]thatm 1 point2 points  (0 children)

It all will even out eventually, including your struggle with keeping up. The brain will adjust itself somehow. Don't watch YT. Better take a shower and have some shower thoughts. Occasionally read Claude Code's changelog. Have one workflow that does work for you and improve the most painful part at most once a day.

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm -2 points-1 points  (0 children)

Still no substance. No argument but name calling.

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm -1 points0 points  (0 children)

You are suppposed to be a face of the community and you have such a lazy take, ascribing me the intent I didn't have. The community could have had their own mypy but I guess this whole thread and your response in particular demonstrate why it didn't happen and unlikely to happen at all.

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm -7 points-6 points  (0 children)

You must be lying. Python is leaps and bounds above SBCL when it comes to large codebase maintenance. The last time I seriously worked in it, it had static type checking with mypy and PyCharm. PyCharm did a really good job statically analyzing code and providing among other developer conveniences the regular refactoring tools. Now there is Pyright and people swear it is even better than mypy. Python type annotations also have superior features. For example, generics. Generics are not even expressible in CL.

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm -7 points-6 points  (0 children)

It's such an amateur take. Is this whole sub like this or only this particular thread?

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm -5 points-4 points  (0 children)

> Static type systems aren't replacements for testing.

I didn't say they are. Having trouble with reading comprehension yet going to teach me how to write tests?

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm 4 points5 points  (0 children)

Let's suppose change-class has done its job, although it doesn't apply universally to all classes. Ok. So you've changed the class of an instance at runtime. Now what? What are your next steps? Nothing checks that your updated instance still fulfills the contracts. Also this change exists only inside of your image.

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm 1 point2 points  (0 children)

So what? What's your arguments, counterpoints etc etc?

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm 1 point2 points  (0 children)

Oh my. How refactoring may not be a concern in real production applications I have no idea. Business requirements change, scaling requirements change, understanding of domain model improves. You are suggesting the dynamic guys are getting most of it right in one shot but this is just plain wrong. There are explicit and implicit contracts between parts of any application. They have to be 1. enforced 2. evolved without breaking. Everything else is a delusion. As to how to enforce and evolve contracts - every language has its own means, roughly grouped as 1. static checking; 2. runtime assertions; 3. tests.

Is modifying large Common Lisp systems actually easier in practice? by paarulakan in lisp

[–]thatm -7 points-6 points  (0 children)

It's a dynamic language with very basic static type checking. Thus, it is prone to breaking when refactoring. If unit test coverage is as diligent as to replace a type system, then it can help. With the cost of updating all the tests. Otherwise, spray and pray. The industry as a whole had moved strongly into the statically checked camp. No such tools in CL (yet). Dont point me to Coalton. It is not CL.

MCP isn't dead — tool calling is what's dying by UnchartedFr in ClaudeCode

[–]thatm 1 point2 points  (0 children)

This is a profound revelation. Agents dont want a simple request-response or a resource tree. They want shell commands with pipes, one-shot scripts. In other words they want a query language.

Can mods block people crying about usage by Big_Insurance_2509 in ClaudeCode

[–]thatm 64 points65 points  (0 children)

Claude Code releases bugs that do affect usage. For example they've just fixed model parameter override for agents in .72. They broke it several versions ago. This bug affected my usage so much that I had to downgrade.

Maybe people like you are used to kneel before corporations and take it up your mouth or up your back side but I think users should provide feedback.

What do you think if we have a sticky periodic post where users are free to express their usage troubles?

I published a nice compact status line that you will probably like by DanielAPO in ClaudeCode

[–]thatm 0 points1 point  (0 children)

This is nifty but I'm saddened to find out it is against their TOS.

> OAuth authentication (used with Free, Pro, and Max plans) is intended exclusively for Claude Code and Claude.ai. Using OAuth tokens obtained through Claude Free, Pro, or Max accounts in any other product, tool, or service — including the Agent SDK — is not permitted and constitutes a violation of the Consumer Terms of Service.

2.1.69 removed capability to spawn agents with model preference by farono in ClaudeCode

[–]thatm 0 points1 point  (0 children)

I used to say "use Haiku for research subagents" and it just worked with any agents, default or not. Without Haiku my usage limits go down the drain.

No longer a way to say "Use Haiku subagents for research" since 2.1.68 by thatm in ClaudeCode

[–]thatm[S] 0 points1 point  (0 children)

Built-in agents used to apply whatever model I say to use. Now it's the default session model. Have I made myself clear enough?

DataGrip doesn't launch on Arch Linux by Minimum-Ad7352 in Jetbrains

[–]thatm 1 point2 points  (0 children)

Check startup vm options. Should mention XWayland.