Search
1000 results for “im_a_GDeveloper”
-
Mastodon #introduction: I'm a computational scientist at Idaho National Laboratory (a US DOE nuclear lab), a developer of the #C++ MOOSE #FiniteElement framework (https://mooseframework.inl.gov), interested in #PhaseField research and computational methods development. I nerd out on #Wikipedia and #OSM #geodata (https://wma.wmcloud.org/), built a pandemic #van, and love #hiking and #camping.
-
Mastodon #introduction: I'm a computational scientist at Idaho National Laboratory (a US DOE nuclear lab), a developer of the #C++ MOOSE #FiniteElement framework (https://mooseframework.inl.gov), interested in #PhaseField research and computational methods development. I nerd out on #Wikipedia and #OSM #geodata (https://wma.wmcloud.org/), built a pandemic #van, and love #hiking and #camping.
-
Mastodon #introduction: I'm a computational scientist at Idaho National Laboratory (a US DOE nuclear lab), a developer of the #C++ MOOSE #FiniteElement framework (https://mooseframework.inl.gov), interested in #PhaseField research and computational methods development. I nerd out on #Wikipedia and #OSM #geodata (https://wma.wmcloud.org/), built a pandemic #van, and love #hiking and #camping.
-
Mastodon #introduction: I'm a computational scientist at Idaho National Laboratory (a US DOE nuclear lab), a developer of the #C++ MOOSE #FiniteElement framework (https://mooseframework.inl.gov), interested in #PhaseField research and computational methods development. I nerd out on #Wikipedia and #OSM #geodata (https://wma.wmcloud.org/), built a pandemic #van, and love #hiking and #camping.
-
I think I need an exit plan from my #engineering project
I've had a great time on it, but I'm not sure how I can move it forward from here.
The project sits directly on the intersection of #sofware #space #orbitalmechanics and #radar. I'm a #developer with a lot of self-taught knowledge in the other fields, so it was perfect for me to evolve into sort of a tech-lead
Our initial success led to a (local) revolution in #data collection (95% less time to perform much better overall).
The same underlying algorithms can be applied to other problems, so why not expand those capabilities?
Because we were so successful a lot of subprojects have been built on what we did. The experts on the core team don't have time to push forward on these frontiers I'd like to work on and I don't have the ability to do it by myself.
Also, the #python #code I wrote/designed now has people that could maintain it.
So I'm sort of at a loose end inside my own project.
Maybe I should find another struggling good idea and chip in.
-
I'd better do a proper #introduction since this is a new profile on a new server 😊
So, hi! I'm Jesper. I'm known online in most places as graffen.
I do cyber security for a living, mostly from an architectural perspective, having spent most of my career as a developer.
I'm a part of the #BornHack organiser team, I'm on the board of #data_coop and you'll often find me drinking cortado at #cryptohagen. My ham callsign is OZ9DLP although I'm hardly ever on the air.
-
@OutOfExileIDR
HI, I'm a developer so I can answer any questions. #Awakari is a free and #opensource service designed to filter a content matching your personal interest from many public sources. You can consider it as a real time search alerting thing or a filtering feed reader. -
I guess it's time to post a new #Introduction, what with the #TwitterMigration going on.
Hi! I'm Gaffen, I'm a #Developer focussing on #web technologies. I also front @hearsepileup in my spare time. On here I mostly post random thoughts, touching on #politics and #PowerDynamics. I'm interested in #smallweb, resisting #surveillancecapitalism and #digitalcapitalism. Most kinds of capitalism haha. I also tend to post my #pixelart and #drawings here from time to time.
Enjoy fediverse, be safe!
-
Full disclosure: I’m a developer on the #kernelCare team, and we already have live patches for #copyfail. No reboot required. Feel free to ask questions.
https://blog.cloudlinux.com/cve-2026-31431-copy-fail-kernel-update
-
#introduction I'm a software engineer currently in a developer relations role at #Google and loving it.
When I'm not coding I'm probably running in the mountains of southwest #Colorado. Previously lived in #SantaFe and #Flagstaff and worked with satellite imagery at #USGS and #DescartesLabs.
#devrel #webdev #frontend #typescript #nodejs #automation #maps #geospatial #opensource
#hydroponics #gardening #vegan
-
I just migrated my account, so I guess an #introduction is in order.
I'm a developer turned product manager. I have been building developer tools and platforms my whole career. Currently, I work at RapidAPI, building API tools and services for developers. It's fun. In the past, I did similar things at Salesforce and Microsoft.
My passion Is #TrailRunning and #UltraMarathons. I love losing myself on long runs.
I look forward to meeting new people and reconnecting with friends.
-
I see a lot of people introducing themselves. I like it. Here's mine.
I'm a developer turned product manager. I have been building developer tools and platforms my whole career. Currently, I work at RapidAPI, building API tools and services for developers. It's a lot of fun. In the past, I did similar things at Salesforce and Microsoft.
My passion is #TrailRunning and #Ultramarathons. I love losing myself on long runs. I hope to connect to more people here and discuss #Running.
-
A belated #introduction: I'm a developer from Brisbane, Australia. Father to 3 wonderful kids who better than me in each an every way 😂
I originally trained as an Industrial Designer but eventually made my way into the digital space (long story). I'm a business owner and I love #football, #brisbaneroar, and #3dprinting (among other things).
-
Alright! Here is my #introduction . I'm am #autistic #trans #nonbinary person.
I'm a developer interested in #functionalprogramming #kotlin #scala #rust #reactivesystems #distributedsystems #security #devops #opensource
I'm a gamer 🎮 #ttrpg #ttrpgs #rpg #masseffect #dragonage #fallout #dandd
I'm a trekkie 🖖 #startrek #StarTrekTNG #startrekds9 #startrekvoyager
Other stuff: #anarchism #antispecism #veganism #environmentalism #transrights #antiracism #blm #antifascism #queerfeminism
-
The Ghost in the Code: Why Developer Integrity is Leaking Memory
1,648 words, 9 minutes read time.
The fundamental contract between me as a developer and my users is a sacred protocol, and right now, my industry is failing the handshake. When I see code specifically designed to break a product unless a ransom is paid, I’m not looking at “gating a feature”—I’m looking at professional sabotage. We are reaching into a user’s environment, seizing control of their native browser functions, or even their physical hardware, and holding them hostage for a credit card number. This isn’t a “business model,” it’s a protection racket run by men who have forgotten that our job is to reduce entropy, not manufacture it.
Let me be clear: I don’t have a problem with a developer who works hard to develop a feature getting paid their worth. We deserve to be compensated for the value we add to the world.
However, personally, I don’t write feature-gated code. I refuse to build traps. I am sick to my stomach that the industry I love has normalized this. If I see a
@media printrule injected just to blackout a component that works perfectly on-screen, I see a ghost in the codebase. Someone decided that their “right to profit” outweighs the user’s “right to function.” This isn’t a new practice; my industry has been flirting with “crippledware” since the days of floppy disks. But just because a sin is legacy doesn’t mean it isn’t technical debt that will eventually bankrupt our collective reputation. I am deconstructing the three reasons why this “sabotage” logic is a terminal error: the theft of user agency, the systemic rot of enshittification, and the inevitable “logic bomb” of community blowback.I’ve watched juniors think they’re being “clever” when they hide a kill-switch behind an obfuscated minified bundle. They think they’re protecting “intellectual property.” The hard truth is they’re usually just hiding mediocrity. If a product is so flimsy that the only way to get a conversion is to break the user’s “Print” button, we haven’t built a tool; we’ve built a digital shakedown. As a lead architect, I must build value that people want to pay for, not hurdles they are forced to pay to jump over. I am looking at the kernel-level rot that occurs when developers prioritize “anti-features” over actual deployment stability.
The Seizure of Borrowed Authority and Hardware Ransom
When I deploy a web application, I am a guest in the user’s browser. But this rot has spread far beyond the browser. We are now seeing the “Ghost in the Code” haunt physical objects. When a manufacturer installs heated seats in a car or extra storage in a computer, and then charges a monthly fee to “unlock” them, they are committing Hardware Ransom. The hardware is already there; the manufacturer has already incurred the cost. It costs them absolutely nothing for the user to use what they have already bought and paid for.
Using code to gate physical equipment is the ultimate form of extortion. It’s the equivalent of a SharePoint architect intentionally breaking the “Export to Excel” function because they want to sell a “Premium Reporting” module. It’s lazy, it’s hostile, and it reveals a fundamental lack of respect for the environment we operate in. When I write code that intercepts a
beforeprintevent to unmount a component or prevents a heating element from firing in a car, I am telling the user that they don’t actually own their machine while my script is running.If my character is the kernel, this kind of logic is a “Kernel Panic” waiting to happen. I cannot build a high-stability career on a foundation of deceit. Every time the industry ships an “anti-feature,” it trains brains to look for ways to restrict rather than ways to empower. We are becoming gatekeepers instead of engineers. In the long run, the market treats gatekeepers like legacy hardware: it finds a workaround and discards them. My authority comes from the value I add, not the friction I manufacture.
The Architecture of Enshittification and the Rise of the Frustration Machine
I must call this practice what it is: a tactical execution of Enshittification. This isn’t a new protocol, but it has become the standard operating procedure for weak companies that have forgotten how to innovate. The lifecycle is predictable: First, a platform or plugin is useful. It solves a problem cleanly. The “Handshake Protocol” is honest. Next, once critical mass is achieved and users are locked in, the pivot happens. The company stops creating value and starts harvesting it. This is when the “Ghosts” are deployed.
The transition from a “useful tool” to a “frustration machine” is where engineering ethics are put to the test. If I am the developer assigned to write the code that hobbles a free version—or locks a physical car seat—I am the janitor of enshittification. I am physically installing the decay that the C-suite ordered because they are too lazy to build a Pro tier that actually justifies its price tag. If we can’t build something that someone pays for because it works, and we have to rely on it failing to trigger a payment, we’ve already lost the war. We’ve admitted our code isn’t good enough to compete on its own merit. We’ve “deprecated” our own integrity.
This “frustration-first” architecture is a crutch for the mediocre. A real lead knows that the most profitable software in history is the stuff that makes the user feel like a god, not a victim. If someone builds a SharePoint web part and intentionally hobbles the CSS so it looks like a 1995 GeoCities page unless the user buys a license, they’re a hack. They’re taking the easy path because they’re too lazy to build actual, high-level features that provide real ROI. My character is the operating system for my career. If I’m comfortable shipping “frustration machines,” then my OS is riddled with malware.
The Logic Bomb: Community Blowback and the Spite-Driven Deployment
Here is the hard truth about the “Ghost in the Code”: the web is transparent. Sabotage logic runs on the client-side, which means the “lock” is handed to a room full of people who know how to pick it. This applies to hardware, too. When car companies lock features, the community responds with “jailbreaks” and custom firmware. When developers insult the intelligence of their peers by shipping a “frustration machine,” they invite a “spite-driven” deployment. I have seen companies go under because they got too greedy with their “anti-features,” and a single pissed-off developer on Reddit posted a three-line script that bypassed their entire “Premium” gate. When we build on frustration, we build on a foundation of spite. And in this community, spite is a high-octane fuel.
I have to ask if I’m a “load-bearing” member of the tech community or just a parasitic process draining the system’s resources. When we participate in enshittification, we contribute to digital entropy. We make the internet a slightly worse place to inhabit. We are essentially building a “Smart City” where the sidewalks disappear unless you’re wearing “Premium” shoes. The market treats parasites like legacy hardware: it finds a workaround and discards them. If that same time was spent building a feature that actually made a business smoother, the users wouldn’t be trying to hack the code; they’d be trying to buy it. My protocol is simple: provide more value than I take. If I can’t do that without sabotaging the environment, I need to step away from the IDE.
The Protocol of the “No-Excuses” Architect
I’ve deconstructed the rot, from tactical CSS sabotage to the strategic decay of enshittification and the extortion of hardware ransom. Now it’s time for the deployment. I can either be a builder of solutions or a builder of hurdles. There is no middle ground. If the industry continues to write “ghosts” into code, it is declaring that it has reached its ceiling. It is saying it has given up on innovation and settled for extortion. That’s a weak way to live and a pathetic way to code.
I don’t write feature-gated code because I want to build legacy code—code that outlives my current job title. I reject the “Ghost.” I will be the one who stands up in the sprint planning meeting and says: “We are not building a frustration machine. If we need more revenue, we build more value. We don’t hold the CSS hostage or the hardware ransom.” I refactor my mindset daily. Every line of code I write is a reflection of my discipline and my integrity. If I wouldn’t want to stand in front of a board of directors and explain why I intentionally broke a native browser function or locked a user’s own car seat, I won’t write it.
The industry is full of “ghosts,” but I refuse to be a medium. I am clearing the technical debt of my character. I am done with the “lazy” way to force a conversion. I’m doing the hard work of building things that people actually want to use. The handshake protocol is waiting. I am going to acknowledge it with integrity, because my system will not time out while I’m busy writing a kill-switch. I’m getting back to the terminal and building something that actually makes the world run better. No excuses.
Call to Action
If you found this guide helpful, don’t let the learning stop here. Subscribe to the newsletter for more in-the-trenches insights. Join the conversation by leaving a comment with your own experiences or questions—your insights might just help another developer avoid a late-night coding meltdown. And if you want to go deeper, connect with me for consulting or further discussion.
D. Bryan King
Sources
- Tiktok’s Enshittification – Cory Doctorow, Pluralistic
- Dark Patterns in Software Engineering – ACM Digital Library
- IEEE Code of Ethics – Professional Conduct for Engineers
- Computer Misuse Act 1990 – Croner-i (UK Legal context for unauthorized access/modification)
- W3C CSS2 Specification: Media Types (Understanding @media print legitimacy)
- Proprietary Malware – GNU Project (Ethical stance on software that restricts users)
Disclaimer:
I love sharing what I’m learning, but please keep in mind that everything I write here—including this post—is just my personal take. These are my own opinions based on my research and my understanding of things at the time I’m writing them. Since life moves way too fast and things change quickly, please use your own best judgment and consult the experts for your specific situations!
Related Posts
Rate this:
#BMWHeatedSeatSubscription #clientSideSabotage #codeIntegrity #crippledware #CSSMediaPrintSabotage #darkPatternsInUI #developerIntegrity #developerManifesto #developerResponsibility #digitalEntropy #DigitalExtortion #enshittification #ethicalEngineering #featureGating #forcedSubscriptions #gatekeepingInTech #HaaSEthics #hardwareAsAService #hardwareLocking #hardwareRansom #intentionalFailure #killSwitches #LeadDeveloper #obfuscatedCode #openSourceVsProprietary #ownershipInTheDigitalAge #predatorySoftware #professionalDeviance #programmaticSabotage #protectionRacket #ReactPluginEthics #SaaSMonetizationEthics #seniorArchitect #SharePointArchitect #softwareEngineeringBestPractices #SoftwareEngineeringEthics #softwareRansom #softwareSabotage #softwareTransparency #softwareUtility #sustainableSoftware #techIndustryDecay #technicalDebt #technicalLeadership #TheGhostInTheCode #userAgency #userAutonomy -
Stood up a new, new mastodon instance, so I'm creating an #introduction post for this server.
I'm a developer/manager with most of my focus on sql (MS SQL and Oracle primarily) and C#. I manage a newly created, small team of devs focused on creating a fully cloud hosted application.
In my spare time, I also study two martial arts: American #Kenpo karate and #Balintawak #Eskrima. I decided to start this server with a focus of hosting individuals interested in either #kenpo or #balintawak.
-
Stood up a new, new mastodon instance, so I'm creating an #introduction post for this server.
I'm a developer/manager with most of my focus on sql (MS SQL and Oracle primarily) and C#. I manage a newly created, small team of devs focused on creating a fully cloud hosted application.
In my spare time, I also study two martial arts: American #Kenpo karate and #Balintawak #Eskrima. I decided to start this server with a focus of hosting individuals interested in either #kenpo or #balintawak.
-
Stood up a new, new mastodon instance, so I'm creating an #introduction post for this server.
I'm a developer/manager with most of my focus on sql (MS SQL and Oracle primarily) and C#. I manage a newly created, small team of devs focused on creating a fully cloud hosted application.
In my spare time, I also study two martial arts: American #Kenpo karate and #Balintawak #Eskrima. I decided to start this server with a focus of hosting individuals interested in either #kenpo or #balintawak.
-
Stood up a new mastodon instance, so I'm creating an #introduction post for this server.
I'm a developer/manager with most of my focus on sql (MSSql and Oracle primarily) and C#. I manage a newly created, small team of devs focused on creating a fully cloud hosted application.
In my spare time, I also study two martial arts: American #Kenpo karate and #Balintawak #Eskrima. I decided to start this server with a focus of hosting individuals interested in either #kenpo or #balintawak.
-
So I didn't do a #Mastodon #introduction post yet, so here it goes
👋 I'm Deepu K Sasidharan, originally from Kerala, India, and currently living in the Netherlands
I'm a polyglot open-source developer and have built some cool projects like #JHipster, #KDash, JDL Studio, and so on. I primarily work with #Java, #Rust, #Golang, #javascript and #typescript
I'm a developer advocate working at #Okta, an international speaker, blogger, and author. I write about #Java, #Rust, #kubernetes and #DevOps
-
A bit of an #introduction
Hi!
I'm a #MedicalImaging enthusiast, starting with degree in #biomedical optics, through working as a developer in medical #computervision and ending with graduating medical school and aiming to be a #radiologist.Privately I'm more about #chess and #dogs , though! ♟️ 🐶
Currently learning #swedish #svenska 🇸🇪
I'll be happy to connect with all the lovely people on #med-mastodon and beyond, I love the idea of #fediverse and what it entails!
-
i am seeking new opportunities in web design, development or ux/ui consultation
💻 🤓 💻
i'm a #developer & #designer specializing in:
– website ui #dev & #design
– #coldfusion #development
– #ui & #web content #marketing #consultationi also create art!
– #illustration
– #collage
– #painting
– #sculptureFT/PT/Remote
PNW-based🤷🏽♂️ 😻 🎨 🏳️🌈 🦄 ☭ △
#WordPress #CF #FediHire #JobSearch #HireMe #HireBrentPruitt #FediJob #Art #Artist #ArtMarketplace -
"I'm a developer. What's your superpower?" - "I'm a fox"
Having a developer's conference in parallel with a furry con is just perfect.
-
"I'm a developer. What's your superpower?" - "I'm a fox"
Having a developer's conference in parallel with a furry con is just perfect.
-
"I'm a developer. What's your superpower?" - "I'm a fox"
Having a developer's conference in parallel with a furry con is just perfect.
-
Out today: “Counties use tax breaks to try to get a commitment from the developer that they’ll use a closed-loop cooling system instead of evaporative cooling. I’m glad counties are using the tools they have, but we only have carrots. We only have incentives.” https://www.texasobserver.org/texas-legislature-data-center-boom-water/
-
Out today: “Counties use tax breaks to try to get a commitment from the developer that they’ll use a closed-loop cooling system instead of evaporative cooling. I’m glad counties are using the tools they have, but we only have carrots. We only have incentives.” https://www.texasobserver.org/texas-legislature-data-center-boom-water/
-
Out today: “Counties use tax breaks to try to get a commitment from the developer that they’ll use a closed-loop cooling system instead of evaporative cooling. I’m glad counties are using the tools they have, but we only have carrots. We only have incentives.” https://www.texasobserver.org/texas-legislature-data-center-boom-water/
-
Out today: “Counties use tax breaks to try to get a commitment from the developer that they’ll use a closed-loop cooling system instead of evaporative cooling. I’m glad counties are using the tools they have, but we only have carrots. We only have incentives.” https://www.texasobserver.org/texas-legislature-data-center-boom-water/
-
Out today: “Counties use tax breaks to try to get a commitment from the developer that they’ll use a closed-loop cooling system instead of evaporative cooling. I’m glad counties are using the tools they have, but we only have carrots. We only have incentives.” https://www.texasobserver.org/texas-legislature-data-center-boom-water/