标签：#m

Разберёмся, к чему нас приведут нейросети и что будет дальше. Это хайп, пузырь или новая реальность? Взгляд разработчика и дорожная карта для входа в AI. Хочу провести небольшой анализ и понять, какие сценарии развития нейросетей могут быть и к чему мы можем подготовиться. Я разработчик, и последние пару лет моя лента — это бесконечный хайп вокруг AI. Но если отключить эмоции и включить холодный анализ, возникает ощущение дежавю. Давайте ненадолго погрузимся в историю. Прошлое. Что мы уже пережили Мы, поколение миллениалов и зумеров, стали свидетелями уникального явления: технологии начали сменять друг друга с огромной скоростью. Каждые два-три года появлялось что-то. Вспомним главные тренды: • Социальные сети (2007–2012) — пугали, что мы перестанем общаться вживую, а приватность умрёт навсегда. Стали рекламным рынком, появились SMM-щики и таргетологи. Кто не пошёл в digital — остался на обочине. • Big Data (2010–2015) — кричали «Большой брат следит за тобой», аналитиков заменят алгоритмы. Сегодня это стандартный слой систем, дата-инженеры — обычная роль. • Облака (2010–2018) — боялись, что данные украдут, а сисадмины вымрут как класс. Облака стали коммунальной услугой. DevOps и SRE — must-have, сисадмины просто переквалифицировались. • IoT (2014–2018) — пугали тем, что хакеры взломают ваш чайник, а вещи станут умнее людей. Технология ушла в промышленность, быт не перевернула. • 3D-печать (2012–2015) — паника «заводы закроются, каждый напечатает пистолет». Прижилась в прототипировании и стоматологии, пистолеты печатают только в новостях. • VR (2016) — боялись, что люди уйдут в виртуал и перестанут различать реальность. Стало игрушкой для геймеров и тренажёром для пилотов. • Метавселенные (2021–2023) — говорили, что жизнь окончательно переедет в цифру, а без аватара на работу не выйдешь. Хайп прошел. • Блокчейн (2015–2018) — страх, что банки исчезнут, а юристы и нотариусы станут не нужны. Web3-революция не случилась, но разработчики были на вес золота. • Крипта (2017

Bridging the Gap: Navigating the Chasm Between Academic Coding and Real-World Software Development The transition from academic coding to professional software development is fraught with challenges, particularly when it comes to navigating and debugging large, unfamiliar codebases. This gap, often overlooked in educational curricula, leaves new developers ill-prepared for the complexities of real-world projects. Below, we dissect the technical mechanisms involved in codebase navigation and debugging, their constraints, and the resulting instabilities, while reflecting on the disconnect between academic training and industry expectations. Mechanisms of Codebase Navigation and Debugging The process of understanding and working within a large codebase involves several interconnected mechanisms. Each plays a critical role in a developer's ability to efficiently and accurately contribute to a project. Code Navigation : Involves traversing a codebase using tools like "go to definition" to map code structure and dependencies. This mechanism relies on the developer's ability to interpret relationships between files and functions. Impact : Efficient navigation reduces time spent understanding the codebase. Internal Process : Iterative exploration of code paths. Observable Effect : Reduced time to locate relevant code segments. Code Comprehension : Analyzing existing code to infer purpose, logic, and side effects. Requires pattern recognition and logical deduction. Impact : Accurate comprehension minimizes unintended modifications. Internal Process : Mental modeling of code behavior. Observable Effect : Correct identification of code functionality. Debugging : Identifying and resolving bugs while minimizing collateral damage. Relies on isolating root causes and understanding dependencies. Impact : Effective debugging prevents regressions. Internal Process : Hypothesis testing and validation. Observable Effect : Bug resolution without introducing new issues. Documentation Ana

Google has expanded Gemini Omni into Google Vids for end-to-end AI video generation and editing. The update lets users create clips from text and image references, then make targeted changes to existing footage through a step-by-step conversation. Rather than rebuilding a video after each revision, users can describe an adjustment, supply additional media where useful and refine the result in place. The central development is Omni's use of multimodal and real-world understanding in a Vids workflow. According to Google DeepMind's Gemini Omni overview , the model can work from arbitrary media, including images, text, video and audio, and apply reference-to-video capabilities grounded in world knowledge and physics-like reasoning. In Google Vids, that foundation is intended to make generated and edited scenes more coherent in composition, context and visual behavior. For teams that already use Vids to communicate ideas, training material or internal updates, the change moves AI assistance beyond first-draft generation. It introduces a conversational editing layer that can alter a chosen part of a video while preserving the broader scene and workflow. What Gemini Omni changes in Google Vids Gemini Omni supports both video creation and revision. A creator can begin with a prompt or image reference to generate a clip, or bring in existing footage and specify what should change. Google describes examples such as changing color grading or lighting, replacing backgrounds and removing background elements. This distinction matters because prompt-to-video and video editing have different practical constraints. Generating a new clip can be useful when no footage exists. Editing existing material is more relevant when a team wants to retain an established subject, scene or message while changing selected details. Omni's reference handling is designed to connect those modes rather than treating each request as an isolated output. Workflow How Gemini Omni is used in Vids Supported

The mobile and tablet ports of the remastered puzzle game include a free trial.

A short case study from my "building and testing MCP agents" series — it stands on its own, but the method behind it is laid out in https://dev.to/langensjonathan/the-parameters-that-actually-matter-when-youre-tuning-an-ai-agent-2agd . TL;DR: I benchmarked two agents that are identical except for one thing — how many MCP servers they're connected to — on the exact same question. Both got the right answer, both called the same single tool. The one with more MCP servers attached still cost 28% more per question , purely from the extra tool schemas the model has to be told about on every single call, whether it uses them or not. The setup MAVERIK is my open-source MCP test bench: define a suite of questions with pass criteria, run it against one or more agent configurations, and compare the results on hard numbers. This post is one deliberately tiny experiment with it: change exactly one thing about an agent, hold everything else fixed, and see what the numbers attribute to that one change. I have a small "GitHub summarizer" agent: one system prompt, one job — answer questions about my GitHub account by calling the GitHub MCP server . I duplicated its configuration (MAVERIK supports this directly — same model, same prompt, same everything) and changed one field on the copy: the set of attached MCP servers, adding deepwiki , microsoft-learn , and context7 . Neither agent needs any of those three for the question I was about to ask; they were attached because that's what the "kitchen sink" version of this agent had accumulated over a few sessions of general-purpose use. Then I wrote the simplest possible test suite — one question: "How many repositories do I have?" with a contains criterion checking the answer includes the correct count. No judge model, no subjectivity — it either says the right number or it doesn't. I ran both agents against it, 2 repetitions each, same model ( claude-haiku ) for both, and pulled up MAVERIK's Agent Comparison report. Agent A — github on

I built a small Flask example that turns voicemail into a routing workflow. Code: https://github.com/team-telnyx/telnyx-code-examples/tree/main/voicemail-smart-router-python The app accepts either: a voicemail transcript an uploaded voicemail audio file For audio, it transcribes the voicemail first. Then it uses Telnyx AI Inference to classify the message and decide where it should go. Categories The app classifies voicemails into: urgent billing support sales spam routine Each category maps to a route: urgent -> Slack alert billing -> email support -> ticket queue sales -> CRM lead spam -> blocklist + archive routine -> daily digest Run it git clone https://github.com/team-telnyx/telnyx-code-examples.git cd telnyx-code-examples/voicemail-smart-router-python cp .env.example .env pip install -r requirements.txt python app.py Configure .env : TELNYX_API_KEY=your_telnyx_api_key AI_MODEL=zai-org/GLM-5.2 FALLBACK_MODEL=meta-llama/Llama-3.3-70B-Instruct HOST=127.0.0.1 Optional Slack webhook for urgent messages: SLACK_WEBHOOK=https://hooks.slack.com/... Classify a transcript curl -X POST http://localhost:5000/voicemails/transcript \ -H "Content-Type: application/json" \ -d '{ "transcript": "This is an emergency. Our production system is down and we need help immediately.", "caller_number": "+17177247292" }' Example response: { "category" : "urgent" , "confidence" : 1.0 , "priority" : "high" , "reason" : "The caller reports a production system outage requiring immediate attention." , "suggested_action" : "Escalate immediately to the on-call engineering team." , "route" : "slack" , "routed_to" : "#oncall-alerts" , "routing_status" : "delivered" } Process voicemail audio curl -X POST http://localhost:5000/voicemails/process \ -F "file=@voicemail.wav" \ -F "caller_number=+17177247292" For audio, the app calls: POST /v2/ai/audio/transcriptions using: distil-whisper/distil-large-v2 Then it calls: POST /v2/ai/chat/completions to classify the transcript. Routes included POST /voic

Google's next foldable doesn't look all that different, save for the camera bar.

submitted by /u/farnoy [link] [留言]

Buying multiple lamps for different rooms can get expensive. Govee’s rechargeable Table Lamp Classic gives you one lamp you can use throughout your home instead of getting one for every room, and right now it’s down to $59 ($21 off) at Amazon. That’s just $4 shy of the all-time low set during Prime Day, and […]

Gemini Robotics 2 includes three models, but only one is publicly available right now.

Here are the best back-to-school deals under $200 on comfy, ergonomic chairs for all-nighters and cram sessions

Spotify says the new feature is designed to let users add personal captions to their favorite songs, such as noting why a track was added to a playlist or when they first discovered it

Despite the slump, Apple and Samsung have both seen their market share go up.

"Dogfighting in space doesn’t quite have the drama of an aerial dogfight."

Learn how I modernized an old codebase of mine using stacked sessions and pull requests in the GitHub Copilot app. The post Stacked sessions and pull requests in the GitHub Copilot app appeared first on The GitHub Blog .

As of this week in Montana, any biotech company with an experimental drug has a clear path to selling it to consumers. Companies whose drugs have been through preliminary testing—sometimes in as few as 10 healthy people—can pay $12,500 to apply to a newly established review board for approval. Once its treatment is rubber-stamped, the…

ABC filed its formal opposition to the Federal Communications Commission's effort to force it to submit to an early renewal of its broadcast station licenses, calling it an effort to chill the speech of broadcasters across the country. In a new filing with the FCC, ABC charges that the agency's willingness to pursue the early […]

The temporary exemption from federal safety standards will let Amazon’s Zoox launch a real, paid robotaxi service in Las Vegas.

The company is also removing some of its own AI-writing features.

The two Chrome updates in June patched more bugs than the 23 updates before them. Now, Google is ramping up its patching schedule thanks to AI-assisted vulnerability discovery.