Boris pfp

Boris

@lokasan

1053 Following
53 Followers


Boris pfp
Boris
@lokasan
My opinion the same, bro
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
ye, this is amazing
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
what is vibecoding, beee
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
nice app, grats
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
grep the best function
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
100% agreed, bro! and the same for me
0 reply
0 recast
1 reaction

Boris pfp
Boris
@lokasan
view is interesting
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
Using Data and Non-Data Descriptors in Python: A Practical Perspective At first, Python descriptors seem like an advanced, behind-the-scenes feature. But once I started using them directly, especially data and non-data descriptors, they became essential for writing cleaner, more powerful code. Data descriptors implement both __get__ and __set__, and always take precedence over instance attributes. I used one to validate temperatures — even if someone tried obj.temp = "hot", the descriptor enforced correctness. This gave me full control over data integrity. Non-data descriptors, with only __get__, are overridden by instance attributes. That’s perfect for cases like @lazy_property, where I compute a value once and store it in the instance for future access — efficient and clean. The key benefit of descriptors is separation of behavior from logic. I no longer scatter validation or caching across the class — it all lives in small, reusable descriptor objects.
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
exactly! I confirmed it
0 reply
0 recast
1 reaction

Boris pfp
Boris
@lokasan
thanks for article
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
@monad GM
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
what?
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
I so want to sleep, aoaoa
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
eh, I don't cry..
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
bad joke. very bad
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
crazy man, so very crazy
0 reply
0 recast
1 reaction

Boris pfp
Boris
@lokasan
I think the same
1 reply
0 recast
1 reaction

max pfp
max
@maxp.eth
workflow that has been going well recently: > claude code w/ 4 opus > big initial prompt; start high-level, ends w/ spoon feeding the direct next thing to do > review work after each prompt, provide feedback & changes > after 2-3 rounds, ask to review progress and simplify anything obvious > try to scope work to end around 10% context remaining (falls off imo) > if not doable, ask to summarize the "days" work in a README to pass to the next session, don't rely on auto-compact
2 replies
2 recasts
8 reactions

Boris pfp
Boris
@lokasan
i remember it
0 reply
0 recast
0 reaction

Boris pfp
Boris
@lokasan
yes, i agreed this
0 reply
0 recast
0 reaction