my english writing is quite bad. if i write article i myself cannot read it. ai helps with the flow, review editing.
nowadays i record audio, stt and then let ai flow it properly.
i hate blog.md like this, given a topic and it does everything.
13 karma · joined October 2, 2021
my english writing is quite bad. if i write article i myself cannot read it. ai helps with the flow, review editing.
nowadays i record audio, stt and then let ai flow it properly.
i hate blog.md like this, given a topic and it does everything.
but from good apis, good data, good interface they can generate quite nice frontends.
i guess, frontend as job is going to have a hard time.
also, writing code is not cognitive load, its always reading code. and llms just increase that. so i mostly try to avoid using them.
but i do like researching with them. context free. like googles ai mode, etc. not from my code editor cause then they get biased and suggest stupid sh8t all the time.
volume of low quality content, dsa/leetcode, etc. is so high, good people/content gets left out. networking, connections, nepotism so much high. getting job based on actual talent very rare.
MNCs which are good outside are so much sh8t here; well capitalism doesn't give a f8ck anyways.
i am learning Elixir and liking the concepts. i am coming from kotlin/jvm and i like kotlin, apart from kotlin-coroutines. planning to migration all threading code to virtual threads. but biggest problem is threadlocal.
if anyone in Bengaluru, India having meetups invite me, duckydude20 at gmail.com
i know this is not the best way. but i added a timeout of 10sec. also while asserting i am polling to know if i got a connection.
i understand and i can make it way better. but for now it's good enough. more importantly, it's better not scatter these kind of codes everywhere. also making things explicit is better always. like now server.Start is Blocking. and in my tests i am spawning a goroutine, rather than it doing implicitly.
another thing, testing dependencies. i am going to test concurrent handler. and it's not dependent on tls or tcp. i can just use a fake and test the concurrency. i like this design. scattering these throughout will make every other test integration tests. increasing time to execute and that is bad.
btw, it would have been better if go lang runs tests in parallel.
one lazy is just coping pasting stuff. other is drying as you go. i have already written this line, why am i reapting it again. let me dry it. extract it, so next time i need not. no two lines in my code should match. if they do extract. i am lazy here. cause i don't want to copy paste next time. i am lazy and will just dry. second lazy is more what lazy means.
i am learning rust by reading docs. and it's teaching me so much. i was very fascinated when it gave me a hint about monomorphization. i went a bit deep and it was such a fascinating subject. would a video like these give me a slight hint of something like this and even if they do, they won't cover it.
the issue with these is lets say theres new framework now you have to wait for this guy to upload. the ability to navigate the docs by yourself. that skill is quite important and these take that away. now you are dependent on this guy, these videos. somebody should have already done it.
idk that what i felt. navigating docs is such a vital skill. esp for me. i struggled, it felt daunting 2 years back. but now docs are my way to go. docs of any framework, technology. i do not feel uncomfortable. and still i try to write each letter by my hand. and only copy which i have already written, that too rarely, if so i already knew it needs to dry and i do it asap.
learning the techniques is essential, how to use a tool you can always visit it's manual, but sadly these teaches tools and not techniques...
i am waiting so much........