rasiim kyan bey
@wallacedrew.bsky.social
refactoring engineer. i cut dev costs by reducing risk in changing software. domain driven blue collar muda monk. software el shabazz yog ras korunnai.
devs: "code quality is not real it's just a gatekeeping thing" ai: "yea keep thinking that. btw you just ran out of tokens give me more of your money."
burnt offerings to the gods of instant gratification
Technical debt is organizational debt wearing a compiler-approved disguise.
the devs at google openai anthropic etc who are developing these ai tools must not sleep sheesh every week a new ai tool a new feature.
it's the line of code and it's the whole application and it's the whole platform. you think it, structure it, get it out to customers bit by bit in multiple passes for as long as theres a business
got that new Nas x Primo on repeat this weekend. got that new Conway on repeat this weekend 🔥
it never fails. i usually see more mistakes and wasted motion in our workflow and delivery flow when we skip tests or push em off to qa
the idea that waste is just a part of doing business, plus a high tolerance for waste and wasteful workflow, plus the idea that improvement is not worth it. the combo is tragic. what does it all stem from?
the default vibe coded thing brings to mind the smart ui anti/pattern. gotta tighten the leash with the design test direction if i dont want the ai cruft to get outta hand and cost me a lotta tokens and bread
the work is smoother when you can break it down, and sketch out a vision first
a (before n after) picture (captioned with the generally accepted business goals) is worth a thousand words
yes profit is the point. but/and i'll take quality and cost cutting over speed and brute force revenue 90% of the time
the word "craft" gets disrespected. i feel like people think it's just about origami and singalongs. they scoff at your craft. i blame kindergarten. and why did serious software delivery professionals choose such a name for serious disciplined ways of working
not system reliability cloud data or network engineering blehkk. my spirit is in application software design and architecture within refactoring within tech debt or software cost reduction within software delivery operational excellence within thriving coworkers and delighted customers.
the better the domain model the lower the maintenance costs the higher the revenue potential
whether i work too fast, with wasted movement, directionless, unsustainable... or i work quickly, smoothly, with small, deliberate, reversible steps, calling my shots, surefooted... the ai lets me do it more and faster.
my workout today was energizing. cns lit up. left the gym with more energy than i brought into it
git commit -am "refactor: inline function for better clarity" ...15 mins later, after realizing the needed abstraction: git commit -am "refactor: extract function for better clarity"
i see it i scan it i read it i understand it i refactor it i thereby share the understanding with future me and coworkers. and thats just the way it is forever and ever amen.
i always regret tryna be slick with the ternaries. never be slick with the ternaries.
a: whats the best way to complete a complex complicated confusing project? q: break it down. then break those down into smaller projects. continue until you can hold a piece in your brain. do one piece at a time start to finish. do the next, repeat til done. adjust along the way as needed.
q: what's the worst way to complete a complex complicated confusing project? a: force fit it in your head. fool your self into thinking you understand it all tryna meet expectations/ deadline. max out your capacity and deathmarch forward repeating the mantra "git shit done".
me, i like my acceptance criteria like i like my unit tests... Given: Arrange When: Act Then: Assert
...the fine art of vibe coding without exceeding the quota.
being un/pleasant to work with is age-agnostic. ive met some young cats who are apathetic and jaded af. and ive met some older folks who stay enthusiastic and curious.