Malkevych Roman

Local lead NASA Space Apps in Kyiv | 🇺🇦

[Malkevych Roman @RomanMalkevych]

Уявіть, якби Чорне море було біля Чернівецької області. Тоді логістика на Заході України була б значно дешевшою. Але це майже так і є. Бо ми маємо можливість це реалізувати почавши річкове судноплавство з Хотина і закінчуючи прямим виходом в море. Єдина проблема - ПМР.

[Mykhailo Liuksikov @liuksikov]

Мало відомий факт, але на території сучасної Молдови на річці Дністер існує річкове пароплавство та навіть є судноремонтна бригада, існуюча на базі судноремонтно-суднобудівного заводу. Так це не одруківка і там навіть щось будували як наприклад плавдок.

Але про все по-порядку ⬇️

[AYi @AYi_AInotes]

网景创始人 、硅谷顶级投资人Marc Andreessen 在访谈里坦言，他看到了科技史上最可怕的一道认知鸿沟，

传统巨头以为 AI 只是个降本增效的插件，而新一代 AI 原生团队，正在用完全非人的组织效率掀翻整个商业版图。

当年写出网景浏览器、见证了整个互联网三十年兴衰的 Marc Andreessen，坐在 Ben Horowitz 面前直接发出了感慨，
如果 1994 年我们做 Netscape 的时候就有今天这种 AI 工具，那简直不可想象。

现在绝大多数传统巨头和现有企业，依然在用改良软件的旧思维去看待大模型。

在他们的组织逻辑里，AI 只是一个高级功能，用来给现有业务做个插件、在钉钉里加个智能助手、或者把客服团队砍掉 20% 省点成本。

他们以为自己在拥抱变革，其实只是在给老旧的蒸汽机打补丁。

但真正恐怖的事情，正在那些刚成立的 AI 原生团队里发生。

那些创始人对 AI 能力的理解，跟大厂完全不在同一个平行宇宙。

他们每周都在看着底层技术飞速进化，而且他们压根不会把自己定义成一家软件公司、硬件公司、甚至是一家 AI 公司。

以前创办一家公司，你的组织架构是按人类的协同瓶颈搭出来的：
招产品经理写文档、招工程师写代码、招法务改合同、招运营做投放。
因为人类的脑力带宽有限，所以必须靠庞大的部门和管理层级来支撑业务。

而真正的 AI 原生物种，是用机器智能作为最底层的骨架。

两个人加上一整套自动化 Agent，可以直接把从市场洞察、软件工程、全栈设计到商业销售的链路全部跑通。

他们不是在效率上快了 30%，他们是在组织形态上彻底跨越了一个物种。

大厂的盲区，从来不是买不起算力，而是他们无法理解组织本身才是最大的负债。

当现有企业还在开会讨论如何把 AI 塞进现有的业务流程时，新一代的野蛮人正在用完全超越行业界限的方式，把传统的业务流程连根拔起。

未来拉开人与人、公司与公司之间差距的，根本不是你用了哪个模型，而是你到底是在用新工具维持旧世界的体面，还是用新世界的底层逻辑，重新定义了自己能做的事情。

[Malkevych Roman @RomanMalkevych]

yes

[Eric S. Raymond @esrtweet]

Entirely true. It's the second-rate programmers that are having trouble adapting to AI, and screaming about it.

The A-list guys are delighted. Listen to Linus Torvalds. Or DHH. Or, a little outside my usual community, Uncle Bob Martin. We can get so much more done now!

[Malkevych Roman @RomanMalkevych]

True

[Santiago @svpino]

For some people, coding was the only valuable skill they had.

If you made your money by selling your ability to write JavaScript, CSS, Python, or whatever else, I understand why you are pissed now.

"Writing code" is worth very little today.

The sad part is that learning to code wasn't easy. It takes years for someone to become a skilled programmer.

Imagine watching all of those years go down the drain.

If you are a programmer (I mean, just someone who knows how to write code in a particular programming language), your days are numbered.

If you still think AI can't do your job, you are just in denial.

But honestly, writing code was never that valuable anyway. If you were a code pusher, you already knew that the best people at your company weren't just writing code.

They came up with new ideas, designed solutions, architected whole systems, knew how to troubleshoot and fix problems, found different ways to build better software, and, in general, spent almost no time writing code.

Not only are those people thriving today, but they're also the ones who will ride the AI wave and learn to bend it to their will.

So don't cling too long to what you lost; embrace what's already here. AI is a tide that lifts all boats, but you have to be open to it.

[Malkevych Roman @RomanMalkevych]

@SecurityReasons В школі багато чого не дають. Щось залежить від самих викладачів і їх залученості, а щось від самих дітей.

Зараз кожен має щось подібне до Jarvis залізної людини, але не кожен має бажання вчитись і розбиратись, творити.

До прикладу такі речі - https://t.co/P8jauz2E2W

[Matt Shumer @mattshumer_]

I asked Opus 5.5 to build a working computer from scratch.

And holy fuck did it deliver.

277k logic gates in JS, an OS on top, and games on the OS. This isn't a mockup... it's a computer.

Run it: https://t.co/fnAEYEPjo5

[Malkevych Roman @RomanMalkevych]

True

[Tim Sweeney @TimSweeneyEpic]

When I was writing Unreal Engine 1, my time was divided as follows:

- Around 30% went to seriously deep coding on hard problems: assembly language texture mappers, C++ BSP trees, data persistence, object oriented systems design, and networking.

- Around 70% was just typing and refactoring large bodies of code needed for a complete engine feature set. This was not hard, and while I was doing it my mind was mostly on the deeper coding topics, thinking and planning for what's next. It didn't feel much different from vibe coding today, except that it was just me typing code on an IBM Model M keyboard rather than prompting it and reviewing the results.

So, it has always seemed perfectly logical that we would rely on AI for that 70%, once the AI could do it with a similar quality standard as we could, which has never been perfection. It came as no surprise that, after a few years of AI model evolution, it was able to take the reigns on that 70% and free up programmers' time for more valuable tasks.

What's more of a surprise is the emergence of AI as a sort of insta-Carmack able to solve hard technical problems quite cleverly and often cleanly, and that it's able to reason about and work in complex 3D scenes both by operating the tools and by directly understanding the raw data files.

I abandoned assembly language in 1998 when out-of-order CPUs made much simpler C/C++ code faster, and never I missed it. If prompting through architectural documents, concept art, and design plans can transcend typing code and tweaking vertices, that will enable developers to spend their time on higher-level, higher value technical and creative tasks.

What matters is the end product, whether it's a game or an engine. Anything developers can do to try out more ideas and make better software and games faster is a win for everyone.

[Malkevych Roman @RomanMalkevych]

@ViUmaVaga С

[Malkevych Roman @RomanMalkevych]

@skypodolsky Нагадало як ми в дитинстві робили свої халабуди на території одного закинутого будівництва. Прикольно було, поки хтось з місцевих хлопчаків не спалив її :)

[Malkevych Roman @RomanMalkevych]

True

[Daniel @growing_daniel]

Software engineers now

[Casey Handmer @CJHandmer]

Long list of QTs of mathematician reactions to OpenAI's release of hundreds of new mathematical proofs.

As a reformed mathematician, I have grown increasingly resentful of the way that gifted children are railroaded into math programs, partly as a side effect of excellence in math emerging relatively early and partly because it's less politically incorrect to recognize excellence in a field that's relatively objective - which is also related to why the LLMs are able to close verifier loops and make progress on RL with math.

In short, promising children should receive comprehensive educations and make contributions across society, including in leadership (France has had several leaders who were also prominent mathematicians for example) and industry - not simply fill universities and quant shops with 180 IQs who earn $50k per year and obsess over semantics. Well it's a bit moot now anyway.

I feel fortunate to have avoided this fate, mostly, by being too disagreeable and/or untalented to make it in academia. As a result I've been able to work in, learn from, and contribute across a wide range of areas. For the next few months at least, it is the time of the dilettante!

[Andrew Curran @AndrewCurran_]

I deeply respect anyone who can update their views in the face of new evidence. The last four years have really taught me how rare it is for someone to be able to publicly change their mind.

[Andrew McCalip @andrewmccalip]

Incredible things happening on the timeline.

I'm full of conflicted feelings about vibe-making. That probably means we're early to a new trend.

[Eric S. Raymond @esrtweet]

This morning it finally came home to me. I will probably never write another program in C again.

Which is a big deal. I've been writing C since 1983. 43 years is a long time and a lot of skill investment.

It's not like I didn't see this coming. I've been writing about the decline of C for years, predicting that it would be displaced by newer systems languages with better safety guarantees and more coherent designs.

It wasn't better language design alone that did it, though. It's how good LLMs now are at generating code from specs and prompts.

This means I can speak a program into existence in Rust or Go without any more effort than would be required to conjure it up in C. What makes this particularly dramatic is that I never learned to hand-code in Rust. And now - I don't need to.

What a long, strange trip it's been.

[Malkevych Roman @RomanMalkevych]

@evil_kaya +

[Malkevych Roman @RomanMalkevych]

True

[François Chollet @fchollet]

I don't read/write code these days, I only instruct an LRM. But it's not because I think LRM code quality is perfect, or even good. And it's not because I think my instructions are always being perfectly acted upon -- I know they aren't.

The thing is: LRMs don't just write your code, they unlock new ways to control what you're doing and maintain understanding of your system, which are about as effective as reading code. You can better test your codebase, you can audit specific components, you can spin up visualizations, you can ask the LRM to red team, etc. You can do all of these things at high speed -- you couldn't before. The benefits of reading/writing code can now be achieved in new ways.

All in all, the ROI of writing code by hand is no longer looking good, not because LRMs got perfect but because they're so fast at doing things that you can develop new workflows around them, workflows that end up being more productive than the old workflows.

[Malkevych Roman @RomanMalkevych]

@thebuggeddev Cool! Can you share repo or prompt?

[Emily - SF ✈️ Nov 7-21 @the_aiju]

i feel so torn up that SO MUCH of my knowledge is now useless? every single C trick i've ever learned. my encyclopaedic knowledge of the verilog standard. all the maths i ever learned. what was it all for. :( my entire pre-LLM output is like a few months of clauding. like wtf.

[Dan Loewenherz @dwlz]

I honestly don’t care at all that I spend 30 years of my life learning syntax and now that knowledge is essentially useless.

Frankly, I’m relieved that I don’t need to care about it anymore. That stuff never really mattered anyways. Code was always just a means to an end.

All I care about is building products that users love. Now I can do that faster. That means I can have bigger impact.

If anything, software engineers should all be celebrating. I don’t understand why you’d “mourn” not needing to write code. The code was never the point.

[Malkevych Roman @RomanMalkevych]

Very true for Ukraine.

[Malkevych Roman @RomanMalkevych]

I agree with you. I've been organizing this hackathon in Kyiv with my wife for 10 years, and it seems to get worse every year.

Hardware challenges were removed; almost everything left is just website challenges.

I was at the ActInSpace hackathon and it was much better; they prepared real practical challenges for participants.

[Malkevych Roman @RomanMalkevych]

Можливості необмежені, головне мати власні бажання і волю до їх реалізації

[Victor M @victormustar]

Opus 5.5 designing LEGO 👀

I asked it to design a Microduck I can build with real LEGO pieces. It:

> designed it life-size using 1113 real LEGO parts
> verified: 3,204 connections, 0 collisions, every step buildable, centre of mass inside the feet 🤯
> made a 141-page LEGO-style booklet (237 steps)
> priced every piece in the browser and prepared the orders on BrickLink