anish

trying to be a better software engineer

[anish @singlaanish56]

@whysosaket @Microsoft @striver_79 @kirat_tw @neembu_paani31 best🤣

[anish @singlaanish56]

@kirat_tw Music ( and instruments)

[amul.exe @amuldotexe]

Hypothesis:
ADHD folks, you likely need less drama in your life

not more

your ambition will paralyze you & stop you from making imperfect progress

just make directionally correct progress & let good things happen to you

make friends with your mediocrity

focus on the process

[anish @singlaanish56]

@ankushdharkar

[anish @singlaanish56]

@_svs_ also most of those pcs just needed cleaning, and because I didn't have any of my own. I used to mix and match the ram / those teeny graphic cards and play on it for weeks.

[anish @singlaanish56]

@_svs_ didn't actually get into it till very long, but the affinity was because was dad used to write custom software for local companies and also repair their pcs. I was just mesmerized by how everything worked when we was there. Computer won't be turning on for days, but as soon (1/n)

[anish @singlaanish56]

@_svs_ He touches it , boom works smoothly. Just trying to find that magic in me.

[anish @singlaanish56]

only way to beat my "skill issue"

[major tom @tailwiinder]

Just met a guy who's in his early career grind phase and he said to me

"the pain of consistently working hard isn't going to go away, whether I like it or not, so I might as well do my part instead of complaining about every minor inconvenience"

Honestly... sums everything up

[major tom @tailwiinder]

Just met a guy who's in his early career grind phase and he said to me

"the pain of consistently working hard isn't going to go away, whether I like it or not, so I might as well do my part instead of complaining about every minor inconvenience"

Honestly... sums everything up

[anish @singlaanish56]

trying hard to actually code my projects instead of fixating learning the language properly or deciding on which framework/lang to use.
It takes more time I know but I am happy I am actually doing something however slow

[anish @singlaanish56]

I understand it's not much, but trying something new. Stuffing too much in a single night with constant context switches, j wasn't able to go past 2 points on my daily checklist.
Keeping it simple enough for my frog brain to handle.
Also focusing more on interview skills

[anish @singlaanish56]

had this self-realization after attending the session on the url parser. I want to have that clean thinking approach to a problem.

Doing that for a week now + 2hr time constraint to help with interviews

[Arnav Gupta @championswimmer]

**Structuring Code Neatly**

Rather than mugging up a bunch of theory about 99 types of design patterns and do a bunch of “LLD Courses” it is better to start off with tightly scoped little command line programs, play with the code, implement the same thing 2-3 times and start seeing the mess in your code and looking at ways it can be more “neatly” arranged so you don’t write the same lines multiple times and extending/changing the logic becomes “easy”.

Here’s some examples -

- parsing URLs into scheme, host, port,path,query etc (read the RFC that defines the URL standards)
- create a command line tic tac toe game, then try to write the “bot” that can play against a human
- create a command line “PC builder” - you need to provide a mobo, CPU, GPU, RAM,HDD to build, CPU & mobo socket must match, RAM & CPU speed must match etc

build them twice, or even better thrice (each time starting from scratch)
Makes you understand how rewrites happen
Gives you perspective when building again that you can pre-empt some issues you ran into first time

Once you’ve done this, then parallely reading up a bit of theory doesn’t hurt. Knowing the formal names of Builder pattern or using a visitor class is good. But first write some shitty code, then rewrite it, get to realise why it was shitty first, then learn all these design pattern “labels”

[anish @singlaanish56]

@version0chiro Insane dedication brother, can you only manage first two everyday

[major tom @tailwiinder]

Optimize for longevity when you begin learning to code.

Your initial strategy must not be to become some ultra giga coding legend. You should initially only optimize to NOT GET BURNT OUT.

If you're comfortable with coding for only 15 minutes a day, start off by coding only for 15 minutes. Increase the limit gradually once your muscle memory starts building and once you start getting used to the process.

If you start panicking and try to get too much done too quickly, you'll most likely end up burning yourself out and being in a paralyzed state for 2-3 months after only a week of following a hectic multi-hour-long routine.

A career is a long game. Treat it like that. Your initial delay won't matter much in the long run.

It's better to get it done a few months late than to hate your work for years and years to come. Understand yourself before you understand code.

[anish @singlaanish56]

@manthanguptaa adding those lines / grids helps somewhat

[anish @singlaanish56]

something that helps me when I really go off track is streaming on twitch. Works well as a mirror.
Sometimes I also explain concepts to my 0 following.
As always I don't abuse it regularly

[amul.exe @amuldotexe]

Starting a body-doubling twitter group chat

DM me if this interests you

standard operating procedure:
- someone shares a gmeet link
- everyone joins, mentions their target for study in chat e.g. complete 5 pages of Rust book in 1 hour
- everyone mutes audio, switches on video if they feel comfortable, else continue with video off
- everyone shares their update against the target they had set
- folks join & leave as they please or start their own google meet
- there will be no talking while the study session is on
- there is limited chat activity apart from study session goals & progress update

p.s.
if you have an existing body-doubling gc on twitter, please feel free to invite me

I am creating this since I couldn't find one

[anish @singlaanish56]

so they forcing us to finally work at a farm, not just dream about it /jk

[Cognition @cognition]

Today we're excited to introduce Devin, the first AI software engineer.

Devin is the new state-of-the-art on the SWE-Bench coding benchmark, has successfully passed practical engineering interviews from leading AI companies, and has even completed real jobs on Upwork.

Devin is an autonomous agent that solves engineering tasks through the use of its own shell, code editor, and web browser.

When evaluated on the SWE-Bench benchmark, which asks an AI to resolve GitHub issues found in real-world open-source projects, Devin correctly resolves 13.86% of the issues unassisted, far exceeding the previous state-of-the-art model performance of 1.96% unassisted and 4.80% assisted.

Check out what Devin can do in the thread below.

[anish @singlaanish56]

@manthanguptaa upvoted, following your golang goal from the teo server 😄.

[anish @singlaanish56]

will give it all, there will be no what if I tried

[Kunal @masaladosa4hb]

I am afraid of being mediocre and not reaching my goals

[anish @singlaanish56]

Just finished first machine coding round for an interview.
I need to do a timed practice more, I usually complete it in 3 hours
but with a timer running , I was all over the place for the first hour.

I will be prepared next time 💪