If you don’t want to go full Cloudflare you can mitigate DDOS using these kind of technique locally.
https://blog.nginx.org/blog/mitigating-ddos-attacks-with-nginx-and-nginx-plus
Cloudflare will be a lot more effective in case of attack. But I don’t think most people need more than a few mitigation rules. If DDOS really come, there are very few things you could do to mitigate anyway.
I would suggest Helvix or Helvim
“Hi computer! Write me a program that make money. I must just run it and I become rich.”
malbolge
and just after haskell
I use this nice trick to use Clojure has a bash script. This auto-download clojure so this id quite portable and reproductible.
Previously I also used Haskell’s turtle lib that could run with a portable shebang and it could even be compiled later if you need more speed.
I use emacs org-mode and I export to markdown. If I must start from markdown, I use panda to generate an org-mode from it, and export it back once I’m done.
I don’t see how this could be positive for any Software developer in the long run. I totally see how this could be positive for CEO/CTO, Project Managers, in the long run, and I see a few short term advantages for Software developers.
Let’s be clear, I saw that coming since Microsoft bought Github, and I am scared by the direction this is taking. The end goal is to move more and more control and power to non-software people about Software development.
By forcing every developer to not use their own tools this will have a lot of advantage for CEO/CTOs but this is terrible for software developers:
And I can think of other possible drawbacks but my comment is already long enough.
As you only mention git and not any git hosting. I would say you could easily use git hooks. Fir you and probably ask everyone in your team to install the same git hooks to have a chance to review changes before they are commited.
For my team there is an init-git-repo.sh shell script in our repository. When you execute it, it will install all the git-hooks fir your local repository.
You can use them to add checks during commit, merge, etc…
Edit: I read a bit too fast. As you are using bitbucket there id probably the equivalent of github’s CODEOWNER file as already proposed in another comment.
nix does not need nixOS to run but is a complex package manager. At least for me, it doesn’t seem more complex than docker ecosystem.
I personally use nix to take care of downloading compatible dependencies in isolation for me. And the rest of the code is really, just basic script shell or Makefile too.
I also could add a fancy mergeShells function I have written in nix to support a docker-compose-like composition of nix-shell files.
But you could go a very long way with nix before you even want to do something like this.
I use a similar approach, but I went further by creating a system that compose like docker-compose would. The trick was to write my own nix function mergeShells.
https://her.esy.fun/posts/0024-replace-docker-compose-with-nix-shell/index.html
For now, I am pretty happy with it. Also, I put the init script inside nix-shell and not in external files and use exit signal to cleanup the state.
This was a very great article to read whose title does not make justice to the content.
I think I kind of dislike the generalization on generation. To me recently there are simply a lot more people that see programming as a job and not as much as a passion.
I learnt programming as a scientific activity and not as a productive one. So this was driven by creativity. And many in my promotion shared these values. But even in my time, many were just interested in the job. And of course, these people were not as effective. They were mediocre in comparison to people programming in their free time.
And yes, there is probably a lot more people like this today, in particular in younger generation. But there are still a lot of people programming for fun in their free time in the latest generation. This is just, they are now hidden by the majority of more “normal” people. Because let’s face it. Attitude of people programming during the week-end for super long hours while still programming for work during the week is not sane and abnormal.
Edit: a big missing part is that passionate dev are not necessarily what company prefer. Because yes, they can do incredible work. But quite often I see company prefer to have few of them and a bunch of more mediocre but reliable developers.
“The congress” is coming closer.
https://www.themoviedb.org/movie/152795-the-congress
I understand why some people might not like this movie. But I think about it a few times a week. And one major part of the scenario is about a famous actor giving her digital copy to a studio and the unforeseen consequences.
The morons… Why use a computer if you don’t have full power?
As a lead I could stop coding. But I choose to keep time to code every week. I believe this is very important to keep in touch with the reality my reports are facing.
So this is possible to still code but this is not natural. Sometimes I simply cannot have the time to touch any code for a few weeks if I do not take care about it.
The first pass of elm ecosystem solved it. Before elm, it was also solved by other frameworks. But people wanted to be able to reuse their components and not rebuild new ones. React provided the ability to reuse css, and dirty js code in the middle of your application. You already had an way bigger ecosystem because you didn’t have to learn and built a complete new system again.
Personally if I had the choice I believe a new start should start at the browser level. Stop supporting HTML/CSS/JS. Create a new app-centric DSL and not a document centric one like html/css/js.
Ideally something inspired from cocoa layout. And I am dreaming but not accept generic code on the client side and only support a small controlled API. It would solve so many security issues. Sure, the creativity in such an ecosystem will be severely reduced. But we will have a so much improved UX.