sun(PhD)
35.8K posts

sun(PhD)
@nightingale_dev
constantly breathing in and out

Call for help. My mum was hit with a stroke in may 2024. Since then our lives haven't remained the same. My family have spent all our savings yet her condition hasn't changed. She has severe BP challenge, she has diabetes. Which has gone on to take a toll on her kidneys.

Yinka Ayefele interviews Baba Ijesha on Fresh FM Baba Ijesha insists he did not commit any offence

These beautiful Dutch will not be around if they keep on importing Muslims

Trivela pass. Copyright: Lamine Yamal




Day 010 of putting it out there that I'm open for new opportunities! I have 8 years of experience working with libraries, tooling and frameworks built with JavaScript and PHP including but not limited to Laravel, WordPress, AdonisJS, Next.js, Nest.js, React, Vue.js, Svelte, jQuery, Tailwind CSS, Inertia.js, etc. linkedin.com/in/devhammed








Code is an output. Nature is healing. For too long we treated code as input. We glorified it, hand-formatted it, prettified it, obsessed over it. We built sophisticated GUIs to write it in: IDEs. We syntax-highlit, tree-sat, mini-mapped the code. Keyboard triggers, inline autocompletes, ghost text. “What color scheme is that?” We stayed up debating the ideal length of APIs and function bodies. Is this API going to look nice enough for another human to read? We’re now turning our attention to the true inputs. Requirements, specs, feedback, design inspiration. Crucially: production inputs. Our coding agents need to understand how your users are experiencing your application, what errors they’re running into, and turn *that* into code. We will inevitably glorify code less, as well as coders. The best engineers I’ve worked with always saw code as a means to an end anyway. An output that’s bound to soon be transformed again.













