lpapez

10 ms·

91.
by lpapez 2y ago
People have been saying the same thing about Internet streaming of music for example. It didn't destroy musicians, just changed how they make their money. Musicians today generally publish music for free, and make money from concerts a
92.
by lpapez 2y ago
Maybe these optimizations benefit the two users who do the operation three times a year. In such an extreme case no amount of optimization work would be profitable. So the parent comment asks a very valid question: how much total time was s
93.
by lpapez 2y ago
Amazing release, Postgres is a gift that keeps on giving. I hope to one day see Incremental View Maintenance extension (IVM) be turned into a first class feature, it's the only thing I need regularly which isn't immediately there!
94.
by lpapez 2y ago
> And why on earth would you have a dedicated scrum master?! It's just not a job that should be requiring that much labor. At most places I worked, having a dedicated Scrum Master on the project was the norm. Yet another case of &qu
95.
by lpapez 2y ago
You can easily write a Tampermonkey Userscript for that. As HN doesn't update the CSS that often, should be quite low-maintenance solution.
96.
by lpapez 2y ago
Peak HN comment.
97.
by lpapez 2y ago
> It may be explicitly stated, but I’ve never had a scrum meeting without all managers and project managers. This, this, this and a thousand times this. It's always the same with Scrum. Every time you point out something clearly wro
98.
by lpapez 2y ago
I was there in 2010s migrating Mongo databases chosen by "expert consultants" to Postgres and dealing with the fallout of massive tech debt those decisions usually caused. Won't get fooled again - no matter how many fluff art
99.
by lpapez 2y ago
Absolutely. If an item has been on your TODO list for years, it's most likely not worth doing anyway. Might as well lose the paper upon which the item is written.
100.
by lpapez 2y ago
> It's legacy in the "we would never invent this as the solution to the problem domain that's today asked of it." I don't think that definition of legacy is useful because so many things which hardly anyone calls
101.
by lpapez 2y ago
SQL a legacy query language? In order for a thing to be considered legacy, there needs to be a widespread successor available. SQL might have been invented in the 70s but it's still going strong as no real alternative has been widely a
102.
by lpapez 2y ago
Honestly I hope the LLM-powered bots will be hugely beneficial for the online discourse in the long term (and keep creating mayhem in the short-term). My hope is that long-term people will realize that most of the arguments and outrage they
103.
by lpapez 2y ago
As announced by their CEO in the previous decade...
104.
by lpapez 2y ago
> The average developer won't see these things, they're typically just writing glue code between Go's great stdlib (which also contains wild things if you take a look) and other 3rd party dependencies. This is what most of
105.
by lpapez 2y ago
Why not start with SQLite? There are benchmarks out there proving that for some use cases (i.e. many small updates) where using SQLite is faster than using the filesystem. [1] So not only do you get all of the benefits of a relational dat
106.
by lpapez 2y ago
I once saw a project in the wild where the "database" was implemented using filesystem directories as "tables" with JSON files inside as "rows". When I asked people working on it if they considered Redis or Mon
107.
by lpapez 2y ago
I don't know, but personally I've spent orders of magnitude more time debugging memory leaks in languages without GC than the time I've wasted waiting for shitty apps to load. Software bloat is a real thing, I agree, but it&#
108.
by lpapez 2y ago
> Insanely smart optimizations done. But then you rewrite the whole thing in vanilla Rust without profiling once and it's still 20x faster, and much more readable than the mix of numpy vectorization and C-routines. I'd argue th
109.
by lpapez 2y ago
Have a look at Laravel Breeze. Has most of the things you mentioned right away, and if you need payments Laravel Cashier makes it easy as well.
110.
by lpapez 2y ago
Similar story. Suddenly when starting WFH the management required detailed time tracking and summaries of each day. Somehow tracking productivity was not seen as neccessary when we were all sitting in a downtown office scrolling through Red
111.
by lpapez 2y ago
Writing an exploit is usually much more difficult than patching the underlying bug. Half of the work in fixing a bug report is getting a reproducible example. Nay, more than half. If there was a magic AI which could generate exploits, I&#x2
112.
by lpapez 2y ago
> If you're earning past six figures, are part of a team of programmers... Compensation is in no way correlated with good engineering practices. They might be paid much because they're developing something which people are will
113.
by lpapez 2y ago
> When I WAS the bane of my existence was senior and staff engineers hoarding all the fun, new work for themselves and forcing me into "bitch work" where I'm just cleaning up old, broken code and handling bugs. Oh how I re
114.
by lpapez 2y ago
> The way scrum is implemented in 90+% of the cases is a complete mockery of what it was supposed to be. Can you really say it is misunderstood if 90+% of people are "doing it wrong"? Is it a useful thinking framework if there
115.
by lpapez 2y ago
Unsafe in Rust is not unsafe in the same sense that C/C++ UB is unsafe. Unsafe in Rust means "soundness cannot be statically verified, the language will insert runtime checks for you and perform a clearly defined action (panic) if
116.
by lpapez 2y ago
I feel like this new wave of RTO is the same like any other org change disliked by the lower ranks. Competent people switch jobs, while incompetent are fired, and the mediocrity stays and grudgingly conforms which is exactly what companies
117.
by lpapez 2y ago
> Consolidating code is easy, pulling it apart is a lot harder. I absolutely agree with this, and the only thing I would add is that is difference is even more pronounced in codebases using a dynamic language. Sure it's not easy to
118.
by lpapez 2y ago
I have not saved any links to back this up. It is just my personal observation formed from working with Mongo and migrating systems away from it.
119.
by lpapez 2y ago
Kudos to the author for reevaluating his opinion and changing heart on a technology he admits to have championed before. IMO GraphQL is a technological dead end in much the same way as Mongo is. They were both conceived to solve a perceived
120.
by lpapez 2y ago
The PHP built-in server is explicitly stated not for production use, and is intended for development purposes only. See the warning at the top of the page: https://www.php.net/manual/en/features.commandline.webse

More ›