4,421 karma · joined June 6, 2012
To the extent possible, prioritize complete vertical slices. While it may not be feasible for foundational or generic technology layers that must be fully developed before building on them, aim to avoid focusing on large horizontal layers that delay end-to-end functionality or demonstrable results within the new system.
Again, depending on many factors, you might consider the strangler fig pattern, in which you implement some component of the new system and operate alongside the original one, route some usage from the old to the new (or even run in shadow), test and validate, repeat incrementally, and so on.
In my mind, what it comes down to is just being really vigilant in ensuring you minimize the risk inherent in a massive migration...which basically means try to achieve the ultimate migration with a series of much smaller, iterative migrations that carry significantly less risk.
I think any may be too broad. That encompasses things like:
- SMB accounting software
- Email marketing platforms
- Project management tools
- CRM software
- Website builders
- SMB HR and payroll services
- SMB IT and security solutions
- freelance/gig platforms
- SMB marketing services
- Legal/compliance for SMBs
And each of these seems like extremely saturated verticals with just a ton of offerings and competition.
This is where I get stuck. The idea of focusing on a small vertical that isn't attractive to venture capital funding appeals to me, but then I'm at a loss for ideas beyond the most obscure niches, like a bingo card creator :P
Your excessive focus on minor linguistic nuances is counterproductive. It's more important to understand the overall message than to get bogged down by trivialities, which everyone here seems to be able to do — except you.
Moreover, by repeatedly correcting language, you give off an 'I'm smarter than you' vibe, which isn't conducive to a productive conversation.
> An ever-expanding library > What a vision that is. We are continuously adding new quotes to Author Clock. Once it's connected to your WiFi they'll simply begin to... apparate.
Could you elaborate? I'm not quite understanding your point, and I may be misinterpreting the sentence.
The assertion that "metaphysics fits enterprise software development discovery and implementation needs perfectly" overlooks a critical distinction between philosophical inquiry and practical application. Metaphysics, which delves into the nature of reality and existence, often involves abstract categorization and the pursuit of understanding universal truths. However, enterprise software development is fundamentally a practical discipline aimed at solving specific business problems.
When software engineers model a domain, they are not engaging in an Aristotelian or Platonic exercise to capture the true essence of entities. Instead, they are creating representations that are useful for achieving particular business objectives. The primary goal is not to uncover ontological truths but to develop functional, efficient, and scalable solutions that meet the needs of users and stakeholders.
Theoretical unifications and abstractions, while intellectually stimulating, can often lead to over-engineered solutions that do not align with the practical demands of enterprise software. Software development requires pragmatism: the ability to prioritize utility and business value over philosophical purity. Abstractions in software are useful only insofar as they contribute to the effectiveness and maintainability of the system within the context of its intended use.
I'm not suggesting there aren't some situations where applying metaphysical thinking can be helpful. However, using this approach as a general, top-down strategy doesn't make much sense. Software engineering, by definition, is a practical discipline, involving concerns and objectives that differ fundamentally from those of metaphysics.
> “Noi.app” is damaged and can’t be opened. You should eject the disk image.
> As she had done at Facebook, Furlow-Smiles circumvented the vendor process at Nike to commit fraud. She linked her Nike corporate card to her PayPal and Venmo accounts. She then paid her associates with PayPal and Venmo, causing fraudulent charges to her Nike card. The associates kicked back portions of the payments to Furlow-Smiles, who submitted fraudulent expense reports to Nike to cover her tracks. The expense reports falsely claimed that the payments were related to the Juneteenth event.
Imagine presenting yourself as a champion of DEI, cloaked in righteousness, while secretly defrauding your company with boundless greed.
[0]: https://www.justice.gov/usao-ndga/pr/former-diversity-progra...