Christian, woman, wife, homeschool mom, grandmother, software engineer, skater. The views are express my own and not those of my employer.
Joined January 2013
- Tweets2.7K
- Following126
- Followers492
- Likes358
I’m noticing an uptick in expert beginners. It appears to be directly related to using AI.
daedtech.com/how-developers-…
I just showed my husband how to use Pythagorean triples to check for square. Made me think of you @JEG2
For anyone who happened to see Kate give a lightning talk at #elixirconf here’s a throwback to her first lightning talk from when she was a teenager.
rubyevents.org/talks/lightni…
I'm watching a tv show where some dude is trying to exert force during a handshake with another dude.
Just an FYI, a candidate I once interviewed dislocated a bone in my hand doing that.
And yes, that pretty much guarantees you won't pass the interview.
Just because you're solving a problem doesn't mean you're solving the right problem.
If you found that you aren't solving the right problem, take heed. You've likely replaced a problem that is "new to you" with a problem you know how to solve. It happens subconsciously.
And this isn't just about data, moving logic around can cause the same issues. It's quite often that a few small steps get you to your destination with zero drama. The harder part with this approach is getting approvals on your prs.
A big hurdle with the messy middle is that devs can clearly see the full work isn't done. They see loose ends and they know something should be done about them. This is where leaning into the difference between "no" and "not yet" and can be very helpful.
When I was very small, we had friends who had rescued a baby chipmunk. It lived with them its whole life. When the husband passed (the chipmunk had passed much before) we went down to help take care of the house. My dad needed to fix the washer. When he opened it up…