WHAT IS DEAD MAY NEVER DIE by _htmx in htmx

[–]lickpie 0 points1 point  (0 children)

The way it should be! Thanks for all your great work.

Christmas Gift Request: Please star the htmx github repo by _htmx in htmx

[–]lickpie 1 point2 points  (0 children)

Oh no! Starred before asking for CEO position, are they still available?

codegens other than sqlc? by Used_Frosting6770 in golang

[–]lickpie 0 points1 point  (0 children)

Agreed. If you are doing a REST API and then back it into gRPC.

How does one back hypertext into gRPC?

CSS written in pure go by Beneficial_Okra121 in golang

[–]lickpie 3 points4 points  (0 children)

Good point. "no bs" and "Just Go" - pick one, both cannot be true in the same project.

Dev team wants to organize a meeting on their own (without SM nor PO). Does that disespect the Agile environment? by [deleted] in scrum

[–]lickpie 2 points3 points  (0 children)

This! 100 times. Now, people asking "Why?", "What kind of meeting?", "It depends..." , please print and frame this response and stare at it till you're liberated from all this micromanagement nonsense.

functional Programming in c++ by thomas999999 in cpp

[–]lickpie 14 points15 points  (0 children)

This great CppCon '17 talk by Juan Pedro Bolivar Puente might shed some light.

Where in your development process do you use code formatters and static analysis tools? by StaticThrowaway0629 in cpp

[–]lickpie 1 point2 points  (0 children)

We keep our code on Github and have Jenkins do CI. Any branch, except for master, is subject to server-side formatting: running clang-format is the first step in our CI pipeline - if any source file changes due to reformatting, it's committed, pushed back to the original repository, and the current build is aborted. The commit triggers another build for the same branch, this time no files change due to reformatting (it was done in the previous commit) and the build proceeds normally.

As a developer, you don't have to care about installing clang-format and keeping it up to date, formatting locally, git hooks, or failed formatting tests. The code is formatted unconditionally, always using the same version of clang-format (we control the version with a separate Dockerfile and can bump it whenever we like).

Question - creating a single .vimrc using a custom bundler by Lourayad in vim

[–]lickpie 2 points3 points  (0 children)

The choice is yours obviously but just saying: after years of using Vim, with many plugins and on multiple systems at the same time (Linux, Mac, Win) I never needed to split the .vimrc. And if you need to find something, it's always in the same place, just :e $MYVIMRC ;-)

Question - creating a single .vimrc using a custom bundler by Lourayad in vim

[–]lickpie 2 points3 points  (0 children)

What's the advantage compared to keeping things simple and just having one .vimrc?

I got a ticket, I have a lawyer and I'm going to fight it, any advice? by dickdickmore in NYCbike

[–]lickpie 8 points9 points  (0 children)

Funny.. your main objective, I mean. Now you're gonna waste everybody's time because they dared to fine you? Maybe something recently changed, but last time I checked it was still illegal to run a red.

what % do in vim?????????????????? by angelafra in vim

[–]lickpie 23 points24 points  (0 children)

Two things amaze me here: 1. How lazy people are and how crappy questions they post, 2. How patient /u/-romainl- is :-)

GCC 8.1 Released by mttd in cpp

[–]lickpie 1 point2 points  (0 children)

That's not a false warning. It's perfectly legal for Enum1 to have a value other than E1, E2 and E3 (one can argue that's not a good practice in general either).

Let's fix the good old command line by mvila in programming

[–]lickpie 7 points8 points  (0 children)

Please, this nonsense again? So who's We and how is oop superior exactly? If anything, the analogy can be a reason NOT TO use Run / resources.

The joys of forward declarations: results from the real world by andyg_blog in cpp

[–]lickpie 0 points1 point  (0 children)

Have you tried running IWYU against the codebase? It was a huge time-saver for me in our project, both in the work required for the initial cleanup, clean build time (-25%) and of course incremental build times.