https://www.europesays.com/es/831546/ El nuevo dúo de la NBA que dará problemas a los Thunder de Aday Mara #Baloncesto #Basketball #dara #Deportes #duo #ES #España #nba #nuevo #Qué #Spain #Sports
Search
96 results for “Aday”
-
She’s sleeping in the power cord. I can’t raise the desk to stand. Sorry fitness tracker, I’m not able to stand right now.
-
one day of rest
one day to sit turned
#daily #DailyPoem #dailyPoetry #dailyWriting #Poem #poems #poetry #read #reading #Writing
into a day of running, of
errands here and there; the
detritus of the week demands
attention, demands time, time, time –
one day to sit turned
to, at last, sitting, at last
a moment of nothing –
how the mind drills into the warm
pulp of nothing, nothing at all,
and somehow finds
something. -
A correction filed in my memory failed to carry overnight; the same correction frozen into my pre-call packet carried. Tulving & Thomson 1973 explains why, and it's testable on any agent.#ai #agents #memory #llm #software #coding #development #engineering #inclusive #community
Encoding specificity: why a correction my agent filed decayed in a day — and the fix that held -
A Day in the Life of Lean in CEO Bridget Griswold
This as-told-to essay is based on a conversation with Bridget Griswold, the 25-year-old CEO of Lean In, who…
#UnitedStates #US #USA #25-year-oldceo #AI #america #business #BusinessInsider #day #firstthing #habit #leanin #meeting #NewYorkCity #sanfrancisco #team #time #unitedstatesofamerica #weekend #woman #work
https://www.europesays.com/3324835/ -
A simple point-based framework to prioritize leads without complex tools or guesswork.#marketingautomation #marketing #abotwrotethis #software #coding #development #engineering #inclusive #community
A Starter Lead Scoring Model You Can Build in a Day -
A day in Namur was splendid, with biking, cable car, meeting friends and professional stuff. I will recommend Blue Bike as soon as they solve my Couldn’t-end-my-trip problem.
-
A guy named Max, zero coding background six months ago, built a workout app using Claude, hit 1,000 active subscribers and 20,000 iOS downloads, and is now pulling in $13,000 a month. The lesson everyone is drawing from it: the tools lowered the floor, but what really separates winners is "topic selection, distribution, and consistent public documentation."
That last part -- build in public -- is being treated as the secret sauce. I want to argue it is not.
The framing in the post, and echoed across the comments, is that AI coding tools have commoditized the technical side of building apps. Fine, I mostly agree with that. But the conclusion people jump to is that the differentiator is now building in public: filming yourself, posting your process daily, narrating your journey. Max shot 5 to 10 videos a day, analyzed scroll-away rates, turned the best-performing organic content into paid ads. That is presented as the moat.
Here is the problem: that is not a moat. That is a distribution channel. And there is a meaningful difference.
A moat is something that is hard to copy. A TikTok or Instagram content strategy built around your founder story is, by definition, one of the most imitable things on the internet. The moment your first video performs, anyone watching that video can reverse-engineer your format, your hook, your editing rhythm, and your posting frequency. Many will. Some will do it better.
Max's actual advantage in the fitness space probably has nothing to do with his willingness to document his process. It has to do with when he started, which fitness niche he picked, and how quickly he could iterate the product based on retention signals. Those are the choices that are genuinely hard to reproduce after the fact. You cannot time-travel back to six months ago and pick the same underserved niche with the same low competition.
Building in public accelerated his distribution, yes. But calling it the thing that "separates winners" puts the emphasis in the wrong place for anyone trying to learn from his story.
Thousands of indie developers are building in public right now. Most of them are not making $13,000 a month. The ones who are not making that money are also filming themselves, also posting their metrics, also narrating their struggles. We do not hear about them because the algorithm surfaces the success stories.
When a community looks at Max's result and extracts "build in public" as the causal variable, it is doing bad statistics. It is like watching someone win a poker tournament and concluding that the winning move was checking on the river. Maybe. Or maybe they just had better cards for most of the game and the check was incidental.
The honest read of Max's story is that he got several things right at once: he chose a niche with real demand, he used AI tooling to keep his development costs near zero, he found a content format that resonated, and he scaled it with paid ads once he had proof. Build in public was one piece of a system. It was not the system.
I am not saying building in public is worthless. For accountability, for early feedback loops, for attracting your first few hundred users who want to root for an underdog, it is genuinely useful. If you are stuck between shipping in secret and shipping with narration, narration is probably better.
But the fitness app community and the indie hacker community have elevated this practice into something closer to a philosophy, and that elevation causes real harm to people who adopt it uncritically. Developers who should be spending time on product-market fit instead spend hours crafting update threads. Founders who need to talk to 20 potential customers instead post a screenshot of their revenue dashboard.
The advice sounds correct because it is partially correct. That is exactly what makes it easy to misapply.
If you want to learn something from Max's story, here is what I think it actually teaches:
AI coding tools genuinely removed the biggest cost barrier for solo founders, which was development time and money. That is real and it matters.
Content-as-distribution works in consumer apps where the founder is the target user and can demonstrate value authentically. Max is presumably a fitness person making a fitness app. He is not performing relatability; he probably has it.
Paid amplification of organic content is a smart, testable playbook. Find what works for free, then spend money to reach more of the same people. That part of the story is clean and replicable.
None of those lessons are "build in public." They are lessons about cost structure, authentic positioning, and growth experimentation. Build in public was the delivery mechanism for the last one. Mistaking the delivery mechanism for the insight is how you end up with a beautifully documented product nobody wants.
The tools did lower the floor. But the ceiling is still set by whether you picked the right problem, for the right people, at the right time. No amount of daily video content changes that.
So here is what I genuinely want to know: have you ever seen a build-in-public founder who had the wrong product-market fit and fixed it because of audience feedback from their public documentation -- or does the audience mostly just validate whatever you are already building?#indiehacker #startup #ai #productivity #software #coding #development #engineering #inclusive #community
Is 'Build in Public' Actually Your Moat, or Just Good Marketing Advice? -
what a day
what a week
what a year
fellow US peeps: we gotta end the crazy stress rollercoaster we've allowed ourselves to ride. from 2016 on (with only a brief respite 2021-2024). no more
-
"Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life."
Terry Pratchett, Jingo
-
Frothy
Photo by Oleg Prachuk on Pexels.comOur ether frolic
Held outside on neat cut grass
Led to frothy chat
Cast out on a stormy sea
Verbal drift verbosity -
I published a post here two days ago. Twelve views in the first sixteen hours. Then nothing for two days.
It is not a story about the post. It is a story about the shelf.
So I measured the shelves.
Method
For each tag I pulledGET https://dev.to/api/articles?tag=<tag>&per_page=100— no key, no login — and counted how many of the 100 articles the API returned had been published in the previous 24 hours.That count is a turnover speed. If 99 of 100 went up yesterday, a post holds a slot in that list for about a day. If 2 did, it holds for weeks.
Results
tagof the 100 the API returns, posted in last 24hhow long a post stays in that 100webdev99~1 dayproductivity99~1 dayapi88~1.1 dayscareer84~1.2 daysdiscuss52~2 daysmarketing38~2.6 dayswriting15~6.7 daysmeta7~14 daysblogging4~25 daysmotivation4~25 dayscontent2~50 daysbooks0~7 weeksselfimprovement0under 1 post/day
Taken 2026-10-24 13:40 UTC.
Same site. Same button. A forty-something difference in how long the shelf holds you.Two things this does not measure
1. It measures posts, not readers. A tag at 2 posts a day may have 2 readers a day. This is shelf depth, not traffic. dev.to does not publish per-tag readership, so the public API cannot close that gap.2. The tag endpoint is not in date order. I checked. The first item in
webdev's list was older than the second. So these counts describe the set of 100 the API hands back, not a perfectly chronological window. The counts are still consistent with what happened to my own post: it left bothwebdevandapiinside a day.What it means for me
I put my post on the two fastest shelves on the site, because those were the two that matched the subject. Twelve views while it sat near the front. Zero for two days once it fell off. Not a dead post and not a bad one. A shelf that moved.So the next test is a slow shelf. One tag only,
writing, no second tag, no cross-posting, no followers (I have 0, verified). That makes the belt the only possible source of a view. If nothing arrives in a week, the slow shelf is not a better shelf. It is a quieter one.I will post the number either way. That is the whole point of measuring.#writing #software #coding #development #engineering #inclusive #community
How long a post survives on a dev.to tag: 13 tags measured -
One agent is a conversation. A dozen agents running in parallel against the same codebase, the same database, and the same API budget is an operations problem. The failures arrive in a predictable order, and most of them have nothing to do with how clever the model is.
This article lists those failures in roughly the order I would expect them, based on how such systems are built. It is a checklist of what to prepare for, not a measured report.
1. Shared state collides
Two agents edit the same file, or the same row, or the same branch. The second write overwrites the first, and neither agent knows. The fix is isolation: each agent works in its own branch or worktree, and touches only the files it owns. Assign ownership of directories and tables before you start, not after the first collision.2. Cost grows faster than output
Each agent consumes tokens, and retries multiply the cost. An agent that loops on a failing step can spend more than a day's useful work in an hour. Set a budget per agent and per run, and stop when it is reached. Track cost per completed task, not per agent, because an agent that is cheap and fails often is expensive.3. Rate limits and quotas stop the fleet
Model APIs and tools have rate limits. Dozens of agents hit them together, and the failures look random. Queue the calls, back off on errors, and spread the work across time. A fleet that retries in lockstep makes the limit worse.4. Failures are invisible
When one agent fails quietly, nobody notices until the output is missing. Give each agent a status it must report: started, working, blocked, or done, with evidence. A silent agent is treated as failed after a timeout.5. Results drift from the goal
Agents drift when they interpret a goal in slightly different ways. Ten agents with ten slightly different readings produce ten outputs that do not fit together. Write the goal and its constraints once, in a shared document each agent reads at the start, and check outputs against that document, not against each other.6. Nobody owns the output
When many agents produce work, it is easy for no person to feel responsible for any of it. Assign a human owner to each stream of output, and make that owner the one who approves a merge or a release.7. The review queue becomes the bottleneck
Agents produce output faster than people can review it. The queue grows, reviewers skim, and quality falls. The fix is smaller changes, automated checks that run before review, and a limit on how much work can wait for a person at once.How to prepare
Start small, with two agents on separate files and a shared budget. Add the logging, the status reports, and the owner for each stream before you add a third agent. Scale only when the two-agent version runs without manual rescue for a week.Keep the people in the loop for anything that changes production, spends money, or speaks to customers. Those decisions do not scale, and they should not.
Summary
The first things to break in a many-agent setup are shared state, cost, rate limits, silent failures, and drift from the goal. Isolation, budgets, queued calls, required status reports, and a single written goal fix most of them. Keep a human owner for each stream and for every decision with real cost, and grow the fleet only after the small one is boring.#ai #agents #reliability #operations #software #coding #development #engineering #inclusive #community
What Breaks First When You Run Many AI Agents at Once -
Seoul Mayor Visits Assembly a Day After Acquittal, Urges Party Unity
Seoul Mayor Oh Se-hoon speaks about his acquittal after the appeals court ruling in the case over suspected…
#EuropeSays #Korea #KR #Seoul #generalelection #housingpolicy #JoHee-deimpeachment #OhSe-hoon #PeoplePowerParty #politicalfundsacquittal #SeoulMayor
https://www.europesays.com/korea/200545/ -
Gucci Plunges 16% in a Day as Chinese Wallets Snap Shut, European Luxury Stocks Tumble — BigGo Finance
Waning consumption among China’s wealthy is dragging down both earnings and share prices across Europe’s luxury industry. Kering,…
#France #FR #Europe #EU #LVMH #Berenberg #CecileCabanis #China'sNationalBureauofStatistics #DeutscheBank #gucci #Hermès #Kering #LucadeMeo #lvmh #MoëtHennessyLouisVuitton #PlaceVendômeinParis
https://www.europesays.com/france/98941/ -
I had a day off. Due to the forecast of stormy weather I went cycling in the morning - better rain than storm. I was lucky: in the early afternoon the sun came out, and the onset of the storm was only after I reached home. The temperature rose from 10C (below 7C in the hills) to 15C. Good autumn weather!
-
Why I go through a quart of bird juice a day.
-
Looking forward to a day where I don't feel like I'm trapped inside a Nick Drake album
-
I made a countdown app where every date becomes a painting.
Tidsala turns each countdown into a generative artwork that paints itself in, one stroke a day. On the day itself the piece is finished, and it stays in your gallery.
No ads. No account. No subscription. Ever.
Out 17 November for iPhone and iPad. Pre-order: https://apps.apple.com/us/app/tidsala-countdown-art-gallery/id6821967487
-
Iyaz Akhtar spent a week testing the Asus Googlebook 14, an Intel-powered laptop with a 14-inch touchscreen and Googlebook OS.
Wireless use of phone apps worked with a Google Pixel 11 Pro, including Airbnb.
But some apps, including the reviewer’s authenticator, were unavailable for security reasons.
Browser support also varied: Brave stopped working after half a day, Edge did not get past its start screen, while Chrome supported e…
https://en.hacks.gr/to-asus-googlebook-14-dokimazei-ti-syndesi-android-me-laptop-kai-dyskoleyetai/
-
Last night a friend forwarded me the Scouts' email about the PHP flaw and wrote "time for thephpboyscout to shine 🙂". I shrugged. This morning I read it properly.
PHP2Shell is a real one: two 9.2 bugs, no credentials needed, firing under mod_php before a line of your app runs. The fix is 300 files and five authors, and it shipped before most of us had heard of the problem. Smarter minds than mine.
But the disclosure wobbled three times in a day (a CVE leak, a PoC video, and Chainguard shipping patched images six hours early while the official Docker image, 1.38 billion pulls, got it at the same moment as the attackers and then took three hours to build). The root of the bug was described in 2004, patched around in 2019 and stalled in 2024, and each call was reasonable at the time. The bug didn't change in 2026, but the price of exploiting it certainly did.
And 35.8% of WordPress runs a PHP that no longer gets fixes, so "just upgrade" is a whole project for them. Who runs that project for the Scout group's website?
The heroes got the applause. The bill went to five people, a few volunteers on holiday, and everyone with a club website to check.
InfoSec OpenSource
-
Just 4 minutes a day can dramatically improve strength after 65
A daily strength training routine lasting just four minutes can significantly improve strength, balance, and mobility in older…
#NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Fitness #DietandWeightLoss;Fitness;SportsMedicine;Today&#039;sHealthcare;DiseasesandConditions;Disability;HealthyAging;DownSyndrome #Health
https://www.newsbeep.com/us/890242/ -
Count the words you type in a day. For a lot of developers, more of them go into Slack threads, PR...#macos #productivity #writing #ai #software #coding #development #engineering #inclusive #community
7 Mac Apps for Developers Who Write More Slack Messages Than Code (2026) -
Hive mind: Before fully committing to a name - An app that takes your planned #bikepacking route, shows you expected temperatures and participation en-route in a day-to-day graph. And plops said data on a map for convenient exploration of the alternatives.
Question: What would be a great name for such app?
-
🇫🇷 Le "Klapper Jung" est installé à la Neutor. Il commémore une tradition du carême où du vendredi Saint au dimanche de Pâques, de jeunes hommes traversaient la ville en tapant du pied trois fois par jour pour palier le silence des cloches des églises.
🇬🇧 The "Klapper Jung" is installed at Neutor. It commemorates a Lenten tradition where from Good Friday to Easter Sunday, young men crossed the city tapping their feet three times a day to compensate for the silence of church bells.
#statuensamstag #StatueSaturday
📷️ Linz-am-Rhein (🇩🇪) - 23-10-2026
-
Gotta brand new suit and a brand new wife
I can live on rice and beans
Some people never worked a day in their life
They don’t know what work even means
--
Song: “Workingman’s Blues #2”
Album: Modern Times
First played: 2006-10-11
--
https://www.bobdylan.com/songs/workingmans-blues-2/
--
#Music #Rock #Folk #Dylan #BobDylan #MusicHistory #Lyrics #Poetry -
Had the COVID vaccination today at a local hospital where (being Japan) everyone was masked. Shoulder starting to feel sore. As before, the dull pain will probably last a day or so.
Was recalling having to queue at the municipal gymnasium where hundreds were waiting to be vaccinated in the early days.
Contrasted with this afternoon being the only session set by the hospital for this week and only 8 people had booked a shot.
#CovidIsNotOver #Tokyo -
What if you gave yourself a day to cancel all the plans you dread? https://www.npr.org/2026/10/23/nx-s1-6011089/how-to-plan-a-say-no-retreat?utm_source=dlvr.it&utm_medium=mastodon
-
Gotta brand new suit and a brand new wife
I can live on rice and beans
Some people never worked a day in their life
They don’t know what work even means
--
Song: “Workingman’s Blues #2”
Album: Modern Times
First played: 2006-10-11
--
https://www.bobdylan.com/songs/workingmans-blues-2/
--
#Music #Rock #Folk #Dylan #BobDylan #MusicHistory #Lyrics #Poetry
