Git never intended to have a super important branch name. Just a sane default. Now you two defaults for no reason at all. Git itself is flexible to not care at all.

It costs me extra time to set up aliases so I can just use consistent commands. It muddles confederations because main is often used as code entry point in programming languages. Not frequently but sometimes when someone mentions "I've made a change in main" it needs leads to confusion. Master is simply superior.

Update?

Justice for @whimsical!

Bonus points for "huisjesmelker" and justification!

Even though I agree that it is a programming error not a memory error. I've seen people write worse Rust code than they would in another language just to make the compiler shut the fuck up and finally built that thang. This might fall in that category.

@YourMom there can be quite some speculation about a lot of things mentioned here.
However please don't tell people COVID-19 was an exaggeration and not all that dangerous. That is like denying the Holocaust to the people that actually lost loved ones in it.

Here is a statistic that can't be exaggerated or explained away. Is Italian death rate over the years. https://macrotrends.net/global-metr...
Clearly something happened in 2020... To cause an unpredidented 17.92% increase

I love TOML first saw it with Hugo (static site generator). Don't know if it suits your purpose but if it does, good in you.

@null-pointer-ex I disagree with that. I've had the need for that quite a few times in the API. Mainly to resume work after a restart crash on processing a large result set. I do like record offset for this better than actual page offset. For previous/next or doom-scrolling (lazy loading) one also needs windowing in the API.

I've seen an edge case in UI too where the user shares a link with a specific page with another user but that is a very rare one. (Used to divide the work going through a list giving each worker a different starting point). But all edge cases I've seen can be solved by something better.

Don't you mean "At least it's not Germany"?

Why are you looking for a reason when reasons exist?

Well that's nice you don't even need a DB admin or install/setup a DBM client.
And it handles indexes for you like a champ. I wish i could work with that kind of talent.

Without sarcasm this doesn't have to be a security issue. Can even by a security layer as it limits direct database access. In hardened environments the service should usually not have permissions to create/alter/drop tables though.

Perhaps I am misunderstanding you. Are you against pagination in a UI because of bad UX, or as a data windowing solution in general?

Your problem was being tied to one language in the first place. Unlike Thor carpenters use many tools. Really good ones can use a few different tools for the same effect. Yet they understand the reach tools unique properties and use that (or deem it useless/redundant).

Your task is the same. Don't learn a language/stack just because you want to but because it makes sense.
Perhaps Kotlin is a better fit; or Go or Python. Why specifically C#?

@wojtek322 is the example the correct way to implement it with variable names that everyone is using? Then please copy it and alter if just enough to suit your needs. One needs to understand the code to alter it to your needs...

Anything else leads to Not Invented Here syndrome and cryptic code. Not something you want in a cryptographic implementation trust me. Almost all security issues with cryptography are not inherent of the algorithm but the implementation.

Feels like something that has very little value in being human readable. That makes your file formal unnecessarily huge and slow parsing. Highly suggest using existing file formats or something binary.
You can always write an optimal -> TOML converter for debugging if that is needed later.

A lot of things are covered by trademark laws but them including this makes it easier to remove crap that is in violation without a whole potential law case.

@PaperTrail <- name checks out!

Not being able to use code from docs is insanity. It's literally the reference material for good implementation of the API.

This is a course made by people that never in their life made a piece of production code and fail to understand the basic concept of programming: you can't build it all yourself from the ground up every time. This is why we have operating systems in the first place.

Unless you want to write another HollyC and TempleOS of course or only people that do that...

That is a sign of a logical and consistent API. Nice!

I've had most luck with Go regarding oneshotting code. Language is simple and strict enough that auto completion goes quite far.

PHP managed to mix them up.
Basically if you can use a map as an array you don't need a struct.

Political topics are in violation of DevRant policy. This crap is the reason. Please post dev related stuff here.

As per usual you are wrong.
The Dutch word for hat is hoed...

Petje af, is what Dutch use for Chapeau

Wonder if it's possible to do a version that does not exclude female coders.

@AlgoRythm you need to have quite some brain capacity to write rust without the compiler complaining. However what they write might be convoluted and overcomplicated.
I generally don't like the push is rust everywhere. The reason is that it's a novelty reason instead of actual benefits.

It's a tool, a bit of a cumbersome tool at that. So the specific benefits better be worth it to do the specific job.
Most people I've seen choosing rust, do premature (performance) optimisation.

@torbuntu I'm fine with that as long as it's stability over speed.

For example there might be a better way of doing it or some polish but if the code as is solves an issue without introducing new ones it's better to push it out and either not close the ticket yet or create a new ticket that has to be picked up before any expansion on said suboptimal code.

There is a lot to be said for keeping momentum. This makes the team feel more productive/motivated. If you put safe guards against the really bad stuff like stability and compounding tech-dept you actually get a better quality codebase and faster. That's the beauty of iterative development.

There needs to be a balance between suggestions and blockers in a review. This is really hard sometimes for me too as I'm quite the perfectionist.

That said I've also worked with truly incompetent people and nothing breaks momentum faster than they do.

Yeah that service is broken and bleeding info at least to vulnerable to SQL injection...

This is outside of your control and not something I would consider a bad judgement call of you. If a manager would have set the deadline it would not be the managers fault either. Picking the service this API belongs to though, now that requires some further questioning.

Edit: misread that. Stuff still stands except for the security issue

I think some of the cons can be fixed especially if the bosman is chill. I'd start with the bus factor and combine that with the alterior motive of working with seniors.

Try to expand your sphere of influence s bit without so grosely overstepping that people feel you are going behind people's back or the guy that thinks he's all that.

If that doesn't work you can always leave. Stating the lies and no financial upside as reason while not burning them as potential client in the future.

You can get quality speed though, so they are not mutually exclusive🤔

@antigermanist its just Latin languages weirdness, so French Spanish and Italian do it.

Not even in Greek is the adjective placed behind the noun.

They already tried with COBOL. Back then IT was also considered a cost center. Quite some people still need to be cured from that...

Also stay consistent in using English it's AI...

Never heard about this one, thanks!