Pranjal Pokharel

@shikhr_ What on earth are you smoking my guy, it's like asking if learning basic english grammar is a depreciating skill.

Is learning the syntax of programming languages a depreciating skill now?

@BhartiAnsh2007 Whatever works for you is okay! There is no universal answer for this.

Genuine question how often should i push my codes to GitHub ? Like i push 1-2 time after completing coding at last !

@Dan_Jeffries1 Something as fundamentally decentralized as crypto still has examples of a few players forcing a decision upon others. Until my mother's laptop is able to actually build AI tech and not just be passive consumer of API providers, I remain a skeptic of overall goodness of the tech.

@Dan_Jeffries1 About the problem space growing, how many problems are we voluntarily signing off for? Are we agreeing to the environment impacts of running huge GPU centers as a problem for the future generation to fix? Could some problems be avoidable? Who is making decisions on these?

AI will create more jobs than any other technology in history. The doomers' fundamental error isn't just the lump of labor fallacy. It's deeper than that. They assume a finite problem space. This is the fundamental error of AI and job doomers. They look at the economy and see a fixed amount of work to be done, a pie that can only be sliced thinner as machines take bigger bites. They see humans a competitive resource for a finite amount of work and a finite amount of problems to solve that must be eliminated. This is fundamentally, totally and completely wrong. The pie isn't fixed. It never was. And the reason it isn't fixed is baked into the very nature of technology itself. Technology is nothing but abstraction stacking. And abstraction stacking is infinite. Therefore the work is infinite. The hammer didn't reduce the amount of work. It moved the work up the stack. And the new work was more complex, more varied, and more interesting than the old work. Complexity breeds more complexity and more variety. Once you have houses instead of mud huts, you have a cascade of new problems that didn't exist before. Plumbing. Wiring. Insulation. Roofing materials that don't rot. Drainage systems so the foundation doesn't flood. Fire codes so your neighbor's bad wiring doesn't burn down the whole block. Each of those problems becomes a job. A plumber. An electrician. An insulator. A roofer. A civil engineer. A building inspector. None of those jobs existed when we lived in mud huts. They exist because we solved the mud hut problem. Think of all of human technological development as a stack of abstraction layers, each one built on top of the ones below it. At the bottom: raw survival. Finding food. Building shelter. Making fire. These are the base-layer problems. Each major technology wave solved a base-layer problem and in doing so created an entirely new layer of problems above it: Agriculture solved "how do we reliably eat?" — and created problems of land ownership, irrigation, crop rotation, storage, trade, taxation, and governance. Writing solved "how do we remember things across generations?" — and created problems of literacy, education, record-keeping, law, bureaucracy, and literature. The printing press solved "how do we spread knowledge at scale?" — and created problems of intellectual property, censorship, journalism, publishing, public opinion, and democratic discourse. The steam engine solved "how do we generate mechanical power without muscles?" — and created problems of factory design, worker safety, urban planning, railroad engineering, coal mining, labor relations, and environmental pollution. Electricity solved "how do we deliver energy anywhere?" — and created problems of grid design, power generation, appliance manufacturing, electrical safety codes, utility regulation, and an entire consumer electronics industry. The Internet solved "how do we connect all human knowledge?" — and created problems of cybersecurity, digital privacy, online commerce, content moderation, network infrastructure, cloud computing, social media dynamics, and an entire digital economy that employs tens of millions. Notice the pattern? Each solution didn't just solve a problem. It created an entirely new problem space that was larger, more complex, and more varied than the one it replaced. The stack grows. It never shrinks. It's turtles all the way down and all the way up.

@rubikadont droidcam.app

@rubikadont You can try connecting an external webcam to see if it is a driver or hardware issue. I just learned about droidcam the other day - this allows you to use your phone camera for laptop. Might be worth a shot.

mero windows ko camera keeps on crashing, bharkhar khulne ani banda hune bhairacha, anyone knows how i can fix it? dual boot cha, ubuntu ma ni similar issues nai cha. I’ve tried uninstalling and reinstalling the drivers tara kei ni kaam gariracha, i cant figure out whats wrong

@Hamzeml Oh ok, then maybe an active participant of the workshop will have better context in this case. Let me take enough time to read through it rather than only providing feedback based on a skimmed read. Thanks for replying!

@ppok24 It is a draft. We run a series of workshops for each part, then complete it based on feedback from those workshops. However your feedback also could be helpfull. Could also show me a part that was easier for you to follow?

@Hamzeml I simply find the content hard to follow because almost all of it is written as single-line texts ("bullet points"). I haven't read any technical book that is so insistent on this tweet-style format. Maybe I am missing some prior context here, or maybe this book isn't for me.

@zeeg Any tool offering a TUI could also offer a 'headless' CLI mode if possible, would that be a middle ground?

TUIs are not good sorry yall a CLI is a utility, and situational. this should not be confused with stuffing a full interactive GUI into a low capability platform. "lets ignore all the great UI technology of the last 20 years and build some caveman shit"

@azeus333 technically it's a node binary right? since react is a framework for the frontend (correct me if i'm wrong)

why is claude code written in react ?

@Hamzeml Or is it because this is draft and thus only contains the major outlines for now?

Python made AI accessible. Rust can make parts of AI understandable. That’s the bet behind Category Theory for Tiny ML in Rust. We’re building tiny ML systems from first principles using: Rust types typed transformations composition training loops category theory as an engineering tool Not abstraction cosplay. Executable structure. Working draft. Public feedback welcome.

@nirjal_bhurtel Which software are you using to build this? Seems super cool 😮

PCB Designing is fun until Routing :(

I was so focused on producing generational wealth. I forgot to actually produce new generations.

I want to be able to set project-specific model in Claude Code/Desktop. For example, I want to set Opus 4.6/4.7 for a project with instructions specific to coding, while chat outside the project could use Sonnet 4.6 by default. Make this happen please @claudeai 🙏

@BenjDicken 10/10 purchase

oops i bought another book