HNHacker News
TopNewBestAskShowJobs

EdgarVerona

695 karma · joined February 9, 2012

submissionscomments
EdgarVerona··on ‘Limbic Capitalism’ Preys on Our Addicted Brains
This is certainly a difficult problem, and I think that as we learn more on this subject people are going to be increasingly uncomfortable with the answers available to us and what it means for the products we create.

What I feel is that, regardless of regulation on a societal level, it is up to us as individuals to decide what we feel comfortable with in regards to the products we create and the risk of harming others that we are willing to take on. We should be able to acknowledge the fact that - regardless of whether or not addiction is a personal failing or an inescapable biological flaw - intentionally leveraging and profiting off of it is an unethical action. It is exploitation regardless of the nature of the flaw being exploited.

It's complicated, because I think there are many types of products that can't avoid the potential for addictive use. In those situations, we have to ask ourselves whether we're targeting that addictive use, or whether it's an undesired side effect that a user may come across - and in that latter situation, to find ways to mitigate those harmful outcomes. If we want to provide outcomes that help our customers and provide them value, we need to be willing to accept that we may have to create awkward-feeling and profit-limiting mitigations.

Flawed as it is, education and the promotion of people developing self-awareness about their addictions is a strong tool we have for mitigation as long as it isn't something buried where users won't easily find it. Setting limits or ceilings on spending (spending of both time and money) is another mitigation. Avoiding monetization models such as gambling mechanics that inherently exploit addiction is another. Promoting and sticking to direct sales of products for discrete costs is another. But there is still so much we need to learn, and many potential pitfalls.

EdgarVerona··on Using Rust to Scale Elixir for 11M Concurrent Users
Thank you for sharing, and for going so deep on it!
EdgarVerona··on Awesome Pascal – A curated list of Delphi, FreePascal, and Pascal shiny things
There's a tender place in my heart for Pascal. The first language I was taught was Turbo Pascal (I had sort of taught myself QBasic before that, as much as one can from reading the help manual and stumbling through), and the built-in libraries was as close to the liberty and scope of Python as you could get in those days. It really inspired me to continue down the path of software development.

I also have fond memories of BBS door games and software, a large portion of which was built with Pascal.

I digress: but it's nice to reminisce about those old days.

EdgarVerona··on “Ethics” and Ethics
When I read it, it felt more about the banality of evil than an explicit choice to be amoral - he actually explicitly goes into it a few paragraphs down. And it is a genuine problem in our industry. It's very easy for us to have our heads down and not think about how our personal morals misalign with the morals of our company (the latter of which often doesn't have a stated set of principles aside from the examples in the products, services, and marketing it creates). We can be moral people as individuals, but overlook it at an organizational level.

But none of that really comes into play with liberty and freedom of speech in a way that I can mesh. That much is a tangential subject. I'd be more concerned on that end if the article's conclusion was that the government should tell us what is moral, but it is asking us to think more about what we consider to be moral.

If your morals tell you that the way your company makes money is okay, then your morals are in alignment and the article doesn't really apply in your situation.

EdgarVerona··on “Ethics” and Ethics
The article is meandering, but I think at its core it has some key points that are worth considering, at least to me:

1) Organizations are built of individuals, and while the individuals can hold strong moral standpoints, it is difficult for an organization as a whole to do so. It is also difficult for individuals to promote taking a moral standpoint as an organization, or in many cases to even notice the incongruity between their personal morals and the morals of their organization.

(This points reminds me of the banality of evil. And I think it is a valid point, and something we should be on guard about if we want our personal values to match the values of the products we create.)

2) It is easy to dismiss moral concerns in business as being something that the market will figure out for you. That is not necessarily the case.

(I have found throughout my own career that many companies are willing to appeal to a morality that is somewhere along the lines of "whatever we can get away with is our moral boundary." Measuring the morality of a decision by public approval of/success in sales as a result of that decision. That is far removed from actual moral judgment, particularly when public approval is so easily swayed by factors that are separate from whether the subject in question is helpful or even actively harming them. See cigarette lobbying until their false claims were finally debunked and their lobbying efforts exposed in the 90's. [As a side note, I'm curious who would argue that the efforts the cigarette industry made throughout the last century to spread misinformation should be considered "free speech" and their ability to do so a preservation of "personal liberty"? Let's see what pops up in the comments.])

3) We have a duty to think more actively about whether our morals align with the morals of our company, and to make that known if we would like to see that change.

There are other points that might be more interesting to those with a design-oriented focus toward the bottom of the article, but these three were the points that I took home from it.

EdgarVerona··on “Ethics” and Ethics
Nothing in this article mentions anything about government regulation: it is talking about self regulation, and asking your company to consider its moral principles in the face of psychologically manipulative practices. Did you read the article? Or are you choosing to falsely equivocate self regulation based on principles held within a body of employees or an organization with government regulation?
EdgarVerona··on JSON as configuration files: please don’t (2016)
Agreed - really folks, it's not going to be the end of the world if you use JSON for your configuration. Or XML. Or comma delimited text files. As long as you agree to it and you have it documented somewhere, I promise your codebase won't suddenly set on fire because of it.

Now, if you add programmability to your configuration files... that is asking for someone to abuse it and turn a simple configuration file into an abomination. I've definitely seen that happen.

EdgarVerona··on JSON as configuration files: please don’t (2016)
Yes - I have seen at some jobs what a horror "configuration files" can be if you let people add programmability into them.

Many years ago I worked at a job that made an XML tag-based language that was turing complete with the intent of it making their configuration "smarter". It ended up making the entire project much more difficult to debug, trace through, and even understand at all.

EdgarVerona··on What Finally Killed AirPower
Thinking about that theoretical effect on pacemakers and hearing aids makes me glad that we have safety regulations.
EdgarVerona··on Thinkpad X210
I'm sold on 3:2 aspect ratio, and wish there was a wider variety of modern laptops available possessing that screen ratio. I hate looking for laptops and finding the only ones with reasonable specs to have widescreen aspect ratios. I feel noticeably constrained using them for anything other than playing games and watching videos.
EdgarVerona··on Nintendo Asks Mobile Developers to Curb Microtransactions
I think it's important to distinguish between types of microtransactions. For me, where I draw the line between ethical and unethical is when the microtransaction is built to act like a slot machine, with variable ratio schedule rewards.

If a microtransaction provides a clear indicator of exactly what you're buying and its cost - or even if it doesn't but provides an honest and upfront maximum ceiling for how much you will have to pay to get the item(s) you want - then a consumer can make an honest cost-to-value analysis and decide whether or not to buy the product. And I'm fine with that - though the latter example I'm less fine with, it at least provides a mitigation: an avenue for doing that analysis in a rational way and creating a maximum amount of spend that prevents open-ended cycles of addiction and spending.

A loot box or other fully randomized model has no such financial ceiling, and calculations of expected value have to be performed by users entirely like measuring odds in a casino. And casinos, like video game companies, take advantage of the fact that humans are intrinsically bad at that: and that people can easily become addicted to systems that provide rewards randomly and intermittently. And unlike a casino, we ask both children and adults to try to make that on-the-spot assessment when we talk about loot boxes, which as a society we have found unacceptable for other forms of variable ratio schedule-based transactions.

My thought process is pretty straightforward. If, in order for a product to survive, it has to/tries to trick a user into misunderstanding the cost-to-value of their financial transaction, then the product can't actually stand on its own merits and doesn't deserve to exist. Or the product should admit that it is a casino game: and as such it should be heavily regulated, kept out of the hands of children, and I want nothing to do with it.

EdgarVerona··on Nintendo Asks Mobile Developers to Curb Microtransactions
When we see a statement like the one that CyberAgent official made, I can't help but think of the Banality of Evil. We're so focused as a society on economic growth - and surely, these employees have financial targets and objectives they've been given that add to that on a personal level for them - that thinking about the ethical implications of an exploitative business model seems unnecessary, and even foolish. "There's no time for that," one might say, or "that's not under the jurisdiction of my job title."

Well, bad news: it's not under the jurisdiction of anyone's job title. And not considering it brings us to... well, where we are today.

EdgarVerona··on Nintendo Asks Mobile Developers to Curb Microtransactions
Great to hear. So are they going to start by removing slot machine microtransactions from games like Fire Emblem Heroes?

I would love to see big, AAA studios step forward and be brave enough to say that variable ratio schedule-based microtransactions are morally objectionable, and that - even if they've used them before - they have changed their minds and are no longer willing to normalize the practice in the industry. But then they have to put their money where their mouth is and actually stop using it.

(To note, thanks to the paywall I can't actually read this article. I read another site's summary of it. So if they are removing variable ratio schedule microtransactions from Fire Emblem Heroes and other games that they control, good on them!)

Here's a telling quote from the summary I read:

“Nintendo is not interested in making a large amount of revenue from a single smartphone game,” an official at CyberAgent told the Journal. “If we managed the game alone, we would have made a lot more.”

THAT speaks to the heart of the conflict that exists in the industry. There are some people who genuinely don't see the use of variable ratio schedules in microtransactions as ethically compromising, and see not using them as "leaving money on the table." It is this attitude that we need to be aware of: not just as consumers, but as creators of products. Software engineers, designers, producers: we need to think carefully about how the products we make can affect people, and how it can harm them. Creating a product cannot just be about maximizing profit. Software Engineers, at the very least, are bound by a duty to think about and attempt to mitigate the harm brought about by their creation. (See IEEE and ACM code of ethics) "If we managed the game alone, we would have made a lot more" makes me glad that they didn't manage the game alone. It implies that no one in that company is asking themselves about their ethical duties as the creator of a system designed to take advantage of common human psychological weaknesses.

When we boil the question of variable ratio schedule microtransactions down to just "did we leave money on the table," we are saying something about what we picture as being our duty to those affected by our products. And it's not a pretty statement, even if it is unintentional. I'm sure that the people who made that statement don't consider themselves to be "bad people," and I won't even go so far as to say that they are "bad people:" but it does make me think of Hannah Arendt and "The Banality of Evil." It's very easy to get so caught up in what you're assigned to do, what your business/organizational/state goals are, that you lose sight of your other ethical duties.

Doing what's right isn't about justifying whatever you can think to create, or even whatever people won't happen to notice or complain about (i.e. what you can get away with). It's about doing an honest evaluation of the ways in which the products you make can hurt people. It's about expressing some level of empathy - thinking seriously and honestly about how you would feel and what would happen to you if you were one of the people that were to fall into harmful cycles that the product encourages. And it's about accepting that - even if you believe that the person falling into it had a "choice," that you were intentionally injecting yourself into and influencing that choice through techniques that we as a species know to be psychologically manipulative. (and indeed, we know they are effective as tools of psychological manipulation because if we didn't, we wouldn't be using them)

EdgarVerona··on Talent Is Everywhere, Opportunity Is Not
This quote within the article really drives the point home:

"The goal of inclusion work is not "More black folk!" Or "More women!" The lack of black folk and women is a symptom of the root cause: opportunity to succeed and thrive is not evenly distributed."

I agree entirely with this statement, and I have seen it happen in both poor white and latino communities that I have lived in during the course of my life. There's a lot of intelligent and capable people out there who aren't going to get their foot in the door: they're never even going to know where the door is.

EdgarVerona··on 40M people with diabetes will be left without insulin by 2030, study predicts
Something important that I think is worth noting is that you can reverse the symptoms of T2 Diabetes, but it does require a lifelong change of lifestyle. If you go back to your old lifestyle, those symptoms are just going to come right back. I know to some it may be obvious, but I think it's worth stressing this. When people say "reverse," they're talking "in remission." The symptoms are waiting to return if you start fucking up again. That being said, it is a much better approach than the alternatives.
EdgarVerona··on Ask HN: Have you ever regretted working on a product?
That's what I'm hoping we can change. When I think of Engineering, I think of trades that tend to have a firm grasp on ethics and take the consequences of what they build very seriously. I know that organizations like the ACM and IEEE espouse those same virtues, and I think they are not only worthy virtues but also important. Something worth being uncomfortable - or even discarded by less ethical companies - in order to defend.

Ethics not being a desirable quality to some (many? That seems too bold to assert) businesses is ironically part of the reason why ethics is so important to hold onto as an engineer. Some businesses would be elated to find software engineers that have discarded their sense of ethics entirely, to the profit of themselves and the harm of our society.

EdgarVerona··on What Makes .NET Core So Special?
That would have been/would be fantastic. I'd be all in on that.
EdgarVerona··on What Makes .NET Core So Special?
Awesome, glad to hear it!
EdgarVerona··on Ask HN: Have you ever regretted working on a product?
Good on you for putting your foot down! You not only learned from your past experience, but you also are setting a good example for other software engineers who may not be thinking about their ethical duties.

People entering the industry need to be thinking about the consequences of the products we make, and I feel like that's something that can be led in part by the visible example of experienced engineers like yourself - ones who have experienced being used for a harmful end and now are willing to both speak up and stand against it happening to them again. I know I needed this very same wake up call when I was a much younger engineer. I feel shame every time I speak about my involvement in harmful products and my cowardice in the moment, but that shame also reminds me of how important it is to talk about it, to try and make sure other engineers think about these duties that are so easily overlooked. And to remind myself that I don't ever want to be in that situation again.

EdgarVerona··on Ask HN: Have you ever regretted working on a product?
Thank you for sharing that story. I think it's important for young software engineers to see and hear about these stories, and for those of us who have experienced them to share them.

Software development is such a rush when you're young, and it's easy to be blinded to other concerns by the thrill of it. Those of us who have had this desire manipulated for malicious ends need to keep speaking up, to remind people that there can be real harm done by our actions and that we have to be thinking not just about the interesting problem spaces we're exploring but also what the product we're making is doing, what it's intent is, what effect it might have on people.

Please keep sharing this story to young engineers as you come across the opportunity to do so. It's a sobering truth about our duties that often goes unspoken.

EdgarVerona··on Ask HN: Have you ever regretted working on a product?
Other questions to ask are:

* Would this product exist without the malicious use cases?

* Can the company sustain itself without the malicious use case?

* Are there ways to mitigate the malicious use cases, and could they be reasonably implemented?

* Is the true intent of the business - when you assess it honestly - for it to be used in the "good" scenario, or in the malicious scenario?

* Are the malicious scenarios being reinforced/rewarded?

* What portion of revenue is directly caused by the malicious use cases?

* Is the company marketing or appealing to the malicious use cases? Are they trying to actively warn against/discourage them?

* What are the worst case scenarios of the malicious use case? Are they theoretical or real?

* What are the best case scenarios of the "golden path" use case? Are they theoretical or real?

And we also need to pay attention as we answer the questions above, looking out for if/when we make shallow justifications rather than honestly assessing the answers to the questions above. Look out for situations where our response is hedged by an excuse that's irrelevant to your ethical duties as a software engineer, such as:

* "but we can't leave money on the table"

* "but people would lose their jobs if we didn't do this"

* "but this is what our competitors do"

* "but if we didn't do this, someone else would"

* "but it also causes [theoretical/unintended side effect that sounds good on paper]" (particularly important to watch out for when that unintended side effect is an oversimplified version of reality)

* "but it's not our choice how it is used" (particularly relevant in situations where the business model relies on the malicious use case, and/or there are opportunities to mitigate the harmful use case that are intentionally going unexplored... or situations where your product itself is using techniques such as behavioral conditioning to train a user's choices)

EdgarVerona··on Ask HN: Have you ever regretted working on a product?
Thank you for sharing that. I hope that you continue to share this story.

I think you can still do good with the situation by doing exactly what you're doing now: talk to other software engineers about this often overlooked duty. Talk to young engineers about the need to examine the ethical implications of the products they are making. These stories of shame are something we need to share with each other, to stress the importance of thinking about the consequences and intent of what we make.

I remember first coming into software development, creating software was a rush. I was a junkie, getting high on solving problems and working against tight deadlines. This is a common experience I've seen in many new software engineers: but when you're getting high off of those factors, it's easy to not even realize that you have to be asking yourself questions about what you're making. Stories like yours can be a bucket of cold water, something that helps to wake people up to the other obligations that are part of our duties as software engineers.

EdgarVerona··on Ask HN: Have you ever regretted working on a product?
Good on you for making the right move.

I think we as an industry need to stop stretching for excuses for why greedy behavior might unintentionally do something good. It's not a worthwhile cause and it doesn't justify the behavior if the "good" is a theoretical and unintended side effect. The "good" being theorycrafted on the nature of this product is indeed both highly speculative, oversimplifying of the human cost of changes to this economic model, and is obviously not the purpose of the product. That "good" is contingent on and integrated with a number of factors too complicated to boil down to a single sentence: it's something that looks good when oversimplified and makes ourselves feel better if we try not to think too hard about it.

When we ask ourselves whether a product we work on is ethical or not, we have to account for the intent of the product, and not merely stretch to find theoretical ways to justify it to ourselves. We do need to think about unintended side effects - particularly when they could harm others - but we shouldn't be using our theoretical and simplified best-case scenario of unintended side effects as a way to justify the intention and practical use cases of the products we make.

We should ask ourselves: if the "good" of an unintended side effect could be cut out of a product and we'd still make it, is it actually the good of a product? Or is it an excuse we're making to ourselves to make us feel better?

EdgarVerona··on Ask HN: Have you ever regretted working on a product?
Definitely - and the intent of the business model and the business itself. I've worked on products before that on the surface (and even what I was told by the folks running it) could have done good. But the company had no intention of using it for good. They had every intention of lying about where they were really making their money though.

I feel like all the justification we see in our industry of "it's just a tool, it's not our fault if it's used poorly" can often end up being a variant of the banality of evil. What if its most obvious use case is the malicious one? What if the company paying you to make it has the malicious use case of the tool in mind? Would the company and the product exist/be sustainable without the malicious use case? Are there ways to curb the malicious use case that are being ignored - intentionally or not? We've got to start asking ourselves these questions. The ACM and IEEE would insist that it is part of our core duty to be asking these questions.

EdgarVerona··on Ask HN: Have you ever regretted working on a product?
Yes. This is so true. This is something we need to teach young software engineers - to try and identify the true business model from the model that the company is claiming to incoming employees. To question what you've been told at face value, and to be brave enough to walk away or put your foot down when you find out you've been had.

I've been there. I often wonder how many others in the industry have.

EdgarVerona··on Ask HN: Have you ever regretted working on a product?
I've talked about this in a few places before... when this subject comes up, I try to talk about it because I think the ethics aspect of software engineering often goes overlooked in our industry. I'll copypasta from the last time I spoke about it.

It's coming up on ten years now since this happened. I was a young, naive software engineer, addicted to the adrenaline rush of solving problems on tight deadlines and not giving much thought to what those solutions were being used for.

The company I was working at suddenly folded, leaving me looking for work. The father of an old friend of mine hit me up, telling me about this new idea he had for a service that doctors' offices would use to contact patients, or for universities to contact their students, all over SMS. For some reason, he was very insistent that it be done over long codes. I didn't understand why at the time and was too naive to press him on this odd requirement. Fuck does it matter if a university texts you from a long code or a short code?

I decided to go for it, and made a prototype of a system that would allow folks to automate sending SMS messages to all their clients (what I was told was the "v1" on which the more interesting features would be layered). He told me he already had some clients, but said they were from "the other side of the tracks."

I will be honest, I was too scared to call him out. I was prepared to take the cowards' path of not asking so I didn't have to know: a fact that still fills me with shame today. It was another guy working there on a separate project who heard him and and pushed for what he meant.

Finally he admitted what the whole thing really was. There were no doctors' offices, no universities lined up. Just porn sites looking to spam people over SMS, with long code numbers so it looked like it was coming from a person and not a business.

I flipped the fuck out, partly at him for decieving me and partly at myself for the fact that I was so willing to not even fucking ask when he said that shady shit.

I told him to fuck this and everything, and walked out the door.

About a week later my friend tried to resurrect the originally proposed business without his dad, and I reluctantly said I would if his dad wasn't involved. But he wasn't in a position to actually keep him out of it, and I walked away for good.

If you are reading this and you are a young software engineer, please do not follow my path. Ask the hard questions. Read the ACM code of ethics and the duties to society that it demands of you. Your job is not just to solve problems: you may be called on to be the one to put your foot down for the sake of ethics, and it is so easy to turn away from that duty when money and comfort are on the side of shutting up and doing as you are told.

EdgarVerona··on What Makes .NET Core So Special?
Oh, the dependency injection definitely works independently of ASP.NET Core - it's just something frequently talked about in tandem with it. Just wrote a console app that used it a couple of days ago.

I don't know about the current status of the GUI layer, other than that I've heard plans for WPF to be ported over to .NET Core. I don't know if or when that will actually happen.

EdgarVerona··on What Makes .NET Core So Special?
I think it's because C# and (most of) its ecosystem is a joy to use compared to many languages that are popular with large corporations. Having that ecosystem and that particularly delightful language become cross platform is a welcome change, and also a welcome sign that Microsoft is willing to open up a bit more than many of us were expecting.
EdgarVerona··on CRISPR is Going to be Replaced
This reads like a pump-and-dump article.
EdgarVerona··on It’s better to be born rich than gifted
To me, it's not so much that they shouldn't be allowed to do that - it's just that we need to recognize the advantage it gives.

These statistics should give a person pause when they talk about "bootstraps" or when they hold a Calvinist perspective that a person not being successful somehow "deserved it." It doesn't mean that we need to have some sort of totally even playing field: but it does mean that we shouldn't pretend the field is even - even if the actionable result is just to treat poor and/or unsuccessful people with more empathy and compassion than we might have previously. And perhaps a measurement more of self-examination when we decide (consciously or unconsciously) that we are "better" than others due to our success.

← PreviousPage 3 of 7Next →