静态网站悖论
个人网站的两种不同实现方式：一种是复杂的内容管理系统（CMS），另一种是简单的静态 HTML 文件。文章指出，尽管大多数普通用户倾向于使用复杂的解决方案（如 WordPress），但实际上，只有少数专业软件工程师能够选择更简单的静态网站。
via HackerNews 2024 10 09
前两天刚好听朋友说 square space 已经涨到了近乎搞笑的 $25 月费，做不用来盈利的个人博客实在难以 justify。这篇文章中吐槽得很在点子上：
normal users are stuck with a bunch of greedy clowns that make them pay for every little thing, all while wasting ungodly amounts of computational power to render what could have been a static website in 99% of cases.
普通用户被困在了一群屁大点功能都要收费的贪婪小丑手里，与此同时浪费着人神共愤额度的算力来渲染 99% 的情况下都可以作为静态的网站。
当然原文中说的“只有少数专业软件工程师才能选择更简单的静态网站”略微夸张并不认同，因为静态站至少是比 self-host 的动态 CMS 少太多维护了。我的 backlog 里也一直躺了篇安利新手用静态站并拉踩 WP 的文，不过网上这种文已经有无数了也还是拦不住前赴后继往各种 CMS 的坑里冲的新手，觉得写了又有什么意义呢就还搁着没写。（当然迟早会像以前反复造的无数轮子一样被废话欲战胜的 but not today）
#indieblog#newletter
https://code.tutsplus.com/tutorials/behavior-driven-development-in-python--net-26547
Behavior-Driven Development (which we will now refer to as "#BDD") follows on from the ideas and principles introduced in #Test-Driven Development. The key points of writing tests before code really apply to BDD as well. The idea is to not only test your code at the granular level with unit tests, but also test your application end to end, using acceptance tests. We will introduce this style of testing with the use of the Lettuce testing framework.
http://pythonhosted.org/behave/
behave is behaviour-driven development, Python style.
Behavior-driven development (or #BDD) is an agile software development technique that encourages collaboration between developers, #QA and non-technical or business participants in a software project. We have a page further describing this philosophy.
behave uses tests written in a natural language style, backed up by Python code.
Once you’ve installed behave, we recommend reading the
tutorial first and then
feature test setup,
behave API and
related software (things that you can combine with behave)
finally: how to use and configure the behave tool.
https://pypi.python.org/pypi/pytest-bdd
#BDD library for the py.test runner
#pytest-bdd implements a subset of Gherkin language for the automation of the project requirements testing and easier behavioral driven development.
Unlike many other BDD tools it doesn’t require a separate runner and benefits from the power and flexibility of the #pytest. It allows to unify your unit and functional #tests, easier continuous integration server configuration and maximal reuse of the tests setup.
Pytest fixtures written for the #unit_test s can be reused for the setup and actions mentioned in the feature steps with dependency injection, which allows a true BDD just-enough specification of the requirements without maintaining any context object containing the side effects of the Gherkin. imperative declarations.