@mikaelacaron Ensemble programming. Each line in this graph represents the ups and downs of each individual. Coding together gets the collective maxima, moving the work forward whether you're up or down.
Had a developer moment updating a project: "Man, this is no good; I should do something about it."
That's the judgy part. The part that wants to throw everything away and start over using my current knowledge, patterns, and understanding.
This is the distracting part.
The site still works. The code is well crafted for my knowledge, patterns, and understanding at the time. Time to start making notes of how to get "there" from "here."
Since I wrote this, I learned that the most likely reason for the Return-To-Office push is declining real estate value, which means less loan leverage.
But no one is brave enough to say so. Instead, they talk about collaboration.
I'm all for increasing collaboration. And that has little to do with whether you work in-person or remotely. https://www.industriallogic.com/blog/collaboration-beyond-back-to-office/
@ratkins And eating together! You can build a considerable amount of social glue and trust by collaborating in real time remotely, but eating together is a strong bonding activity.
Anyone have a way to disable shadows on Mac window screenshots by default? Command-Shift-4, space, Option-click works, but I want to avoid it. defaults write com.apple.screencapture disable-shadow true does not seem to work.
I had gotten the impression that Swift was an awkward, kludgy, fiddly language like (bias alert!) C++ or Scala, rather than a language that has that undefinable coherence that languages like Ruby or Clojure or Elixir have. I’ve been pleasantly surprised so far.
Of course, I haven’t gotten to reference counting yet.
@itsjoshbruce@marick Swift folks decided to go the route of "Let's make it really hard to create bugs" which means the language is becoming more complicated.
Trunk-based development works well with small commits when you only have a few groups committing. As the number of groups climb, the "push wars" ensue.
Traditional CI used a commit token of some kind, like a plush toy. "I have the commit frog, it's my turn."
What do folks use these days? Where are the remote commit tokens, where you wait in line for your turn to commit?
@GeePawHill I think you nailed it.
There were times on the last project I wish we had a virtual Commit Froggie. But we the push wars didn't happen THAT often. May not be worth coding.
On the other hand, it might not be hard…
@ratkins@GeePawHill It's not just toe-stepping, though. You can have group A working on file A, group B on file B.
I'm on C. I want to push. Oh, my code is out-of-date because A pushed. I get their changes, so everything is now integrated on my machine, and all tests pass. Ready to push.
Crap. B pushed before I had the chance.
This is where a queue for the token would be helpful.
@marick@cammerman The declarative way would be an "event to process" in your observed data. When it's unprocessed, show Thing then set it to nil or empty. This then triggers another rerender, "Oh there are no more events, so I should hide Thing."
There's nothing wrong with AppKit, and it's not going to vanish anytime soon.
@marick Well, something outside of SwiftUI MIGHT be able to capture keyboard events. …Honestly though, I think this kind of thing would be easier with AppKit.