208 karma · joined January 31, 2013
This movement is brilliant for them
ORMs would be my next battle, but SQL injection could become an issue if not treated carefully, so I would still consider libraries like SQLDelight or other SQL first libraries
I want that experience to be good, and not using a subpar tool like (Teams, IRC etc)
As a rule of thumb, I want to use the best tool available for the job, IntelliJ for the IDE, the best coding model (whatever that is at the time), the best Video call tool, the best monitor, the best keyboard etc
Although best is usually subjective, in some of this cases what is "best" is objectively clear, in some cases the gap between the best and the next one is small in others is huge. In the case of communication tools I think the difference is huge.
Is this needed to do my work? nope It makes working more pleasant? definitely yes
Avoid July and August, horrible heat and most people have left the city
27” 5k (5120 x 2880) -> 218 PPI
32” 4k (3840 x 2160) -> 137.68 PPI
34” 5k (5120 x 2160) -> 163.44 PPI
39,7 5K (5120 x 2160) -> 139.97 PPI
Apple Pro Display XDR 32" 6k (6016 x 3384) -> 218 PPI
ABNB creates externalities to the countries where it operates (increase rent prices), so it would make sense to tax them because of it.
And if they don't like the tax, they are free to stop operating in that country ;)
I guess ultimately it depends on which language you are more familiar with...
That’s even cheaper if you hire them as contractors
I see this being a trend in the coming years
Trust is a big part of stock value, if you don't trust the board is time to sell...
It would be nice to open just one PR with several sets of changes where you could provide context for each set of changes.
With GitHub you could do this by having a commit per each set of changes, but you can't add a description for each commit.
You end up having a PR that points to the previous PR, and then you have to decide if you run CI in that PR or just the last PR, and then having some merge issues. With all this hassle people usually just open a big PR with all the changes or decide against doing that small refactor (because it would have to do it in another PR and the hassle is not worth it), overall this ends up decreasing code quality in the codebase.
Maybe I'm over-hyping it, but I really doubt there has been a UI toolkit with that much work behind in a long time (Maybe Cocoa and one of the last 3 iterations of UI toolkit on Windows had that many work hours, but Cocoa does not work in all OS and the Windows ones well ... :shrug:)
I think this also should be something that other governments should take into account when taxing the newly legalized cannabis business, if you tax it too heavily from day one you may be pushing clients both clients and producers to the black market.
It forces you to think a moment for a good PR title, but it is an small price to pay when it gives you a 0 extra work changelog that is good enough for semi-internal use.