@ThePrimeagen@igorguemusic there was nothing really to build before nodejs came along. The js code would run, w/o build, in the browser as this was the only place it could run. So I am not sure if js should pick up that responsibility just because someone decided to take the langauge out of context.
@semanticart Ok thanks. Sounds interesting for sure. But I assume as opposed to a canary, it adds complexity to the codebase. Because the code doesn't need to care about canary but it needs to contain extra logic to conditionally serve a feature or not.
@semanticart I just found this sentence: A canary release is also different from a feature flag release, as feature flags are used to expose a specific feature to a small subgroup of users. A canary release exposes a specific version of the entire application or service.
@Carnage4Life Sounds like a fallacy. Just because a real rockstar may not play well with a real orchestra, which has to be proven first btw, doesn't mean this translates to a team where there is neither a real rockstar nor a real orchestra.
@gunnarmorling Mock is a bit of s generic term. It depends on what you are mocking I guess. mocking I/O is perfectly fine, imo. For example, It can be real hard to spin up half of your service fleet to run tests, locally.
@t3dotgg Hooks are useful to automate some of my own tasks. Meaning they are personal in a way and ment to aid. For quality gates the only thing that makes sense is CI on pull request. Hooks can be bypassed anyway, so you cannot make them mandatory and you cannot trust they they have run.
@ngriffin_uk@t3dotgg If this stuff isn't running on you CI server, it doesn't do anything as those constraints can be bypassed or not even enabled. If it runs on the server, what do you need it locally for? Hooks can be useful in some cases, but not to enforce constraints.
@GabrielRUrbina@ThePrimeagen I think one commit with a good message per PR, is the way to go. I usually do a bunch of commits with garbage messages and then do squash merge. But I also know projects doing a normal merge but requiring you to rebase/squash your feature branch beforehand. More or less the same.
@rawkode Once again, no one with imposter syndrome would say they have it's. Saying you have imposter syndrome indicates that you think you are better than you are, in reality. So it's quite the opposite from imposter syndrome.
@tottinge Until they are in the middle of the way more simple rewrite and realize why things have been done this way. All the small things to consider, are missing when judging while glancing over things.
@christiancmann @ansonphong@kentcdodds Bottom line is, yes there are solutions. But why would I make my life harder? If you don't have your brightest day, this stuff can cost you some time, to figure out and fix. I rather not create avoidable pitfalls. So I can sped my time or something else.
@christiancmann @ansonphong@kentcdodds Yes, you do want spaces. But it's very hard to tell how to align properly if your editor is hiding the true indentation from you. Say you need to make sure your string is indented under a certain key or variable to have valid syntax.
@ansonphong@kentcdodds I had already issues with that. When you use a multiline string and it looks ok in your code because tabs are displayed in a certain way, but actually it's broken. I had it in go and cue. So if tabs then 4 space width or nothing, for me.