Analogue Pocket Hate Story
endrift.com
endrift.com
Reframe a fixed price as "this will be X amount of hours". Invariably, nobody knows what kind of "gotchas" will be encountered during dev, and with fixed price, you're absorbing that risk yourself. As an hourly rate, that risk is borne by the client. This also applies to shifting scope; if the client shifts scope mid-way, they will bear that cost in an hourly setup instead of you.
If you can bill $1M for a project because you're a worldwide expert, do so, otherwise bill by hour/day/week because you should already know that deadlines will be broken and the spec you are given when you sign has nothing to do with actually is required to ship the product.
It then sounds like some other timelines were shifted, but rather than engaging with the company to learn what was going on, they silently invented more 'disrespect'.
Building a product is hard. It's also expensive. Many many companies go out of business trying. The company being somewhat reasonable with money, and moving other deadlines around to accomplish their goals, is not evil in and of itself. It sounds like OP needs to learn how to engage constructively, communicate their concerns and questions, and empathize with the people they're working with a bit.
Yeah, a $1 to $2 raise, how generous. What I got out of this article is that the author knows the value of their time. $20,000 for 4 to 6 months of work for a software engineer is an insult. They might as well ask him to work for free.
Analogue was hoping for a screaming deal on this software. He was right to walk away.
Analogue wasn't looking for SV contractors, they were looking for contractors in any location (in this case, a remote contractor). That Endrift happened to be located in SV changes their specific appetite for the offer, but doesn't make the offer unreasonable or disrespectful, either.
> Analogue wasn't looking for SV contractors, they were looking for contractors in any location (in this case, a remote contractor). That Endrift happened to be located in SV changes their specific appetite for the offer, but doesn't make the offer unreasonable or disrespectful, either.
I wouldn't expect to get cycle-accurate FPGA emulation work (by one of a handful of experienced experts in simulating the original hardware!) done for ~$30 USD an hour from basically anywhere on the planet. Contracting out of Eastern Europe or South America you'd end up paying about that much for a mostly incompetent web dev -- for what Analogue wanted, there's no real way to describe it other than "hoping to hit a homerun on an absolutely insanely unreasonable offer".
This is deeply specialist knowledge that Analogue is looking for.
Someone capable of doing a good job on this can make FAR more doing something else. $20K is a joke.
Her time.
The author of the article gave an estimate of hundreds of hours across 2 to 4 months and Analogue's valuation of that time was $10k - for an expert in the domain working in software. That number is an insult. Even doubled it's quite bad.
That's exactly what she did. She didn't lead by demanding a specific number, but in some cases, that's actually pretty good advice, it can be good to let companies make the first offer on salary.
Otherwise, she engaged with the company, told them upfront that $10,000 wasn't enough without leading them along too much; they came back with $20,000, which sounds like it still wasn't a great offer for her, but she engaged a bit longer to see what the context was and whether or not it would work.
When the company came back with NDA demands and demands around her own Open Source projects that she wasn't comfortable with, she decided that the job wasn't for her, and (imo, very respectfully) turned down the offer: https://endrift.com/resources/post-assets/analogue-13.png
Writing a blog post about this process is allowed, I don't see anything entitled or disrespectful about that. NDAs and non-competes would make me very nervous if I was contracting with someone, particularly if I'm a domain expert with a popular Open Source project in the field that they're hiring me to work on.
The other side of this comment thread is that she very factually described a negotiation process she had with a company, described why it went wrong and why it didn't work for her (she feels her time is worth more and wasn't being valued enough, among other issues), and described graciously breaking off the job offer on what seems like good terms to me -- and people are angry about that outcome?
> This reads like a case of 'all about me'-ism.
No, it reads like someone negotiating a salary and terms and having a clear view of what they think they're worth and when terms seem bad to them, which is a normal thing that people who look for jobs should be comfortable with. Ultimately, when you're negotiating a contract it does no one any favors for you to do anything else other than advocate for yourself during that negotiation process. Looking at company culture (trademarking fgpa, claims about emulation, etc), looking at side-project terms (delaying releases of an Open Source project), and looking at salary are all part of that -- and being honest about how you read those signals is something that good companies want. It doesn't help anyone to mask these objections.
I get a little frustrated when I see people describe normal negotiation as entitled. This article is how job searches and hiring processes are supposed to work.
In SV, the company is from HK. If that offer was ridiculous too, she should have said as much.
I’ve been offered flat 200$ for jobs that cost >10k$. Your clients might not know the price of your labor, it’s your job to inform them.
Founded is a typical weasel word because people tend to be more trusting of american companies.
$20,000 for 300-400hrs of work, as estimated, quoted and documented by the author.
I don't know why we are trying to misinterpret the story so hard in this thread. And I don't know how much more entitlement we can possibly have as profession on this continent, where we find $50-$66USD per hour of optional, interesting and challenging, comfortable and remote work, a perceived insult worthy of HackerNews front page. This person was not forced at gunpoint to work beneath their sustainable means. They got an offer, they rejected the offer. I give the author a credit of self-awareness for noting this is indeed a lot of money for a lot of people; less so for most of us on HN it appears.
Was there some public badmouthing of this developer by Analogue or something? Because if not, this is possibly one of the most petty and entitled things I've seen posted to do with software development in a while. Don't want to take a low-ball offer? Don't take it. Posting what look to be private conversations online to shame someone because they didn't offer you enough money for something you have full choice to accept or ignore? WTF?
It's OK to both acknowledge that software engineers are extremely privileged and often divorced from the realities of other workers, and to acknowledge that we can use our privilege in ways that can help people (and in fact have something of a moral responsibility to do so), and finally also to acknowledge that we have market rates as an industry and we don't have an obligation to give labor away to companies who want to ignore those rates. Nobody working at McDonald's on a minimum wage salary is going to benefit from you under-charging for your consulting/contract work.
If you want to help those people and acknowledge your privilege, there are a lot of ways to do that without undervaluing yourself. Direct your generosity towards under-privileged people/organizations, not towards companies that are even more privileged than you are. It's easy to accidentally misdirect responses to guilt (even legitimate guilt), and undervaluing salaries out of "fairness" to other workers is a misdirection of guilt. The fact that Amazon mistreats its warehouse workers is not helped by Amazon programmers allowing Amazon to pay them less for the same amount of programming labor. It would be helped by activism, by possibly quitting outright so the company is no longer getting the labor, or by publicly advocating for the other workers, or by donating a lot of money to lobbying groups to help raise minimum wage. But it's not showing solidarity with low-income workers to give more money to your employer.
They gave an estimate, company made an offer; they asked for more, company doubled. They decided it still wasn't worth it. Awesome. Nobody was forced to do business together. Why are we still trying to make excuses as if there was some pressure to do un/underpaid work? I did not see it in the very polite and understanding screenshots. Am I missing something that's causing this outrage? why is this even a thing we're talking about is still my personal question in this thread :D
Edit: You know what; I re-read to see if I'm missing something, and indeed I did: though author insists, multiple times, in bold letters, that company mandated six months, based on screenshots, company in fact relented and agreed to one month difference. Which author themselves indicate was far less than normal between-releases period.
1: https://endrift.com/resources/post-assets/analogue-12.png
Nope, I'm out, I have no rage to spare at this particular "injustice".
This comment is just so ridiculous I don't know where to start.
Let's start with entitlement, not once did I say things like the author or software engineers in general are "entitled" to anything. My words are about reality, reality is, $20,000 is not enough money to get me to do any work for longer than a month because I can walk down the street and get a job that pays me more after a 5 hour interview.
Let's talk about having the "privilege" to do interesting work remotely. Aka, the privilege to donate your time to someone else's business. I can do interesting work on my own thank you very much, I don't need $20,000 from some company for the privilege to do interesting work, I can open my laptop and do it and I own the result in the end.
If making a lot of money causes you to feel guilt sort your issues out.
* Not taking an offer because it's not worthwhile - more power to you and the author. Zero issues or concerns from me. I wouldn't take it either.
But I wouldn't make a thing out of it either! The person is clearly comfortable in their day job, they have hobbies they enjoy, and they had an offer they negotiated then rejected (eventually; after the other side followed-up; apparently only companies are bad when they ghost employees, employees not replying with change of heart is fine:). Life.Is.Good.
* A well-to-do random person freely not taking a random $20k contract from a random company making top post on Hacker News with outrage at the "disrespect" and the awful exploitative business practices and evil leaders? Yeah, that's entitlement.
- $10,000 for four months is the equivalent of a $30K/year salary. That would have been low for me when I lived in Tampa, Florida, in 2000; in Silicon Valley in 2020, you could make more than that working at Panda Express. (This is not an exaggeration for effect, I promise.)
- doubling it to $20,000 is a $60K/year salary equivalent, right? That would have been just fine when I lived in Tampa, Florida, in 2000! In Silicon Valley in 2020, it is…not super great, let's just say. BUT!
- problem #1: "equivalent" is a dodge in practice, since actually it's, well, just $20K flat. WHICH LEADS TO!
- problem #2: the "extra six months" the article referred to the employer trying to add on after the fact did not refer to adding more money to the contract. Now we've gone from $20K for four months to $20K for ten months -- which is actually worse than the original offer -- and at this point we are handily back to "screw this, I'm gonna make more money slinging orange chicken at the mall".
tl;dr: the problem is not with the author wanting their time to be properly valued. "But building hardware is expensive, man" is not sufficient justification for this kind of nonsense.
The offer was not (as I understand it) $20k for 4 months of life, it was $20k for estimated 300-400hrs of work, freely estimated by the author themselves. Which comes out to $50-$65 USD/hr. Which is atrociously low for Silicon Valley consultant rates, and quite high in much of the world. So it may well not be worth author's time, but does not on its own indicate atrocious personal intentional malignant disrespect worthy of international outrage.
(everything else, I'm leaving intentionally aside - I understand a small snippet of one person's perspective about the issue, and nothing about the framework of hardware development, where I hear margins to be slimmer than slim, unlike in the wider world of purely-software development).
I don't think $50 an hour is a reasonable salary for consulting period. An experienced/senior developer working full time for a company with benefits in a cheap area should still (off the top of my head) probably be looking for at min $100,000 to $120,000 yearly salary (roughly $50 an hour). Depending on the situation you might be able to get more than that, I'm sure I could find people who would tell me that my estimation is also low. It is a very low salary for developers living in San Francisco, but let's leave that area out of the conversation for a second since it's something of an anomaly.
When you consult/contract, you are now paying for your own health insurance, your taxes are now more complicated, you are paying for most of your own gear, your situation is more complicated and your work is short time, you don't have the same level of job security, you are more self-directed, and you are taking on a greater amount of responsibility for the success of the project you're working on.
You need to charge more for consulting work than you charge for normal full-time development.
And all of that even ignores that at the point you're doing consulting work, you're doing it because you're likely a domain expert. A full-time domain expert in a company should be making way more than $120,000 a year, and similarly should be charging even more for consulting work. Contractors undervaluing themselves and choosing to charge too little is a pretty big cause of burnout and failure for people who are trying to get into that kind of work. I would not entertain for a second a $50 an hour rate for contracting work even if I lived in a rural area with cheap housing.
Everyone's situation is different, maybe there are people who can make that work and it makes sense for them, but on average people undervalue what their salaries should be when contracting. The overwhelming advice that I hear from contractors is "take what you think is fair to pay yourself and at least double it to get your minimum rate." Huge cause of burnout for people who get into self-employment, they give away their work for too little and then can't keep up because they're over-stressed and overworked.
I'm in Canada. Experienced developer salary under 100k CAD is the norm. Consultant rates of $100CAD/hr are not unusual.
And then there's the rest of the world.
I have no beef with author for rejecting an offer that didn't make sense to them.
I am however disappointed for eagerness to ascribe malevolence and disrespect, and demonize a company whose side, balance sheet, and options we don't understand even remotely. I've read the screenshoted messages and they all seemed polite & understanding; no pressure, no offense. They made an offer and it didn't work out, life goes on for all involved - unless, and this is my personal daily fear, an internet mob decides some offense was committed. I expect and hope for more from HN.
Is that what happened here? The second most popular comment on this page starts with, "this reads like a case of 'all about me'-ism."
$50 an hour is low for programming consulting in America in general, which is where Analogue is hiring. That doesn't mean I hate the Pocket, but it's worth just saying that it's not a competitive salary, and if you're in the US unless you have a very good reason you should think extremely carefully before you accept an offer like this, it's below market-rate. I think it's reasonable to read into that offer and say that Analogue is undervaluing the work that Endrift does (maybe not on purpose, but in practice pricing something below market rate is literally undervaluing it). I feel confident that Analogue knows what average market rates are for programmers in America. Again, doesn't make me hate Analogue or the Pocket overall, it's just a thing they did.
But the context of this conversation is a set of top level posts that are immediately accusing the developer of being entitled and of the post of being petty and mean-spirited. Who are we calling out here? You have a very different reading than me of what kind of HN culture is being demonstrated under this post. I'm not seeing a pile-on of Analogue from HN, I'm also not seeing a set of top level comments urging context or describing that this is a normal negotiation process -- what I'm seeing from people calling out the salary as under market-rate is that they are primarily either pointing out an accurate fact about US market rates, or stepping up to defend an author who shared their honest experiences of a US company offering them lower-than-US rates, and then immediately got called selfish/entitled for doing so.
It's a strange jujutsu that we're talking about whether or not people are piling on Analogue too hard as a direct child thread under a top-level comment that says the salary was good and that the post author has a problem with communication and empathy.
Amount Is based on team members, friends and colleagues working at large established companies. I imagine price there may be more depressed than at small successful rapidly growing companies - but percentage wise, though they make minority of HN, boring dev jobs at large companies are majority of actual Devs. Canadian averages are notoriously hard to get but based on linked in and glass doors, there seems to be a lot of dev jobs well under 100k.
(fwiw, based on sample size of n=2, my friends who are Canadian Devs but on primarily American companies, effectively get American salary grandfathered. They both acknowledge its far higher than what they previously had and what they might get otherwise in market)
It is my understanding that e. G. UK is largely the same - development is a white collar office job like any other, not a rock star exotic occupation it appears based on HN to be in US.
Very cursory search shows median US developer salary (not average vocal HN audience salary:) to be 100k US and UK average dev salary to be fraction of that. These may or may not be accurate, but most dev jobs are far more boring and standardized than HN average.
I have a senior dev on my team at 35k€/year. Prices in SV != Prices in the rest of the world.
First they said it wasn't going to impact the author's open source work.
Then they started talking about delaying mGBA development until the product was released.
Then they started talking about delaying mGBA development until many months after the product was released.
Would you similarly recommend that if a employee was to find a way to go the extra mile and really make a impact on the business they should hold back? After all, if businesses think people are going to throw labor at them they didn't ask for, they are going to have a tough time.
I'm mostly joking but people are told as children that they should work hard and can expect their boss to notice and reward them. It isn't their fault that lots of people abuse that social construct, they are just naïve.
This is a case of "Analogue has a history of being shady", and their attempt to negotiate this on Discord while offering a miserable pay is one more proof of it. There's maybe 10 qualified people on earth to make a cycle-accurate GBA BIOS, and they offer 20k for exclusive work for 10 months ?
Turns out they only needed one, and got it done.
Do you understand the work that was asked?...
I don't read that as accepting the offer, I read it as continuing the negotiation.
" 6 days later I was told that the doubling was approved and we could sort out the fine details "
Like ok, we're now past the payment negotiation stage, now onto other details.
The person in the article clearly(to me) agreed to an insuficient amount of money, and then wrote a blog post to complain about it.
There is something sublime, while simultaneously prosaic, about missing that everyone's actions are about themselves, especially in the business portion of life.
You can find allies and mentors and trustworthy partners. But ultimately, you are the only one who can decide if your next action is the right one, for you, your career, your mental health. Thus it is always about you. No one else can be a bigger advocate.
I'm not sure if the parent comment realizes that the author didn't actually accept the job? It sounds like parent believes she cut off work or something, which isn't at all what the article describes; it describes a pretty standard run-of-the-mill negotiation process that the author eventually cut off, and that left the author with a sour taste in her mouth about the company culture.
None of that is entitlement. If you go into contract work, you are going to get a million sob stories from a million companies about how building products is hard. Often those sob stories will be paired with real red flags like this article describes (leading with aggressively low offers, asking you to put off other work you're doing, etc). Building products is hard, but also paying rent is hard, and so you have a duty to yourself to advocate first and foremost for yourself during negotiations.
It's not kindness for you as a contractor to take on work that doesn't fit you or that you don't think is sustainable; you're setting yourself up for burnout and failed projects if you do that. And burning out in the middle of development, not being able to make rent, having to ignore other clients, all of that also makes products hard to ship. All of that is also a recipe for going out of business.
It's professional to treat yourself and your time and skills with the respect they deserve and not bother with lowball offers. It doesn't exactly come across as professional to me to throw all this online for the world to see because apparently they either didn't want to pay (or couldn't afford) what they needed so offered far less than was needed. Maybe there's some subtext here which I'm missing or isn't explained? Did this company disparage her conduct or skills publicly or something? The level of the response (even how it's called a "hate story") just comes across as weird and overly petty to me.
Telling people to value their time and effort is laudable. Lambasting some company or person in public because they offered you less than you were worth is not. If I contacted you in private and offered you $1000 to design a GBA emulator (not quite the same thing, I know) and you thought that was far too little money, is that worth posting screencaps of, or maybe you should just tell me "really that's so low of an offer that whether you intend it to be or not it's sort of insulting, as I would be working for so far less than I value my time"? That seems like the most useful thing to do for all involved. Maybe something good comes of it, maybe nothing changes, but at least it's not just one person pointing at another and doing the equivalent of saying "look at them and laugh because they had the temerity to try to pay me for work, but just not enough". I mean at some point the person she's talking to literally says in the screencaps "No hehe this is just a personal conversation".
It's not screwing someone over to make an offer of work, no matter how low. Some people are happy to do certain types of work for free. Others want to be paid. The amount they may want to be paid might be based on many things, including market rates and cost of living in their area. Making an offer to someone is never screwing them over, nor even trying to, as long as they can freely reject it. The whole idea that them making an offer, no matter how low, is some sort of way of screwing someone over is just totally weird to me, and I'm not sure how people are even coming to that conclusion.
Because Endrift also isn't really a random person, she's in charge of some extremely public, fairly lauded emulators in the retro space. Analogue is releasing one of the more anticipated and public hardware projects in that space, and Endrift within that context is talking about their experiences with Analogue the company -- including some reasonably relevant details like that the company asked them to delay a release of an Open Source emulator.
Back when I was in college, people in my department shared what was being offered by companies that came over to job fairs trying to hire us. We talked about the hiring processes, the interview processes, and what their culture was like, because we were all part of a community of people who were going to be interacting with the same companies. Unless it was under NDA we didn't keep a ton of that stuff secret, we wanted the people we were going to class with to know what companies were worth pursuing and what companies weren't. So sure, this doesn't warrant a NYT article, it's not an accusation that means Analogue the company should be burned to the ground or something, but don't you see any value in a prominent voice in the emulation community talking about (on a personal blog) their experiences with a company that is a very public presence within the emulation space?
Some additional context here is possibly warranted that the author didn't share this post to HN, somebody else did. I feel like often with worries about things being "too public", there's a weird phenomenon where communities being open enough that people outside of that community can look in suddenly means that anything posted publicly is expected to be intended for a global audience or planned out as a potentially viral piece. But in the same way that I don't think the negotiation process here is worth as much debate as its seeing in the comments, I also don't think the author reflecting on that experience publicly is weird, at least not given the context of the general news about Analogue happening right now, and at least not given the context that this is the person running mGBA. I certainly don't think it's weird enough that it warrants publicly claiming that the author is lacking empathy.
> even how it's called a "hate story"
Someone else has already mentioned, but this is a reference to a video game title.
I don't really have a problem with someone saying a company low-balled them. Honestly, the fact that she took screencaps of what appear to be private conversations (where the other side specifically refers to it as a personal conversation) and refers to specific people at that company is where I think it goes from being something equivalent to "that time Analogue tried to hire me but vastly underestimated the cost and my value, so I turned them down" into something else. If the author had written something along those lines, even at length, then I don't think the vast majority would have a problem with that.
Instead what we have is something that seems far more personal, and far more targeted as specific people, but without context as to why that's warranted, and not necessarily shared with some people with like situations, but for the world to see.
> Some additional context here is possibly warranted that the author didn't share this post to HN, somebody else did.
The author posted it online. It wasn't some private conversation (although she doesn't seem to think posting private conversations is worth noting enough to justify from what I can see), but pushed out for the world to see. Google's going to index it, people are going to share it.
> there's a weird phenomenon where communities being open enough that people outside of that community can look in suddenly means that anything posted publicly is expected to be intended for a global audience or planned out as a potentially viral piece.
I think perhaps people show be more careful what they say online in open locations. These are not private conversations. Other people see them. When you say something in an open forum it's the equivalent of carving it into a tree in a public area in the real world. Any expectation that it's private is ludicrous, no matter how many people seem to fall back to that excuse when called out for something they've said. Perhaps people just should act as they would like to be treated in public. The author, by making a private conversation public deserves no consideration that her public post wasn't intended to be seen by the world, in my opinion.
> But in the same way that I don't think the negotiation process here is worth as much debate as its seeing in the comments
I wouldn't think it was really worth doing an expose on either, but the author seems to think it worth while. The negotiation is rather mundane. It's that she decided to air it to the world which I think is the more interesting thing, even if it's interesting in a way that I think doesn't speak well of her.
> this is a reference to a video game title.
I noticed that, and I think that's a bit less objectionable because of it. It's still kind of ick though, and I think speaks to a lack of care regarding the situation.
In case it hasn't come through as obvious, my real objection to the behavior is the airing of private conversations with individuals for no useful reason. That the conversation seems utterly mundane but is presented otherwise makes it worse in my eyes, because there's no obvious reason from the conversation either.
I think I've written enough on this. The only reason I've written what I have so far is because people keep equating her behavior to less objectionable comparisons, but to me it seems clearly different when it's public on the internet, aimed at specific people, and uses screencaps of a private conversation in a way that I think would make most people feel violated if it was put online like that, regardless of whether they said anything objectionable in it.
I can agree to disagree on things, but I will leave out by saying that the Internet is a global medium that spans multiple continents, cultures, and languages. If the expectation is that everything posted online needs to be thought of through the lens of a global press release, the end result of that is you are going to have a lot less interesting content online and lot less culture.
There is a difference between a truly private post (meaning that no one is supposed to see it) and a targeted post intending to primarily communicate with a specific audience. When I write posts on HN going into programming details, I don't preface them for people who are unfamiliar with the concept of programming. I don't write in the same style on HN as I do in other contexts, and I don't engage in the same topics. All of that stuff is public, people can correlate it if they want to, in which case I'm going to kind of shrug and kind of look at them weird.
This may just be a personal opinion, people are welcome to disagree with me on this, they can disagree with me on anything. But I think transparent communities with their own circles, memes, cultures, and concerns are a good thing, and making those communities more insular, or demanding that they constantly explain themselves to people who don't understand the references, have a background of their concerns and internal debates, or recognize the people involved -- I think that's an unnecessary burden to place on people.
"All about me"-ism, what a complete crock. Made-up MBA word salad used to shame a person for daring to exercise a shred of self-respect and autonomy, instead of being treated like a doormat.
> Building a product is hard. It's also expensive... and empathize with the people they're working with a bit.
Sorry to be a hater, but I don't care. I'm not going to cry myself to sleep at night because there's one less "product" to consume in the world. One less thing in the world that has my name tucked away in a measly, legally-obligated "About this software" window nobody views, for work that will get thrown in a landfill and forgotten in less than a decade. Sound the alarms everybody, there's one less toy in the world! And if it wasn't for this entitled person, you would have had it faster, with one more feature, for the same cost: the most important things there are. I bawl at the thought.
No, I truly don't care that building your product is hard work or that you have thin margins. Because if I did, I'd own stock. Simple as that. So until then, all that hard product-building work? That sounds like your problem. Not my problem.
Some companies have money and want to complete a project, and some developers can do the work and want to be compensated. The process by which the compensation is determined involves negotiation. That is a two-sided process. In none of the presented screenshots did the author actually propose what she thought was a fair compensation for the work. She suggests $20K may work but that is the moment to say what she thinks is fair or what would have been worth her time
A lot of people who do emulator work are not based in SF. Many are in other countries where $10K stretches a lot further. The actual offer is not really insulting if the company didn't know she was in such a high COL area.
In the case of GBA emulator work, there is some sort of market. For example, MVG wrote the emulator for the Shantae re-release and there's no reason to believe others can't do the same.
If the author straight up made a counter, we could judge the reasonableness accordingly. In absence, it seems like entitlement.
Why isn't it entitlement on Analogue's side to offer so low a bid and with ridiculous restrictions?
Because at the end of the day it's just an offer. She should have just said no, or named a price that was appropriate. The blogpost is literally about nothing, just a failed business transaction like millions that happen every day, but it gets weirdly personal for no real reason that I can see.
No there isn't.
> She suggests $20K may work but that is the moment to say what she thinks is fair or what would have been worth her time
Actually the "right time" to specify it, is literally any time she decides she's come to an adequate number, and put it in ink, at her own leisure. Again, she has the skills, she gets to makes the demands. Go make another offer to someone else instead. Not difficult to understand.
> The actual offer is not really insulting if the company didn't know she was in such a high COL area.
Again: your problem. Not my problem.
This isn't really selfish; I have a responsibility to me and my wife. I need to know that I won't get too burnt out, I need to know that the money I am making will sustain me comfortably, I need to know that I will have enough to pay my mortgage or my wife's school etc. If I am going to work to make someone else a profit, then I should try and maximize my own as well.
> The company being somewhat reasonable with money
That's the thing, they weren't. If you've done the math and know how much a task is worth, then you should offer roughly that amount. To ask one amount and then double it when it's not enough means you either haven't done the math, or you have and you were hoping the potential hire hadn't.
It's like when I see anything regularly go on sale for 50%+ off; they're probably making money even when it's on sale, which means without the sale they have more than a 100% markup over cost. They have their market cornered and are getting as greedy as they can. Nothing wrong with that. Nothing wrong with me not buying it either.
1. You should get the scope of work from a client before they throw a number at you. 2. You should then turn them back a proposal with an amount (based on some estimate of hours, or whichever way you prefer to bill people (daily, retainer, hourly, whatever)
In this scenario, they threw out a number and it set a bad expectation on the dev. I don't blame the author. This is 300-400 hours of your life you will not get back and it sounds like it's not competitive to them based on their situation. The business will have to try someone else or change up their approach.
Big whoop, right? My 500 W PC with a 40" OLED panel can do that with ease. Well this can do it in a handheld with 7+ hours of battery.
Watch the linus tech tips video, the failed completely in this regard.
I personally watched the 54 minute in-depth overview from My Life in Gaming[2], and it was clear that LTT/ShortCircuit overlooked or were incorrect in some parts of their initial impressions.
EDIT: Specially in regards to the display, they spent no time at all to experiment with the 3 built-in GBA display modes; if they used the modes that replicated the original GBA or GBA SP (AGS-101) screens, they would've had a more color-equivalent appearance. MLiG in their video spent 10+ minutes on display modes alone.
They did use the GBA SP mode in the comparison: https://youtu.be/h6l5fAbcim0?t=619
But the broader point that the channel is specifically unboxing/first-impressions and not a review is definitely accurate.
Apologies, missed that for sure. There could still be a multitude of other factors at play (backlight brightness, saturation setting, sharpness setting, etc.)
> But the broader point that the channel is specifically unboxing/first-impressions and not a review is definitely accurate.
Agreed!
Not saying it doesn't matter at all, just that smaller screens seems to make that kind of thing less obvious.
To each their own though.
I like to tinker and I'm a display junkie. Playing retro games revitalizes me by bringing my headspace back to when I was young. Little me loves these toys. It would be trivial for me to fall down a cynical nihilistic cliff any moment of any day. If a utilitarian wants an explanation, they can have that one.
The imperfections of the audio chips in old consoles are easily audible to humans. If the goal is accurate recreation then assuming the audio chips and driving circuitry is perfect is insufficient.
Video recreation is still far below what the Human Visual System can detect. We are not masters of the universe yet.
But that also doesn't necessarily offset the latency of getting inputs into the emulator in the first place or in getting video frames from the emulator to the display.
I agree with most of your point here, bus is that particular one true? Doesn't the Gamecube (for example) use a PowerPC chip? I would be very surprised if isn't an effort to make FPGA implementations of the PowerPC.
I realize that there's a lot more to making a clone system than "just recreating the CPU", but why would making an FPGA for something after the N64 be impractical?
I think this might be more important as time goes on as well. Getting cycle-accurate emulation of anything more complex than the Dreamcast I think will become pretty prohibitive to do in-software. I suspect something like CEN64 might end up being the last cycle-accurate emulator out there (though I would absolutely love to be wrong on that). The advantages of FPGAs would make themselves substantially more apparent at that point than the Gameboy or NES.
That's not an inherent limitation of software emulation, no, but for all practical purposes it is as nobody is doing specialized software emulation for a specific set of hardware to bypass the normal OS/graphics stack. It's instead "throw linux on it, and fullscreen an off the shelf emulator"
That said, I will concede that there is definitely an audience for low-power devices obviously, and maybe FPGAs will fill that niche.
As a software engineer, I spend all day dealing with bugs. I have a good gaming PC and a PS5, and spend much more time on my PS5 because it always just works. No tweaking settings, no crashes, no compatibility issues, no incompatibility with my controller.
When I get home from a hard day's work, I want to play something on an appliance. Analogue devices are appliances, and emulators (and even the Mister) are not.
In the UK for example, there is no legal ability to format shift for end users at all, so ultimately you can't really do legal software emulation, at all.
(Do not take this as legal advice that hardware emulation is permitted. It's complicated.)
They offered an entirely reasonable amount of money for anyone who didn't live in the valley (most people), then we're flexible enough to double it when it wasn't enough.
They asked the person to sign a reasonable NDA that sounds much less restrictive than anything I've ever had to sign, and they were out? 6 months of non-competition on a direct competitor in a tech job is nothing.
The blog author is the developer of the mGBA emulator which is free and open source... There is no commercial competition for Analogue there.
This whole thing sounds more to me like one of Analogue's lawyers thought up a scheme to lock down that project for cheap under the guise of paying for some development work.
This “non-competition for 6 months is nothing” is also a red flag, in my view, for the whole tech scene then. It doesn’t make it right, if common as you say, just make the norm wrong.
And you left out of your comment the point that they were not fulfilling a few promises made even before the job had started. Which is a very big part of author’s reason.
It’s a pretty straightforward conversation. I just say what I’m willing to do. If it doesn’t work out, it’s okay. But that’s harder for enthusiasts.
I think part of this is that enthusiasts also want to help out and they’re usually unfamiliar with consulting style gigs. When both parties want to play and they’re both willing to discount/pay premium but bid and ask don’t cross even with the handicap, then this sort of thing tends to happen.
That’s why the value judgment comes in. They both want to play.
Which is not to say there's no reason to own an Analog Pocket, it's a set of tradeoffs. I just personally find those trade offs make very little sense.
[0] by which I mean the game, taken as a piece of artistic expression
I will say that FPGA emulation is cool in some ways -- the power draw is less and you can achieve lower latency without some of the CPU-intensive methods that software emulators have pursued to do it. But most of the claims made about it do not stand up to scrutiny.
Compared to original hardware, the promise is that it will have a better screen, a sleep mode, let you play on TV, load ROMs from computer (if you're a developer), etc. Compared to software, the promise is the form factor.
Seems to be $120 for equivalent form-factor, but still missing a large amount of what the Pocket supports (such as physical cartridges, link cable, and TV output), and with a worse display and a smaller battery. And it's not like the Pocket is that much more expensive at $220.
https://www.eurogamer.net/articles/digitalfoundry-2021-analo...
I've ordered one today as soon as the orders opened, personally I'm incredibly excited about it - it will compliment my collection of classic gameboys really really well.
The point is to be better than a real Gameboy. Most of the original GBs don't have backlights, the original GBA in particular is INCREDIBLY hard to see unless you're sitting directly under a lamp. The speakers are usually pretty quiet. With the Gameboy Advance, if you want a frontlight/backlight you need to get an SP which I personally think is very uncomfortable for extended periods, and also doesn't have a headphone jack without a dongle (Nintendo was way ahead of Apple on that!). The GBA is backwards compatible with older Gameboy games, but the cartridges awkwardly stick out of the device an inch or 2, which make them awkward to transport around.
Plus what others have mentioned, with the fact that it'll probably get hacked very soon to enable running any game from an SD card.
I like the idea of updated hardware and features in that form-factor, but was put off by the negatives. I would definitely buy a revision if they make one though.
The author's treatment was not great though, so I hope the company does better in the future.
Edit: here is the review: https://news.ycombinator.com/item?id=29541242
What is the logical conclusion of your comment? Is expertise solely tied to the amount of compensation someone receives?
Welcome to earth.
This story had 0 comments and was far off the front page. I read the article, found it interesting, and upvoted it. That seems to have bumped it to the front page to snowball.
So let's assume (as a good faith actor would) that the counter party doesn't know what this undertaking really entails. It's a lot of work - so a better response might be something like "the amount of work we are talking about would take a good engineer approximately 4 months. let's start the negotation there"
Maybe the author is new to business, but there's a lot to be desired in their communication. The screenshots of their communications only emphasize my take on it.
> As evidenced by the continuously slipping timeline in mGBA, I’m not very good at estimating timelines, so I gave a (very) rough estimate of 2 to 4 months. A reply affirming that that sounded reasonable, with an estimation of 300 to 400 hours of work, with a price tag of $10,000 was what I got back (assuming the project didn’t run seriously overtime).
> $10,000.
I have seen this sort of thing before in the 'real' industry. You work for a hardware company and they see the software work as a 'extra' that you just bash something out and hope for the best. I have went out of my way to not work for hardware companies anymore. Many do not 'grok' software. That the hardware and software have to work together or they both fail.
This sort of story is probably better on r/choosingbeggars.
They could have ghosted. They could have made a reasonable counter.
Instead they decided to sling mud.
Childish and unprofessional.