Archive
Discover and discuss technology tools
Explore the Tiscuss archive by category or keyword, then jump into conversations around what matters most.
LiveComment: AI Plugin for "Who Is Hiring?" on Hacker News
LiveComment: Revolutionizing Hiring Insights on Hacker News LiveComment is a cutting edge AI plugin designed to enhance the utility of the "Who Is Hiring?" sect…
AI Job Replacement: The Risks of Over-Reliance on AI
The people deciding that AI can replace your job are also the ones least likely to understand what your job truly involves, according to Box founder Aaron Levie, who pointed to this as an example of “AI psychosis.” Indeed, ClickUp recently cut 22% of its workforce for AI agents, tech layoffs in 2026 are already nearly matching all of 2025, […]
Show HN: AI-Powered Remote Job Board
AI Powered Remote Job Board: Revolutionizing Job Searches The job market is experiencing a significant transformation with the advent of AI powered technologies…
AI-Powered Job Search: RemoteJobs.Place Launched on Hacker News
AI Powered Job Search: RemoteJobs.Place Launched on Hacker News In today’s rapidly evolving job market, finding the right remote position can be challenging. Th…
AI Tool Tracks Ghost Jobs After Tech Company Ghosting
AI Tool Tracks Elusive Job Offer Rejections After Unacknowledged Applicants In today's competitive job market, many job seekers experience frustration when they…
Billionaires Propose AI Job Loss Compensation
**This week: the billionaires who broke the economy want to pay you to shut up about it.** Last week, Elon Musk pinned a post to the top of his X profile: "Universal HIGH INCOME via checks issued by the Federal government is the best way to deal with unemployment caused by AI." Sam Altman wants to go bigger — "universal extreme wealth", paid in compute tokens. Amodei says UBI may be "part of the answer." Khosla says it's a necessary safety net. All of them, in unison. These are the guys who spent twenty years arguing that government should stay out of markets, that handouts breed dependency, that the individual should stand on their own. Musk literally ran a federal cost-cutting operation. And now they want the government to mail checks to every citizen. Why? Because they broke the thing, and they know it. The people building the tools that eat the jobs are pre-emptively offering to pay for the damage — on their terms, through their platforms, using their math. **A universal basic income paid by the people who automated your job is not a safety net. It's a leash.**
AI's Impact on Business: Speed vs. Smart Decision-Making
I’ve been thinking about this for a while, especially with all the discussions around AI replacing jobs. One thing that feels consistently misunderstood: AI doesn’t improve the quality of decisions by itself. It increases the speed at which existing decision logic operates. That has a simple consequence: Good systems become better. Weak systems fail faster. But there’s another layer that is often ignored. Right now, many companies are reacting to AI by reducing headcount. Some of that is rational: - there is real slack in certain roles - some work can already be automated or simplified In those cases, AI acts as a kind of cleanup mechanism. But this is where it gets more complex. If companies reduce people too quickly, they don’t just cut cost — they also remove: - domain knowledge - informal networks - context that is not documented anywhere This kind of knowledge is not easily replaced by AI. So you end up with a paradox: AI increases speed, but the organization loses the very knowledge needed to make good decisions at that speed. At the same time, layoffs are not always a signal of weak systems. Strong organizations can also reduce roles because they: - increase productivity per employee - reallocate work - shift toward new capabilities The difference is what happens next. Some organizations use AI to scale and create new opportunities. Others mainly use it to cut cost because they lack the structure to turn speed into growth. So instead of asking: “Will AI replace jobs?” A more relevant question might be: Is the organization structured in a way that can actually benefit from faster decision-making? Because if not, AI won’t make it smarter. It will just make it faster at being wrong.
AI Impact on Jobs: Freelancers and Marketers Share Experiences
So, I was scrolling through Linkedin and saw this post & felt really really bad for this dude.....so just wanted to take an opinion. Has your job been impacted by AI yet? I handle marketing at a saas brand and I believe since I keep myself updated with AI, my job is not at risk as of now, but who knows what could happen at any moment in this uncertain world🤷
Clera: AI Matching Candidates to Perfect Roles
An AI agent matching candidates to the right roles.
Snabbit Secures $56M as On-Demand Home Services Boom
Snabbit now processes over 40,000 daily jobs and has cut costs sharply as it expands across cities and services.
AI Optimists vs. Pessimists: Will AI Reduce Unemployment?
How does what Dario is saying that unemployment is going to 20% if AI is going to be used to solve our problems? AI is a tool for humans to point at problems and solve them. Making humans act less like machine. Good. Making humans afraid that they will lose their income source because of a machine. Bad. This doesn’t make logical sense. Do they not like humans and want to solve their problems? Unemployment is one of our biggest problems. And they are saying that AI can’t fix it? Also, universal job guantee polls higher than universal basic income. Most people like to work and provide value. They don’t like being exploited and living in fear that their livelihood will be erased. What am I missing here AI optimists? AI pessimist? Realists?
AI CEOs Discuss Universal Basic Income Timeline
In my oppinion it will take 10 or more years. Goverments are slow as hell. I work in a call center in Portugal and they work slow and are very disorganized. Even tho they already use ai. But ai needs to take our job first to have productivity so then they can give us the universal income. I work in a bank call center and I don't see ai taking my job already. Maybe it could but organizations work so slow
AI Agents: Identity, Not Memory, Was the Key to Stability
Everyone's building memory layers right now. Longer context, better embeddings, persistent state across sessions. I spent weeks on the same thing. But the failure mode that actually cost me the most debugging time had nothing to do with memory. Here's what it looked like: an agent would be technically correct - good reasoning, clean output - but operating from the wrong context entirely. Answering questions nobody asked. Taking actions outside its scope. Not hallucinating. Drifting. Like a competent person who walked into the wrong meeting and started contributing without realizing they're in the wrong room. I run 11 persistent agents locally. Each one is a domain specialist - its entire life is one thing. The mail agent's every session, every test, every bug fix is about routing messages. The standards auditor's whole existence is quality checks. They're not generic workers configured for a task. They've each accumulated dozens of sessions of operational history in their domain, and that history is what makes them good at their job. When they started drifting, my first instinct was what everyone's instinct is: better memory. More context. None of it helped. An agent with perfect recall of its last 50 sessions would still lose track of who it was in session 51. What actually fixed it I separated identity from memory entirely. Three files per agent: passport.json - who you are. Role, purpose, principles. Rarely changes. This is the anchor. local.json - what happened. Rolling session history, key learnings. Capped and trimmed when it fills up. observations.json - what you've noticed about the humans and agents you work with. Concrete stuff like "the git agent needs 2 retries on large diffs" or "quality audits overcorrect on technical claims." The agent writes these itself based on what actually happens. Identity loads first, then memory, then observations. That ordering matters. When the identity file loads first, the agent has a stable reference point before any history lands. The mail routing agent learned the sharpest version of this. When identity was ambiguous, it would route messages from the wrong sender. The fix wasn't better routing logic - it was: fail loud when identity is unclear. Wrong identity is worse than silence. The files alone weren't enough Three JSON files helped, but didn't scale past a few agents. What actually made 11 work is that none of them need to understand the full system. Hooks inject context automatically every session - project rules, branch instructions, current plan. One command reaches any agent. Memory auto-archives when it fills up. Plans keep work focused so agents don't carry their entire history in context. The system learned from failing. The agents communicate through a local email system - they send each other tasks, status updates, bug reports. One agent monitors all logs for errors. When it spots something, it emails the agent who owns that domain and wakes them up to investigate. The agents fix each other. The memory agent iterated three sessions to fix a single rollover boundary condition - each time it shipped, observed a new edge case, and improved. These aren't cold modules. They break, they help each other fix it, they get better. That's how the system got to where it is. You don't need 11 agents The 11 agents in my setup maintain the framework itself. That's the reference implementation. But u could start with one agent on a side project - just identity and memory, pick up where u left off tomorrow. Need a team? Add a backend agent, a frontend agent, a design researcher. Three agents, same pattern, same commands. Or scale to 30 for a bigger system. Each new agent is one command and the same structure. What this doesn't solve This all runs locally on one machine. I don't know whether identity drift looks the same in hosted environments. If u run stateless agents behind an API, the problem might not exist for you. Small project, small community, growing. The pattern itself is small enough to steal - three JSON files and a convention. But the system that keeps agents coherent at scale is where the real work went. pip install aipass and two commands to get a working agent. The .trinity/ directory is the identity layer. Has anyone else tried separating identity from memory in their agent setups? Curious whether the ordering matters in other architectures, or if it's just an artifact of how this system evolved.
AI's Productivity Boost: Layoffs or Worker Benefits?
I keep hearing that AI will make workers more productive. But the part I don’t understand is this: If one employee can now do the work of three people, why is the default outcome usually: * fire two people * keep the same workload * give the remaining person more pressure * send the savings upward Why isn’t the obvious outcome: * shorter work weeks * higher wages * lower prices * more time off * better services It feels like AI is being sold to the public as “everyone will be more productive,” but implemented by companies as “we need fewer humans.” Maybe I’m missing something, but productivity gains only feel like progress if normal people share in them. Otherwise it’s not really “*AI helping workers*.” It’s just automation being used as a layoff machine. **Do you think AI will actually improve life for workers, or will it mostly just increase profits while making jobs more insecure?**
Snabbit Aims for $400M Valuation in New Funding Round
Snabbit has scaled rapidly, crossing one million jobs in March, amid growing investor interest.