Erik on Software

Sign in Subscribe

Topic

community

A collection of 47 issues

Community Post: Part 6 - GPTZero can't be relied upon to determine human or AI authorship

* I've been quoted 25 times by various publications since 2016 * A platform I started using in 2025 provides a "Check for AI" option * GPTZero increasingly considers my replies to be AI generated * Apparently, my English is too perfect to be human A community post I made

Community Comment: Part 42 - Positive, negative & "realistic" company culture

* For a long time, I valued being a realist rather than a pessimist or optimist * However, I've long discovered something * The world is largely negative, so being a realist means largely being negative * Making the choice to be positive is the only true alternative path The comments I

Community Comment: Part 41 - Always do the right thing, even when nobody's watching

* Management is doing the things right * Leadership is doing the right thing * This Peter Drucker quote is about the nature of one's actions * Always do the right thing, even when nobody's watching The comments I provided in reaction to a community discussion thread. Former Senior Advisor

Community Comment: Part 40 - Being bold & clear helps avoid the traps of enterprise architecture

* Enterprise architecture traps and how to avoid them * Be bold and direct when it comes to describing traps and cures * Ivory tower architectures are traps, but who actually creates architectures? * If you want to make progress, avoid usage of unclear or circular definitions The comments I provided in reaction to

Community Comment: Part 39 - George Bernard Shaw's dictum extended to AI

* The "AI is going to take all our jobs" narrative is lazy * Shaw: "Those who can, do" * Shaw: "Those who can't, teach" * Gfesser: "Those who can't do or teach, use AI" The comments I provided in reaction to

Community Comment: Part 37 - All code is disposable; only some code is trash

* All code is disposable; only some code is trash * The word "trash" has negative connotations * All portions of given code base have life cycle * Avoid miscommunication by being clear! The comments I provided in reaction to a community discussion thread. Software Architect at Design & Construction Product Firm:

Community Comment: Part 36 - Data modelers need to understand patterns

* Data modelers need to understand patterns * Like programming, don't reinvent the wheel * Universal patterns & metapatterns exist * Remember "The Data Model Resource Book" The comments I provided in reaction to a community discussion thread. Vice President at Data Modeling Training Firm: I am always wondering why

Community Comment: Part 35 - Despite naysayers, benchmarking can be valuable

* Don't repeat a quote before assessing it * Galanakis incorrect about unexecuted code * Execution required for relative performance * Benchmarking valuable despite naysayers The comments I provided in reaction to a community discussion thread. Chief Challenge Writer at Coding Challenges: Some advice just never gets old. “Controlling complexity is the

Community Comment: Part 34 - Popular data engines use Java / the JVM because it ruled the enterprise for many years

* Reasoning behind popular data engines & Java * Java / the JVM long ruled the enterprise * Spark, Flink, Presto & Trino are all Java-based * Remember: Presto & Trino share some history The comments I provided in reaction to a community discussion thread. Head of Product at Data Lakehouse Product Firm: 🤷‍♂️ GitHub PRs

Community Post: Part 5 - Databricks is the 2023 runner-up winner following acceptance of my proposal to include it in DB-Engines ranking

* DB-Engines ranking of DBMS products * Databricks climbs after my proposal to include * Databricks is runner-up winner for 2023 * Earlier rankings left out Databricks A well-received community post I recently made (re-posted 14 times at the time of this blog post): https://www.linkedin.com/posts/erikgfesser_databricks-snowflake-dbengines-activity-7150225307155755008-E_uS Some of