When hiring software engneers I look beyond technical talent. What I really want is someone who understands "the ecosystem" they work in. Recruiting is always challenging. I think this is a good start to help you spot the great ones.
Companies say they want engaged employees. Funny, I’ve never heard an employee say they wanted to be "engaged" (at least not to their company). Personally, I’d much rather be inspired. When you’re high on inspiration, you can get two weeks of work done in a weekend. Inspiration literally brings the future forward like a time machine.
Having worked in financial services for most of my career I want to share some the software engineering challenges that are associated with tracking and moving money digitally. Most of these lessons have been learned the hard way. Hopefully they will be useful to anyone moving into the fintech space.
We think that generative AI creativity is limited by its training data and algorithms, and therefore can produce technically proficient content, but not truly novel and innovative content. We like to believe that our own creativity and innovation, rooted in personal experience, knowledge, and human emotions results in intentionality and emotional depth that cannot be replicated by AI. Current research contradicts that view.
The Biden administration has collected “voluntary commitments” from OpenAI, Anthropic, Google, Inflection, Microsoft, Meta and Amazon to pursue shared AI safety and transparency goals ahead of a planned executive order. Will it be enough?
Corporate bullsh*t can be a handy supply of manure for fertilizing new ideas and innovation. Corporate bullsh*t also has a number of negative effects on both employees and organizations, including a tendency to suppress those with differing opinions and perspectives. The most detrimental consequence of rampant organizational bullsh*t is the corrosion of organizational decision-making. Can you spot it?
Joel Spolsky (of Fog Creek Software and Stack Overflow) describes system re-writes as “the single worst strategic mistake that any software company can make”. However, engineering teams love full rewrites because they incorrectly think of old systems as specs. They assume that since the old system works, all functional aspects have been settled. Design risks have been eliminated! They can focus on making changes to the underlying architecture without worry. This is a deeply flawed assumption.