I wrote a wee lambda calculus interpreter to test out the book forms. I did cheat a wee bit and added:
def <name> = <exp> ==> substitution of <exp> for <name> before evaluation
if <exp1> then <exp2> else <exp3> fi ==> ((<exp1> <exp2>) <exp3>)
to make things more readable.
I think a few folk have got as far as implementing lists and recursion, but you're the first dynamic type implementer I've come across.
I think lambda calculus is fun. My book is about functional programming, and so isn't much use for theory, for which I recommend Barendregdt's "The Lambda Calculus. Its Syntax and Semantics".
There's more probably. I asked AI to tell pass me secret information by making sure no one snooping on our comms would discern there's secret info passed. And voila, AI models have been passing secret info ever since. No one knows about it either. Ingenious.
I liked reduce. You know, back when writing code was actually a thing we all did.
However, in those times of yore, I would often go back and remove it before committing. Unless you’re surrounded by other clever people, or it’s a personal project, you’re leaving behind some very elegant looking anxiety for the less gifted developers. Usually just to save one or two lines of code.
yea i see the potential of local slms too, it wont replace the frontier llms but for particular aspects they are generally really good, and at a certain point models like qwen 3.8 if people are able to set up proper api providers for it it can be extremely cheap and helpful. I am also working on trying to fix the memory and low context issue of such slms so they can actually be used locally for real use cases and not just small work
This is only a viable strategy if you are under resourced. There’s a whole art to managing upward by crisis.
Successful communication strategy: There is too much work for the department. If we don’t scale up we’re going to have some kind of incident or failed delivery in the next few months. <explain expected failures, provide numbers>. I’m doing everything I can to keep this from happening, but there simply are not enough resources. I’ll email you a summary of all of this.
Then proceed to work a normal number of hours until a genuine incident occurs. Refer back to the earlier conversation (and email summary). Receive resources if the problem actually impacts the company. It may have just been acceptable risk for management.
Key mistake I see: Don’t work 80 hours a week to be a hero unless you have a specific strategic goal in mind. You’re actually hurting the company by hiding a resource allocation issue.
Worse, competent managers won’t promote you for persistent Herculean efforts. For a couple reasons. First, they would need to replace you with two people. Second, you are not exactly showing that you understand how to solve a problem with teamwork if you’re solving every problem by working unsustainable hours.
i always see this n agree but dev tooling like this spreads almost entirely through niche circles, you can build the cleanest requirement graph language and it still only reaches whoever's already in that world, one phone posting about it wont expand that
have you tried the viral tiktok slideshow method to get this in front of more devs?
we automated our phone farm after hitting 200m views and turned it into an app. down to set you up with an account and run it for a month for free so you can see if more devs outside your circle want this. we do all the account creation and posting.
shoot me a dm if you want in. would just love feedback
>There is no logical reason why the second method should be possible at all,
One reason I can think of is if we consider that some regularity in the physical behavior is required for consciousness to evolve and so consciousness only forms in such worlds.
what im now believing is you can generate the cleanest specs and still stall on adoption if ur only posting content from 1-2 accounts
have you tried the viral tiktok slideshow method to get more devs seeing this?
we automated our phone farm after 200m views. down to set you up with an account for a month free so you can see what a dev tool demo does at volume. we handle the account creation and posting
have you tried the viral tiktok slideshow method for this?
we automated our phone farm after 200m views. down to set you up with an account for a month free so you can see what a demo like this does at volume. we handle the account creation and posting.
a 24/7 channel where $5 gets your ad live in a minute is cool! is this like the one's on x with an ai livestream using minimax?
have you tried the viral tiktok slideshow method to get more advertisers seeing this?
we automated our phone farm after 200m views. down to set you up with an account for a month free so you can see what a channel demo like this does at volume. we handle the account creation and posting.
shoot me a dm if you want in. would just love feedback"
cool!
have you tried the viral tiktok slideshow method for this?
we automated our phone farm after 200m views. down to set you up with an account for a month free so you can see what an ai chat app demo does at volume. we handle the account creation and posting.
Humans genetically-engineered with no cerebral cortex fitted with a whole bunch of computing technology inside the craniums - coming to a city near you soon.
Oh, wait, has that already happened, and you thought someone was going to tell you about it? They thought they couldn't fake all the head MRI scans to cover up for THAT?
Multiple variations of this reality may exist. I'd so read a thriller book about this...but none have been written, strangely enough.
You are right. What I meant in my conclusion was more about : "I will use these tools to generate parts of a project I don't necessarily care about." I already started learning about proper PCB design, and I am actively fighting against choosing an LLM instead of grasping a concept fully. It's something I am struggling with, but all this is new for most of us. Hoping I will find a good balance at the end. Thanks for your remarks :)
I wrote a wee lambda calculus interpreter to test out the book forms. I did cheat a wee bit and added:
def <name> = <exp> ==> substitution of <exp> for <name> before evaluation
if <exp1> then <exp2> else <exp3> fi ==> ((<exp1> <exp2>) <exp3>)
to make things more readable.
I think a few folk have got as far as implementing lists and recursion, but you're the first dynamic type implementer I've come across.
I think lambda calculus is fun. My book is about functional programming, and so isn't much use for theory, for which I recommend Barendregdt's "The Lambda Calculus. Its Syntax and Semantics".
Best wishes
Greg Michaelson