Sheikh Limon

Fedora Project Apps Maintainer (@fedora). Engineering core developer tooling & infrastructure. Contributor to @goose_oss

[Sheikh Limon @sheikhlimon_dev]

relearning to code again
switched back to arch linux
built my neovim config from scratch
started contributing to open source
participated in hacktoberfest
made contributions to @goose_oss
trying to land job .. frontend, backend or whatever
still learning every day

[Sumedha Uppal @SumedhaUppal]

what’s your 2025 lore?

[Sheikh Limon @sheikhlimon_dev]

I treat AI like a fast, tireless junior-to-mid engineer sitting next to me. I don't give it academic prompts; I give it constraints, have it map out edge cases, and then I act as the filter to cut out scope creep and keep the solution simple.

[lauren @poteto]

codebases have always contained slop. we have always been okay with this because code rarely needs to be perfect, outside of mission critical "hard" (eg embedded) software.

swe is a unique form of engineering because you're often building something that constantly evolves and is almost organic - user tastes change, your mental models evolve, and features come and go.

admittedly, i and many others who've been coding for a long time were initially (like back in 2024) skeptical that agents would write production code. "but what about all the slop that would enter our beautiful codebase?".

well, even before, we had human slop, and there was a lot of it! if we're being truthful, most people call "code i didn't write" slop. the reality is that 99% of people (i include myself in that number) don't even know what Good Code looks like, let alone be capable of writing it. i would propose that Good Code is:

• correct
• bug free
• fast and cost efficient to run

it has always been exceedingly difficult and expensive to write truly Good Code, because for the longest time (maybe @bendlang will change that), code was not something you could cheaply and formally guarantee to have all 3 of these properties. this is why writing hard software is much more difficult and expensive, because depending on the use case, you may only get one chance and so you have to be right from the start.

but the vast majority of software we use does not need to be Good Code to provide value to users. in fact, it is very likely that most software we use is not formally verifiable! we accepted some bugs in exchange for velocity and progress, so we rely on tests and o11y instead and have adopted a more incremental approach. this is a good thing!

agents help us move faster, and if you're open to the idea, are capable of helping us write better code. it won't be Good Code (that is still expensive), but it is likely to be much better on average at scale.

the new craft of swe is to figure out how to do this. it's your job now! if your productivity with and without agents is not significantly different, you're doing something wrong. but it's not too late to embrace it and use it as an opportunity to learn a whole new skill tree

[Sheikh Limon @sheikhlimon_dev]

@owenthcarey Been daily driving for over a year now

[Sheikh Limon @sheikhlimon_dev]

@ivandotcodes Pretty stocked

[Sheikh Limon @sheikhlimon_dev]

I'm 27.

Fedora Apps Maintainer & OSS Contributor from Bangladesh.

Looking for a paid job before my career path unlocks the “Manual Labor” DLC. 😭

[Dmitrii Kovanikov @ChShersh]

I'm 32.

Solo C++ dev from the UK, based in London.

Looking to connect with more C++ devs!

[nini @nini_incrypto_]

Google 把内部工程师的代码审查（Code Review）规范公开啦

这几乎是目前业界最顶级的标准

很多程序员只会写代码，但不知道怎么审代码，可以看看 Google 是怎么做的

1.双向指南：不仅教审查者怎么挑毛病，还教作者怎么写出容易通过的代码

2.术语科普：解释了 Google 内部常用的 LGTM（看起来不错）和 CL（变更列表）到底意味着什么

3.实战价值：这套规范不是理论，而是 Google 每一位工程师都在用的实际操作准则

如果你想提升团队的代码质量，或者想知道顶级大厂的开发门槛，这份文档必读！

https://t.co/OdaozRkMYn

[Sheikh Limon @sheikhlimon_dev]

@adibhanna That’s amazing news. Congratulations!

[Adib Hanna @adibhanna]

Had an interview with a “crypto” recruiter. We talked for about 40 minutes, and then they asked me to look at some code.

Their first instruction was to clone the repo. I didn’t. They seemed surprised, so I told them I wanted a moment to check whether it was safe first.

I ran a quick analysis with Claude.

Turns out the code had a backdoor. It would copy my environment variables and send them to a remote server.

The recruiter went speechless and ended the call pretty quickly.

Be careful who you talk to. Scammers are real.

[trash @trashh_dev]

me and my llm trying to find an entry level software engineer position

[Adib Hanna @adibhanna]

So I think I’m going all in on my company, @lumarylabs — I’ve never been happier working since I lost my job. The freedom to build anything you want is priceless.

(At least until I burn through my savings.)

If you’re looking to build any kind of software, I’m open to new clients.
(please share this for visibility)

[Sheikh Limon @sheikhlimon_dev]

@adibhanna @lumarylabs This really resonated with me. I’d love to contribute and learn if you’re open to it. Portfolio here: https://t.co/FouUpZ4Ddu

[jack @jack]

mesh-llm: pool compute to run open models. built by @michaelneale at block: https://t.co/MV79Rmz37a

[Nick Khami @skeptrune]

>what do you think of the claude codebase?

brother, i'm not even reading my own code anymore. what makes you think i'm going to read someone else's?

[Sheikh Limon @sheikhlimon_dev]

@ptr_to_joel lol

[The Wheelie Investor @WheelieInvestor]

Dude why is my girlfriend doxxing me?!?!

[Node.js @nodejs]

Node.js is moving to one major release per year starting with Node 27! 🚀

✅ Simpler: Every release becomes LTS.
✅ Predictable: Version numbers now align with the year.
✅ New: A 6-month Alpha channel for early testing.

Read why we’re evolving: https://t.co/PVWdf9Z1q9

[Sheikh Limon @sheikhlimon_dev]

@TheFigen_ could be her husband though

[Sahaj @iamsahaj_xyz]

update: I vibe-coded my own diff viewer using rust

- super fast
- syntax highlighting with treesitter
- vim-like keybinds (hjkl)
- navigate to next changed hunk with "}"
- mark file as viewed with space

might open-source once I'm happy with it

[Sheikh Limon @sheikhlimon_dev]

@himanshustwts LoL

[jack @jack]

dialectical autocoding: https://t.co/RSufx0WmKk

new research by block AI (https://t.co/MmzmTIswSP)