Golang

So far I have been using my nvim golang setup for around more than 6months now and I am still learning something new everyday while I use it. coc.vim works really well so far for me. Linting, autocomplete, jumping to definitions back and forth, code folding, checking for references for where a function/method is used, it works out for me well so far. What I am trying to fix on my setup so far The debugging experience for sure can be improved, I have tried using nvim-dap-go. ...

Ok, not vim, but nvim tl;dr what does all this get me in my setup https://github.com/tasdikrahman/dotfiles/tree/master/vim jump to definitions jump to references jump to symbols fuzzy file search code folding jumping between test and implementation file testing specific function real time code linting Cleaning my vim config after some time and ended up removing a bunch of things and starting afresh, a couple of plugins which had been archived but worked all the while were https://t.co/lmjXtN7HbS, switched to https://t.co/7ZSoKMgwBW as it was the recommended replacement (1/n) ...

This post mostly is for documentary purposes for myself, about a few things which I ended up noticing while using client-go as I used it for deliveryhero/k8s-cluster-upgrade-tool, which used the out-cluster client configuration, a couple of things are specific to that setup, like client init, but other things like testing interactions via client-go are more generic. Initialization of the config client-go in itself, shows a couple of example of client init here, pasting the snippet here for context ...

Just a continuation of the tweet, adding into small snippets for context. Came across this issue where spf13/cobra would not work for mandatory flags set, when PreRun is set for a command while building a cli tool https://t.co/GmULRFrFfm (1/n) — Tasdik Rahman (@tasdikrahman) February 28, 2022 Context When you have both the PreRun and Run directives, and the mandatory flag present, which you expect to run before the PreRun directives mentioned, it will not be respected. This post is just a small nudge to prevent someone from trying to achieve the same as the same hasn’t been documented on cobra.dev side so far (in case nothing has been missed) ...

This blog post is a continuation of these two threads. A few things about database schema changes. (1/n) — Tasdik Rahman (@tasdikrahman) October 17, 2020 This is where @rails active record migrations really shine. I find it's UX super clean. (1/n)https://t.co/vA6Jb345yc — Tasdik Rahman (@tasdikrahman) October 18, 2020 The schema of your relational database, will change over time for your application. Trying to introduce these changes from dev setup -> integration/UAT -> production env, in a clear, consistent and repeatable manner, would definitely add value in trying to maintain repeatability across different environments. ...