zenolove

Already back in ye olde times, "let me google that for you" which I see so often posted on Reddit. Sometimes you just wanna exchange with a human, and absorb some of their wisdom, which is the whole point of asking a question. Not so different than wanting to shop at a butcher you can establish a relationship with, rather than a faceless supermarket meat counter.

What about "your milestones, roadmap, discussions and strategies do not matter, but my precious code had elbow grease put into it."

Petty and getting nowhere. Everyone loses. How about product and engineers also disrespect sales, and sales disrespects customers and everyone else.

I really don't get why this is even a question. Good people do good stuff, and bad people make bad companies.

Well said. It is all about trust.

Just like "etiquette" accomplishes no purpose except letting people easily figure out who put the effort into learning it, vs. who didn't.

Back then this distinguished by class, but ironically, today where's so easy to learn, it finally distinguishes by merit.

I don't think anybody would complain about working code. Your PR would explain your reasoning and choice of solution, and that on its own could make or break through acceptance criteria. At least it would by mine.

Errors are fine too. Just not negligence.

Yeah, what happened to "review your own code first".

Even before AI I used to ban linting so I could spot and reject code that clearly showed no effort was put in it.

First occurrence of "undreadable" got a note, and a second one got a rejection. And by "undreadable" I do not intend missing semicolons or parenthesis styles or meaningless things like that. I mean obscured semantics or overcrowding and so on.

They do exist; if "professional" means "hired" it has no bearing on quality, it is not in any shape equivalent to "judicious" nor "careful". If salary goes into "push features" that's gonna be the only incentive.

Or paying maintainers and contributors.

Horrible degrading take. Be the change you want to see. Don't fuel the fire that's burning you.

If something's not happening, something else's making it impractical. Saying this as a 10+ years product manager and R&D person with 20+ more years of engineering on top.

I also had to deal with "managers are just complicating things" or "users are stupid and don't understand anything"; do you think I complained? No, I had engineers barter trust of their ingenuity with trust of my wisdom, and brought them to customer calls and presented them to users almost like royalty, which made them incredibly respectful as soon as they saw what kind of crap users had to deal with.

It's slippery. You're swamped with low-effort PRs, can't possibly test and review all of them. You will become a visible bottleneck, and guess whether it's easier to defend quality vs. "blocking a lot of features" which "seem to work". If you're tied by your salary as a reviewer, you will have to let go, and at the same time you'll suffer the consequences of the "lack of oversight" when things go south.

Hey! Would you consider trialing some help, even part-time initially, and pro-bono, to see how it goes? As a developer since childhood, and product manager for most of my career, with (I dare say) some out-of-the-box, simplicity, "cheap is best" professional deviation, and sex-positivity in my personal and artistic life, maybe there's something we can get together on? Give me a shout! zenojevski at gmail dot com, or https slash slash zeno dot love. At the very least we can have some fun and maybe keep writing :D Zeno

A better name might be “sometimes function”

> What I have achieved so far

> • Understand large parts of Furby's BLE communication protocol

> • Open a secret debug menu in Furby's LCD eyes

Then I looked at the project logo again and it spooked me out

The [E0C6S46](https://download.epson-europe.com/pub/electronics-de/asmic/4...) still powers the 1st and 2nd gen Tamagotchi!

4-bit (!) 32KHz MCU with 6,144 words of 12-bit (‼) ROM, 640 words of internal 4-bit RAM, and a 160-word 4-bit frame buffer for the integrated LCD driver (enough for double-buffering)!

The thing is a beauty! I wrote a Typescript emulator for it, a year ago or so, though for whatever reason I haven’t pushed it to GH yet (but I will if anyone’s interested! It can run unmodified Tamagotchi firmware.

I believe this is the issue mentioned by parent:

https://github.com/alacritty/alacritty/issues/4673

Thank you, this is a much more wholesome reading of it. I probably misunderstood the tone.

That said, I am actually actively trying to grow my engineers into somewhat of mini product managers themselves.

It’s going quite great so far— the more they get exposed to users and problems, the more they are taking ownership of their work.

I don’t hear things like “the user doesn’t understand” anymore, but rather “I tried to make it clear to anyone who uses it”.

They started coming up with features and changes that were way more brilliant than anything I could come up with. And also interviewing developers (who are also target users for us), performing small tests to validate hypothesis, and so on.

And they also started making little jokes in customer calls to keep users’ mood up! Some users even thanked us for letting them test our early “broken” work-in-progress :D and apologized for not testing well enough. The first time I saw this, it was crazy!

I am so incredibly proud of them!

Awww. As a product manager who hopes to be serving, encouraging and fostering his team well, this saddens me to read