laudable-logic
Best headphones? The Cold War story behind
New Spotify patent proposes analyzing users' speech
Agreed. What I mean by "perfect" is: for a given part/component/decision/etc, take the time (an always-limited resource) to learn as much as possible and contemplate more than just the seemingly obvious path forward. Take security for example. I'd rather 'waste time' now making sure I'm covering any gaps in that realm before shipping.
OTOH maybe some jacked-up abstraction/incorrect tool choice/ugly-ui/etc is something that can wait a few sprints or longer. At least you can plan when to deal with these. Security breaches tend to plan your day for itself on your behalf. :)
A CEO from my past often muttered that "perfect software comes at infinite cost". It's key, imo, to identify which components of what you are building _must_ be perfect. The rest can have warts.
I worked on a project that made moderate use of this. Worked alright; biggest problem was convincing DBAs/IT to enable it.
I had to resort to git's assume-unchanged[O] to keep these changes out of commits made in the heat of battle.
> this isn't a best practice for config files
Have had great results (in dotnet land) with MS' Secrets Manager[1].
[0] https://www.git-scm.com/docs/git-update-index [1] https://docs.microsoft.com/en-us/aspnet/core/security/app-se...
Knowing the team was one of those that is constantly using nearly-depleted markers and hating life, I thought to check. Sure enough... all empty, nothing to replace them with.
I thought to just let said report arrive at next day's meeting, ready to whiteboard it up only to look woefully unprepared, but I waited. I waited until about an hour before the meeting to see if they might have clued-in and sorted the problem for themselves...
An hour later I returned from a slushy 2km walk, soaked, with a box of markers that I just placed in the drawer, unbeknownst to all.
Approximately 3 months before VD, our relationship concluded. And then a week before VD, back on... like a house on fire. With nary enough time to execute the original plan, I pivoted the idea somewhat. I opted to export the 'best' few weeks from the WhatsApp convo, then proceeded to stand up a quick MVC site with the exported data presented as if it were a messaging app, complete with the very same images we each used for avatars at that time. Hosted the site off my lappy, and when she arrived for VD dinner, a link was sent to her phone, seemingly out of nowhere. She clicked it, and was greeted with this view, and the title "Budding Love" pinned as a header while she scrolled, smiled, and swelled with tears...
She was a techie chick, but didn't know how to code. She ended up confessing the best part was when I took her through and explained the purpose of all the code that I wrote for this gift I made. She even called me out for committing a sin or two (i.e. code dupe, embedded-SQL-in-C#, etc.) that I would often bitch to her about seeing at work :)
Edit: typo