vula
31 posts


Excited to share that I’ll be speaking at @SolanaConf in Abu Dhabi ☀️
There's no greater honor on Solana than presenting at the Breakpoint stage.
Expect alpha 🫡

English

@filipceres @matija_sol @4ptOLabs @solbound_dev @ninoborovic @rok0_sol Brother @ninoborovic barley fits at the table 📦
English

When vertical scaling hits the wall, people start scaling horizontally.
A.k.a., "we couldn't make our agents produce better code, so we added more agents and made them produce slop faster." 👌
Ivan Velichko@iximiuz
Cursor 2.0 made me seriously consider going back to Vim
English

@matija_sol @ninoborovic @sol_serg @solbound_dev Reminds me of the good old days when dad used to say: “Izađi neću ti ništa” 🙃

Record types were added to C# 9, followed by record structs in C# 10. Have they affected your coding style, and in what way specifically?
Here is my take on the impact that record types have had on how I write C# code nowadays. Record types impacted several areas of coding and design:
• 𝗢𝘃𝗲𝗿𝗮𝗹𝗹 𝘀𝘆𝗻𝘁𝗮𝘅 – records also brought other pieces of syntax, such as init-only setters, primary constructors, with expressions.
• 𝗧𝘆𝗽𝗲 𝗱𝗲𝗰𝗹𝗮𝗿𝗮𝘁𝗶𝗼𝗻𝘀 – there is now a clear division between entities, immutable classes, and value objects.
• 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗱𝗲𝘀𝗶𝗴𝗻 – designing functional types has become easier than ever; one can now write an entire model in a pure functional style, never declaring a single old-school class.
In the latest video, I am demonstrating the effects of records and record structs on the design of types.
As it quickly becomes apparent, there is a strong incentive now towards clearly separating types into:
• 𝗘𝗻𝘁𝗶𝘁𝗶𝗲𝘀 – usually heavyweight classes, consisting of other entities and values, accompanied by a persistent ID, exposing mutable, often costly operations.
• 𝗜𝗺𝗺𝘂𝘁𝗮𝗯𝗹𝗲 𝗰𝗹𝗮𝘀𝘀𝗲𝘀 – traditional classes with no mutators and property setters, but also with reference-typed equality.
• 𝗩𝗮𝗹𝘂𝗲 𝗼𝗯𝗷𝗲𝗰𝘁𝘀 𝗮𝘀 𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝘁𝘆𝗽𝗲𝘀 – immutable classes with value-typed semantics, now coded as records (i.e., record classes).
• 𝗩𝗮𝗹𝘂𝗲 𝗼𝗯𝗷𝗲𝗰𝘁𝘀 𝗮𝘀 𝘃𝗮𝗹𝘂𝗲 𝘁𝘆𝗽𝗲𝘀 – immutable value types with performant value-typed semantics, now coded as record structs.
Write your impressions and experiences with record types in the comments. Watch the full video for more details.
youtube.com/watch?v=ltPCWP…

YouTube
English

Startup village next week, Solana Summer is here bb ☀️🌊🚀
Cringe arc BTS brought to you by the phenomenal @itsme_lucia
English

@davidfowl If o3 searches the web using a search engine, doesn't that mean the search engine is crucial to your result? Just food for thought.
English














