Posts

https://excalidraw.com/ Keyboard shortcuts Tools Tool Press This Hand (panning tool) H Selection V or 1 Rectangle R or 2 Diamond D or 3 Ellipse O or 4 Arrow A or 5 Line L or 6 Draw P or 7 Text T or 8 Insert image 9 Eraser E or 0 Frame tool F Laser pointer K Pick a color from the canvas I or Shift + S or Shift + G Edit line/arrow points Ctrl + Enter Edit text / add label Enter Pick a color from canvas Enter or Shift + Enter Finish editing (text editor) Esc or Ctrl + Enter Curved arrow A + click + click + click Curved line L + click + click + click Add a new line (text editor) Q Prevent arrow binding Ctrl Add/ Update link for a selected shape Ctrl + K View ...

zellij 把这个放在最前面的目的，是因为这是后面所有软件的外壳。 终端的分屏工具，原来我是用tmux的，目前已完全换到了zellij，同类软件还有screen等。 https://github.com/zellij-org/zellij ...

Ctrl+n 打开/关闭 NvimTree

What is Operate? Operate, the second of the Four Pillars of Feature Management, encompasses feature flag use cases that improve the operational health of your application. It entails making feature flags a mission-critical piece of your operations. As deployment speeds and infrastructural complexity go up, so does the need for operational safeguards. Feature management is that safeguard. Teams that use feature flags via a feature management platform reduce risk and ensure customers remain satisfied with their service. They dramatically cut down on serious incidents. For example, as previously cited, Honeycomb has a “change fail rate” of just 0.1% , a feat shared only by the world’s most elite software teams. And the company cites its use of LaunchDarkly as a big reason for its exceedingly low failure rate. ...

Reducing technical debt from feature flags Read time: 16 minutes Last edited: Oct 15, 2024 Overview This guide provides ways to reduce and eliminate technical debt related to feature flags using LaunchDarkly. Like all debt, technical debt accumulates over time, but you can mitigate that debt over time if you put effective processes in place before you need them. In this guide, we’ll explore: The challenge of technical debt The lifecycle of a flag Naming conventions Using tags Code references Deprecating, archiving, and deleting flags Just like feature flags should be a core engineering practice, so should a strategy to address technical debt. LaunchDarkly can help you by automatically identifying flags that need code removal or are ready to archive. ...

It’s a very sudden thought. I start a personal blog, only write by myself, and only use English. It’s about all my life. From my born To the last if I can. Today when I search something about software architect, I went to this blog https://docs.microsoft.com/en-us/archive/blogs/marcod/ then I saw a blog named “After 18 years posting” it’s quite shack me. I want be a man like him. don’t need post every day. but post 18 years and more. let’s go. ...

What is feature management? Feature management is a new class of software development tools and techniques powered by feature flags. A feature flag is a lever of control within your code (an if-else statement) that decouples code deployments from feature releases. Developers have used some variation of feature flags for years. But when it comes to enjoying the full benefits of feature flags, many have only scratched the surface. At most organizations, the art of feature flagging is confined to just a few teams across a few use cases. Such limits stem, in part, from the fact that managing feature flags at scale is quite challenging. For one thing, technical debt can rapidly accrue if you start using flags in large volumes. As a result, only a handful of developers end up using them, thus limiting the value an organization can capture from those flags (see what we did there?). Another drawback of conventional flags is they only support basic true-false, or Boolean, use cases. This, too, prevents organizations from realizing the full benefits of feature flags. ...

如何键入真正的Tab字符？ 如果你想要在 Vim 中输入真正的 Tab 字符，你可以在插入模式下按 Ctrl-V，然后按 Tab。这将插入一个真正的 Tab 字符，而不是空格。 注释代码？ 快捷注释， V gc 如何缩进？ 在 Neovim 中，您可以使用以下方法进行代码缩进： ...

拆分为两套代码所存在的问题： 使用不同分支后，大型修改的合并将变得极为困难，不论是从上游合并到下游，还是下游合并到上游，都将成为一个耗时巨大的工程，以轻共享代码合并上游为例，历时3个多月，经历过大量测试，仍然出现风险不可控。如果只是禁绝了从下游合并到上游的可能，下游的客户也一样需要承担上游合并到下游所带来的功能异常风险，及下游代码丢失的风险，该风险从宏观和微观层面，都与下游合并至上游一致。 ...

十年Kubernetes：过去、现在和未来 翻译自https://thenewstack.io/10-years-of-kubernetes-past-present-and-future/ Matt Butcher 回顾了事情的起点，Kubernetes走向成熟的历程，以及它在WebAssembly运动中的潜力。 2024年6月12日上午10:00 由 Matt Butcher 撰写 ...