zimmski

6 ms·

1.
by zimmski 2y ago
Just announced an deep dive blog post with findings about an evaluation benchmark on software development quality. Here is a thread to the most important findings https://twitter.com/zimmskal/status/178601266181512
2.
by zimmski 5y ago
At Symflower we do, one of us has it as its main editor and it looks extremely productive. As a former VIM hardcore user i enjoy the pair programming sessions. I guess these sessions must feel the same way when a non-VIM user watches a VIM
3.
by zimmski 5y ago
Its a nice and short introduction to SAT and especially SMT with a real world example written in SMTLIB. If anybody is interested or has any questions, let me know. We are planning to post more about SAT and SMT as they are part of our core
4.
by zimmski 5y ago
Looking forward to having even less context switches with a perfectly working GitLab plugin inside of VS Code.
5.
by zimmski 5y ago
As someone who is in the business of software, infrastructure and especially testing for now almost 20 years, i can underline the fact that people often still think of (automated) software testing as something that is not needed. "I tr
6.
Introduction on Doing a Symbolic Execution(symflower.com)
1 points by zimmski 5y ago|0 comments
7.
by zimmski 5y ago
Does anybody know another Z3 online version or another SMT solver that can be used online? Rise4fun is gone for good :-( https://github.com/Z3Prover/z3/issues/5472
8.
Good Code Coverage means bug-free Software Or does it?(symflower.com)
1 points by zimmski 5y ago|5 comments
9.
by zimmski 5y ago
Just read through the article and was wondering if anybody had experience with migrating from Cypress to Playwright, or Playwright in general? Before Cypress i was used to working around problems of Selenium/Webdriver. Now it seems wit
10.
Comparison of Playwright vs. Cypress for E2E web testing(medium.com)
2 points by zimmski 5y ago|1 comments
11.
by zimmski 5y ago
One of the funniest articles i have read in a while. Know the author's journey really well, the dailies were funny as heck. Getting rid of a "/" is really hard work, you need to dig deep. Worth reading even if you don&#x
12.
by zimmski 6y ago
Yep. I have that practice too and i thought that was good enough but with git-autofixup and my posted alias i am down to under one second. So it will save you 1-14 sesconds of your life with every fixup you do... unless it cannot be done au
13.
by zimmski 6y ago
Totally agree. I guess what i am trying to say is that learning rebase is a must and powerful tool but if you are doing the same things again and again you should think about automating them and use your thinking-power and time for non-auto
14.
by zimmski 6y ago
I/we do but sometimes you just overlook something especially if there are a lot of changes. But having someone else review what you do almost completely removes that problem. I usually do not look through all commits again when a basic
15.
by zimmski 6y ago
Learning rebasing is one thing but wasting hours every week on rebasing because you are doing the same thing over and over again is another. When i do a one line fixup i just do not want to figure out the correct commit and then rebase i ju
16.
by zimmski 6y ago
git-autofixup definitely changed my daily development life.... I mostly use it with this Git alias ``` autofixup = !"autofixup origin/master --exit-code; test $? -lt 2 && GIT_SEQUENCE_EDITOR=true git rebase -i --autosquash