Filter by tag

Workshop "Second Brain without the chaos: build your own personal system for work, study, and personal projects" [ukr]

Create your own AI Second Brain — a personalized system that will help you organize information that’s usually scattered across notes, chats, documents, and to-do lists. During the workshop, you’ll build your first working version of the system step by step, which you’ll be able to use right after the session. Later on, you can scale it up and adapt it to your own work style. Together, we’ll set up key areas for your daily work: • Inbox — ideas, thoughts, and quick notes; • Work — tasks, meetings, follow-ups, and decisions; • Learning — books, courses, articles, and notes; • Personal Projects — personal projects and goals; • Decisions — analyzing options and making decisions; • Weekly Review — weekly review, reflection, and planning. Technical Requirements: • The workshop will be held in Claude; a Pro subscription is required • Prerequisites: Claude, Claude Code • The workshop will run on macOS, Linux, and Windows Bring your notes, tasks, ideas, or plans with you — by the end of the workshop, they’ll form the foundation of your personal AI system.

Ihor Zakutynskyi

(CTO at Universe),
AI fwdays’26
From Concept to Production with Claude and Guinness, or How AI Brought the Fun Back to Development [ukr]

When you build a product yourself alongside an AI agent, the code is no longer the bottleneck. The agent writes code quickly but makes mistakes with confidence: it cites laws that don’t exist or invents founders for the “About Us” page. I’ll share how I went from an idea in a bar to Jurly—a live, two-sided legal marketplace with AI-powered insights for clients and a workspace for lawyers—and what I had to build around the agent to make its “done” status trustworthy. Let’s break it down: - How one person at Claude Code takes a product from concept to launch: specs, TDD, dev reviews, AGENTS.md, and personal skills for verifying specs and code. - AI harness - Hallucinations in the product: a nonexistent law, a real article with fictional content, and a “pure hallucination” that even the automated check missed; how RAG, code-based citation verification, a critic, and a golden set reduce the risk. - The cost of this approach: accountability without a team, PII and security, the agent’s error log—and what worked and what didn’t. Key takeaway: An AI system is only as reliable as the checks surrounding it. An engineer’s role is shifting from writing code to designing these checks—from software engineer to product engineer.

Ilya Litvinov

(AI-Native Software Engineer(xEngineer) at Wix),
AI fwdays’26
The LLM Proposes. The Logic Decides. Neurosymbolic agents, higher-order logic, and the AI we almost forgot [ukr]

A language model is fluent, and sometimes it is wrong and sure. In a chat that costs one bad answer. In an agent with a memory it costs more: the agent stores the mistake, reasons from it, and repeats it tomorrow. Retrieval cannot tell which of two contradictory notes is right, and a second model asked to judge only predicts a plausible verdict. The fix is not new. Before deep learning, expert systems such as MYCIN and XCON kept knowledge as rules, applied them the same way every time, and answered "why?" and "how?". They failed at one thing: getting knowledge in, because every rule was typed by hand. LLMs are very good at exactly that. Neurosymbolic AI puts the two halves back together. The talk follows that reunion through one running example: an assistant whose LLM "remembers" a meeting in Berlin while its calendar has the same person in Lisbon at the same hour. We cover deduction, induction and abduction, and why LLMs are good at the last; reasoning over a knowledge graph with Prolog and Datalog; and why higher-order logic programming (λProlog) fits agents well, with types that reject malformed LLM output, relations as values, scoped what-if assumptions, rules about rules, and proofs that a small kernel can check. We end with a working agent whose LLM writes λProlog behind six guards, and with honest numbers on what the logic layer catches and what it cannot. For AI and agent engineers who know Python and LLMs. No background in logic or mathematics is assumed.

Volodymyr Pavlyshyn

(Senior Staff Engineer at Affinidi),
AI fwdays’26
Gotta remember ’em all: how to make your AI as smart as you[ukr]

An AI agent knows only what you show it — and it won’t suggest a solution you don’t know exists. On top of that, it forgets everything between chats. This talk explains what knowledge a human needs so the agent can work at full power, and how to build memory for it: from local files to shared memory via an MCP server. You’ll learn: — why agents miss obvious solutions and how to fix it — the memory bank pattern and a ready-to-use file structure — the levels of agent memory: chats, local files, Obsidian, git, MCP memory server — practical rules for keeping agent memory up to date

Hanna Likhtman

(Solution Architect at Geniusee),
AI fwdays’26
Building Successful Software Factories [ukr]

Software engineering is moving from agents that help write code to autonomous systems that take an approved requirement, write the code and verify the result with little human supervision: software factories. The approach is new, yet OpenAI, Anthropic, Stripe, Uber and others have already described theirs publicly. Each company tells its own story, but the same principles run through them: what a factory may build, how it proves the result is correct, how far its agents can be trusted, and how it keeps paying off. This talk walks through these principles and why each one is needed, drawing on those public write-ups and on the factories I build at Dev AI Consulting. The measure of success throughout: a factory whose “done” you can trust.

Vyacheslav Koldovskyy

(Founder at Dev AI Consulting),
AI fwdays’26
AI agent anti-patterns: how to burn a pile of tokens and get nothing [ukr]

Why do some teams speed up with the same AI tools while others drown in slop? We'll go through common anti-patterns of working with AI agents in development, from "generate everything at once" to blind trust in the output, what they lead to in practice, and what to do instead.

Kyrylo Sulimovskyi

(Head of Development at GameInspire),
AI fwdays’26
Building a profitable SaaS without microservices [ukr]

Vsevolod will share how he managed to build a profitable B2B SaaS without investments, which is used by top scientific publishers and grant agencies. What decisions were correct and helped to build everything in conditions of limited resources? What decisions were wrong? He will also talk about how to best organize teamwork in such conditions and what microservices have to do with it.

Vsevolod Solovyov

(prophy.ai),
CTO fwdays'25 conference
Observability with Elasticsearch: Best Practices for High-Load Platform [ukr]

The session covers architectural strategies that keep Elasticsearch stable under heavy load: proper index and shard design, ILM policies, persistent queues in Logstash, metrics downsampling, and self-monitoring of the observability stack. Insights are drawn from operating platforms that handle terabytes of logs and millions of events per day.

Anton Pryhodko

(EPAM, Systems Architect),
Highload fwdays'25 conference
Database isolation: how we deal with hundreds of direct connections to the database [ukr]

What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed. In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.

Mykhailo Kratiuk

(Backend Software Engineer at Solidgate),
Highload fwdays'25 conference
Rebranding for Growth [ukr, online]

Since there is no single formula for rebranding, this presentation will explore best practices for aligning business strategy and communication to achieve business goals. What is the role of rebranding in business strategy? When and why is rebranding necessary? What problems does rebranding solve, and what does it not address?

Anna Velykoivanenko

(Brand & GTM strategy, corporate communications, employer brand at DataArt),
Fwdays IT Summit
Sign in
Or by mail
Sign in
Or by mail
Register with email
Register with email
Forgot password?