Nylige søk

Ingen søk nylig

Alternativer for søk

Ikke tilgjengelig på snabelen.no.
snabelen.no er en av mange uavhengige Mastodon-servere du kan bruke for å delta i det desentraliserte sosiale nettet.
Ein norsk heimstad for den desentraliserte mikroblogge-plattformen.

Administrert av:

Serverstatistikk:

367
aktive brukere

snabelen.no: OmStatusProfilkatalogPersonvernregler

Mastodon: OmLast ned appenHurtigtasterVis kildekodev4.4.8

#softwaredevelopment

37 innlegg35 deltakere2 innlegg i dag
Miguel Afonso Caetano<p>Spot on!! Like most technologies, AI is "just" another accelerator. </p><p>"To recap my argument, yes, AI can accelerate our output, but it won’t liberate us. AI is accelerating everyone’s output. Not just you and your colleagues’ output. It’s accelerating the output from your competition, both nationally and internationally. The world has sped up.</p><p>In a state of accelerated innovation, we need AI tools just to keep our head above water. If your company can’t push out new and better products, they’ll be eclipsed by companies that can. If CEOs thin their number of employees, thinking it will yield more profits, that short-term thinking commits the fallacy of assuming that the goal posts are staying in the same position.</p><p>The release windows in which you must push out new software are shortening and becoming more frequent. Expectations about quality are increasing. You have to spend more time in research and development to ensure the competitor’s next release doesn’t put you out of business. This is why company layoffs might be a strategically poor decision: in an attempt to capture short-term profits, they shed the human validation resources needed to compete in the long-term, accelerated race.<br>(...)<br>We’re all accelerating and reeling from its effects. The idea of AI as liberation — liberation from all the tedious and time-consuming tasks you have to do — sounds much more appealing. But that liberation is a false narrative. AI isn’t liberating us. It’s speeding up the race. And we’re out of breath."</p><p><a href="https://idratherbewriting.com/blog/ai-narrative-from-liberation-to-acceleration" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">idratherbewriting.com/blog/ai-</span><span class="invisible">narrative-from-liberation-to-acceleration</span></a></p><p><a href="https://tldr.nettime.org/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://tldr.nettime.org/tags/GenerativeAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenerativeAI</span></a> <a href="https://tldr.nettime.org/tags/Automation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Automation</span></a> <a href="https://tldr.nettime.org/tags/Productivity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Productivity</span></a> <a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalWriting</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDocumentation</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDevelopment</span></a></p>
Mark Levison

🤖 AI code generators promise speed, but what about the hidden costs? From
technical debt to team dynamics, there's more to consider.
If AI integration feels overwhelming, you're not alone. Understanding the full
picture helps reduce uncertainty.
agilepainrelief.com/blog/the-r

#AI [agilealliance.social/tags/AI] #SoftwareDevelopment
[agilealliance.social/tags/Soft] #TechReality
[agilealliance.social/tags/Tech]

Miguel Afonso Caetano

"Today, AIs can do some things. Eventually, they may be able to do everything. Forecasts generally project forward from what AI can do today, estimating how long it will take to fill in the gaps.

We often underestimate the size of those gaps. Some of this is just “out of sight, out of mind” (or, if you prefer, “availability bias”) – it’s easier to notice the things AIs are doing than the things they aren’t. But also, AIs have important gaps in fuzzy high-level skills that we don’t have great vocabulary for. These skills are applied diffusely across our workday instead of showing up as a crisp bullet on a todo list, making it easier to forget they exist.

In today’s post, I’m going to discuss some of the capabilities that AIs will need to acquire in order to progress from carrying out tasks to automating entire projects and jobs. I’ll also argue against some specific ideas that are sometimes presented in arguments for “short timelines” (AGI arriving within the next few years).

I’ll mostly be talking about software engineering. Automated coding is central to many scenarios of rapid AI progress, and it’s the domain I know best. But the principles I’m going to discuss apply to many fields.

We often analyze AI’s aptitude for a job by enumerating the tasks involved in that job. However, the whole is more than the sum of its parts. Breaking up a job (or a large project) into tasks is a useful mental scaffold, but it’s also an oversimplified way of thinking about things. The boundaries between tasks are not clean; information bleeds across."

secondthoughts.ai/p/a-project-

Second Thoughts · A Project Is Not a Bundle of TasksAv Steve Newman
#AI#GenerativeAI#LLMs
Sebastian Hans

New blog post: Unit testing vs. integration testing

“Unit tests and integration tests are often compared – and usually presented as opposites. In this post, I will examine these two types of tests from a different point of view and show how this perspective can help us write better tests.”

sebastian-hans.de/blog/unit-te

sebastian-hans.deUnit testing vs. integration testing — Sebastian's blogSebastian's blog – Unit testing vs. integration testing
#softwareengineering#softwaredevelopment#testing
InfoQ

As #AI moves from proof-of-concept to production, the real challenges emerge - not just in model performance, but in architecture, process & accountability.

Developers are building delivery pipelines where AI learns, adapts & interacts with human judgment. From MLOps to team culture, this shift is redefining software engineering.

📘 Explore the journey in this #InfoQ eMag!

⬇️ Download your **FREE** copy now: bit.ly/47lKE1P

#MLOps#LLMs#AIagents
Clément Robert

Introducing runtime_introspect v0.2.0 !

github.com/neutrinoceros/runti

This versions introduces high level, portable APIs like

- FeatureSet.supports("free-threading")
- FeatureSet.supports("JIT")
- FeatureSet.supports("py-limited-api")

making it possible to inspect availability for specific features at runtime with *very* little code (turns out solving this problem in the general case is complicated enough that I only want to do it once).

For instance

from runtime_introspect import runtime_feature_set
fs = runtime_feature_set()
if fs.supports("free-threading"):
... # cool multi-threading stuff
else:
... # less cool, single threading stuff

every non-EOL version of #CPython (including unstable ones, #Python315) are supported.

What's Changed This version introduces highlevel APIs and adds support for CPython 3.15 Added TST: add CPython 3.15 to test matrix by @neutrinoceros in #32 FEAT: add high level APIs by @neutrinoce...
GitHubRelease v0.2.0 · neutrinoceros/runtime-introspectWhat's Changed This version introduces highlevel APIs and adds support for CPython 3.15 Added TST: add CPython 3.15 to test matrix by @neutrinoceros in #32 FEAT: add high level APIs by @neutrinoce...
#Python#softwaredevelopment#opensourcesoftware
Christoffer S.

I really enjoy and love development using nvim + tmux.

Normally I develop on my desktop. But then I step away from it... but realize I want to do some lightweight development... ssh, tmux a... and boom, back into dev environment.

It's just... so ... fluid, and flawless. Love it.

#tmux#nvim#Development
PopulærtTidslinjer
Om