Neural Networks Without Magic: 80-Year History, Business Applications, and Why They Will Not Replace Experts Overnight
Vasily Ryazanov, candidate of physical and mathematical sciences and head of the Data Science team at Twinby, sat down with journalist Alexander Shulepov to separate hype from practical value in neural networks. The conversation covers the technology’s long history, how contemporary language models operate, real business deployments, and the persistent need for human expertise.
From family history to Data Science: why neural networks entered his life long before ChatGPT
Ryazanov explains that his path began in the 1970s when his father worked on artificial intelligence and pattern recognition under academician Zhuravlev at the Academy of Sciences after finishing graduate studies around 1977. Early networks processed tables of only hundreds or thousands of rows on computers that ran for hours. By the 2000s the workflow had become clearer: load tabular data, train an algorithm, and obtain results, often written in C++.
He stresses that neural networks are not 10–20 years old but approximately 80 years old. Interest has risen and fallen in waves, with renewed attention around 2014–2015 driven by advances in image recognition, face detection, and projects such as Google DeepDream.
How TikTok became a professional platform
Ryazanov began posting on TikTok in 2019. Initial experiments with monowheel videos and song translations did not stick; a friend’s suggestion to discuss remote work and Data Science produced his first successful clip. The platform’s recommendation engine, which analyzes watch time, likes, on-screen content, speech, and music, quickly matched his material with an interested audience.
Skills and education required
For engineers and data scientists, Ryazanov insists on a solid foundation in probability theory, linear algebra, statistics, programming, and data handling. Entrepreneurs and marketers need only a clear understanding of capabilities, limitations, and data-handling rules. His own education at MIPT remains essential because much of his current work involves code and model training rather than simple prompting.
Distinguishing artificial intelligence, neural networks, and ChatGPT
Artificial intelligence is the broad goal of automating tasks associated with human thinking. Neural networks are one mathematical approach inspired by biological neurons. ChatGPT is a conversational system built on the Generative Pre-trained Transformer architecture; it predicts the next token while respecting dialogue history, safety constraints, and other controls.
Training begins with enormous datasets and GPU clusters to create a base model, followed by domain-specific fine-tuning or connection to corporate data. The cost of training frontier-scale models is dominated by GPUs, electricity, cooling, and infrastructure.
Prompts, Claude, and paid tiers
A prompt is simply a textual instruction that may assign a role, state goals, specify output format, and supply source material. Ryazanov prefers natural conversation with models, often dictating thoughts via keyboard while walking. He uses Claude most frequently because it maintains long context well and produces precise phrasing; ChatGPT remains useful for its multimodal features. Paid plans mainly remove rate limits and provide priority access during peak load.
Hallucinations, confidentiality, and the “AI psychologist” trap
Common beginner mistakes include uploading sensitive documents and placing excessive trust in fluent answers. Models can invent films, misattribute works, or cite nonexistent papers. Ryazanov warns against sending passports, medical records, trade secrets, or proprietary code to external services. When the cost of error is high—in health, finance, law, or safety—every output must be verified against primary sources and domain experts.
Although models can help structure reflections or prepare questions for a therapist or physician, they are not substitutes for professional care. The convenience of receiving a personalized summary in minutes makes the interface psychologically compelling, increasing the risk of over-reliance.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.