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
Securing 1C Web Client Access with External MFA via Nginx, Keycloak and Active Directory
A detailed implementation separates user browser access from integration traffic by placing MFA enforcement on an external Nginx and Keycloak layer while preserving the original IIS endpoints for automated systems. The architecture uses a new IIS server for employees only, with oauth2-proxy handling OIDC flows against Keycloak federated to Active Directory. Access is restricted to members of a dedicated AD group such as 1C_Web_2FA, and TOTP serves as the second factor. Existing integrations continue to reach the legacy IIS directly from whitelisted IP addresses without triggering interactive authentication. The solution avoids 1C OpenID Authentication, keeps native 1C login intact, and supports desktop shortcuts that launch the web client in a dedicated browser window. Network controls ensure the new IIS cannot be reached directly from the internet, preventing bypass of the MFA gateway.
Avanpost Unveils DAG System for Sensitive File Discovery and Excessive Access Rights Management
Avanpost has launched its new DAG solution designed to control access to unstructured data across file servers, cloud environments, and corporate knowledge bases. The system scans file contents to identify confidential information, maps actual user permissions, and highlights policy violations that official regulations often overlook. Built-in workflow automation routes access review requests to data owners, collects approvals, assigns remediation tasks to IT teams, and verifies changes through follow-up scans. DAG integrates with existing IdM/IAM platforms to factor in employee roles and employment status, automatically triggering access reviews during job changes or terminations. The platform also forwards detected violations to SIEM and SOAR systems for coordinated response and supports both high-load enterprise deployments and simpler mid-market installations. Customers can request on-site pilots to evaluate the solution against their current infrastructure.
Why Complex Password Policies Fail to Protect Companies: Practical Account Security Guidance
Many organizations implement strict password rules requiring at least eight characters with numbers, uppercase letters, and special symbols, plus mandatory changes every 30 days. Employees respond by creating predictable variations such as Company2026!, Company2026@, and Company2026#, which offer little real protection against phishing or credential stuffing. The core issue lies in poor visibility into all accounts across Active Directory, VPN, cloud services, databases, and contractor access rather than password length alone. Effective security begins with full inventory of every account, classification into user, privileged, service, and external types, and clear ownership assignment. Privileged accounts require separate credentials, MFA, minimal rights, and activity logging, while service accounts must avoid hardcoded secrets in configuration files or source code. Password managers must enforce client-side encryption so that even compromised administrator accounts cannot access stored secrets. MFA deployment should prioritize high-risk entry points such as VPN, email, and backup systems, and access revocation must integrate with HR processes to prevent former employees or contractors from retaining credentials.
Wireshark Wi-Fi Traffic Analysis: Diagnosing Connectivity Failures in 802.11 Networks
Wireshark captures help distinguish between radio-layer issues, DHCP failures, and application-layer problems when a device connects to Wi-Fi but cannot load pages. The guide explains how to select the right capture point—client, monitor-mode adapter, or wired side of the access point—and why ordinary Ethernet headers often hide critical 802.11 management and control frames. Detailed sections cover CSMA/CA contention, frame types (Management, Control, Data), EAPOL-Key exchanges for WPA2-Personal, and the limitations of retry flags as loss indicators. Practical Linux commands using iw, dumpcap, and NetworkManager demonstrate how to enable monitor mode on channel 6 HT20 and record a two-minute trace. Filters for wlan.addr, eapol, and wlan.fc.retry allow analysts to isolate association failures, key-handshake problems, or DHCP delays. The article also addresses decryption of WPA2 traffic with a known passphrase and warns that Wireshark cannot replace a spectrum analyzer for detecting non-Wi-Fi interference.