It's not. Actually it's almost worse because it tends to hide issues even deeper.
This practice is very similar to when teachers would reward students for good behavior on days the teachers would be evaluated.
Principal looks good to the board/state, teachers look good to the principal, and students look good to the teachers - but yet, we get caught up in looking good and impressing others, that we forget the real issue of children that are still getting left behind.
> I have had to deserialize into map[string]interface{} to handle ambiguous situations at runtime a lot.
Something I worry about is if I'm getting too jaded. You really think things are different elsewhere, but then you see that we all eat the same shit sandwhich.
That code would never have to be written if someone just used their brain before switching their integer IDs to string GUIDs. Bless your soul but I wish we didn't have to resort to such things. Some things code can't fix.
private groups work best for this, lets not get ahead of ourselves and try to make some sort of jira bounty ticket tracker for some indie diy crowd
if requirements were a solved problem... everyone would have a very valuable skillset to determine the things worth doing given the inherent ambiguity across all levels
but if you are cut from the same cloth, lets paste a gist as a sign up sheet of whos interested in private group projects and work from there?
How did you deliver the guides? Confluence doc + screenshots? What worked?
Also, what is the category/term called for those type of pain points? It's like those typical enterprise-y, sad but true, jaded senior tropes.
Like this question:
> How to represent a form from an object that isn’t backed by a row in the table?
I don't know how to describe it exactly, but it's like a question that gives off a strong signal of someone operating at a high level in an enterprise context.
I'm genuinely curious on the ways people solved those types of questions.
It is likely that HN has been influencing you into associating writing/coding/building with failure.
Try to work on things without the idea of "Show HN" on your mind. I think a lot of paralysis can come from trying to impress people here. The hivemind will find some way to discuss (lack thereof) profitability, novelty, and accessibility.
I don't think the author has to divide writing good (quality) with being slow (speed), and writing fast with being bad.
I firmly believe that the goals is aligned on both sides. Client wants a feature "just works" by a certain date, and programmer wants to ship that very feature (without breaking anything else) on that certain date.
The impedance mismatch is that programmers see (code) quality as enabling higher velocity (work on new features without needing to maintain old ones) with the trade-off being the upfront cost. The client sees that the time it takes to deliver feature X as being proportional to delivering feature Y and Z.
The catch is that it is very hard to communicate that delivering feature Y and Z would be quicker (or not needed) if feature X was designed properly. This is because you can only approach this in hindsight (orthogonal thought: this is why upfront waterfall fell out compared to iterative agile).
The hard truth both sides don't want to admit is that the programmer does not know what they are building and the client does not know what they are asking.
Instead of the client wishing that the programmer had more domain experience and the programmer wishing the client had more technical experience, there should just be a stronger focus on empathy and letting things fail as part of the process.
I find it interesting that when things fail, client knows exactly what failed and programmer knows exactly why it failed. Must have something to do with hindsight :)
Interestingly the constraint of only being able to use a simplified alphabet would let Vim "supercharge" this tech.
My assumption is that translating the thought "delete the current line that the cursor is on" to the actual action is still far away. And then expanding that to something like "delete the current line that the cursor is on and all the lines above it" might be even more difficult.
But the equivalent operations in normal mode are "dd" and "dgg", this interfaces very nicely with the implant.
I found meds to have enhancing effects on my code. Everything I have earned is because of it.
My best guess is you are still in the phase of titration and finding the correct type of medication that works for you.
Having an empathetic doctor who is willing to work with you can make that road smoother. She printed out papers from pubmed to help me better understand what I'll be taking and what to expect. It felt very nice to actually be taken seriously.
I do notice that the other experiences may not truly reflect the efficacy of medication. The actual symptoms are still not well defined, not all doctors are equal, being misdiagnosed, etc.
Hard truth? It's still guess and check. There are so many comorbid conditons associated with ADHD - most of the time it is just the symptom of an underlying cause. ADHD meds only work on people with ADHD :)