zkomp

11 ms·

61.
by zkomp 9y ago
Sigh. Slackers gonna be slacking. Why are we regressing back to the horrible world of vendor lock in and single browser sites. Chrome is the new IE6?
62.
by zkomp 9y ago
I can agree slightly on some of this, but it quickly miss the point completely and is not even funny or satire. It is quite simple: just skip the people and or technologies that make you vomit in your mouth and go for the interesting parts
63.
by zkomp 9y ago
It was a good talk at fosdempgday. Well paced, funny at times, esp the part comparing booleans with mysql "booleans" and "check constraints" (spoiler neither boolean nor checked) Too bad I'm stuck on 9.1 for the tim
64.
by zkomp 9y ago
eeerm... Yeah, like Facebook (it's the actual name) (best to just spell out the obvious)
65.
by zkomp 9y ago
This is still playing the game / i.e executing the instructions. Exactly the same instructions on same hardware that were distributed to everyone... This is just the extreme form of the fastest way to complete the game, using the (bro
66.
by zkomp 9y ago
I disabled most notifications but is still occasionally hit by this; more annoying imho is trying to use siri-app "suggestions", the exact moment you press it often reorganize the icons making you enter something completely unrela
67.
by zkomp 9y ago
In Stockholm, there is one journal system everyone is mandated to use, written in APL (was called Take Care but could have changed name), and completely without access control. I believe each institution get printed access logs sent to them
68.
by zkomp 9y ago
Sad to see Apple drop the ball completely with all the little things. I've seen issues with the touchbar and keyboard from all my collegues. As a long time apple user, (since forever, early 90ties) I will never buy one of these pieces
69.
by zkomp 9y ago
Hmm are you sure? I've read the fractal of bad design many times. Some issues might be "fixed" but could they fix the actual *fractal of bad design"? Isn't it still a mix of c-style, java-style, inconcistent, left a
70.
by zkomp 9y ago
Ouch I did not know Valve had sunk so low... String matching parts of a local username alone can not ever be enough for a ban... Completely ridiculous
71.
by zkomp 9y ago
I don't get it either. Neither see the supposed (objective) "errors" in the language design. Why not have both raise/rescue and throw/catch when the used are different. And why not have both methods, functions and c
72.
by zkomp 9y ago
First thing I do on every new device, computer tablet or phone is disable the stupid autocorrect. I can't understand how it can be the default. Spellcheck and suggestions are fine, autocorrect absolutely not... The more languages you n
73.
by zkomp 9y ago
(have we come to some max nesting level here, cant reply to the child comment) One db can be a problem, or a strenght depending on the domain; And I really dislike religious design, esp microservices. I have less problems by avoiding ORMs (
74.
by zkomp 9y ago
I like data. A database is created to handle it, give you tools to query, modify, scale, secure the data. A rest api... how and why should it be responsible for your data? It solved a different problem. You might not even need a database I
75.
by zkomp 9y ago
I personally would write a simple plpgsql stored procedure, but I would not trust user input and only allow a defined set of colums from a defined set of tables. you can have lots of dynamic sql but that might become a rabbithole, just as w
76.
by zkomp 9y ago
The db is separate and the interfaces are defined and the test is for this interface (as part of the schema repository) You dont need an ORM for testing your code... But I think this varies from project to project. How many different applic
77.
by zkomp 9y ago
I think bussiness logic in the database has prevented disasters in the projects I have worked on. I honestly dont see how it could have been solved better... It probably depends on the domain/problems. My experience is with transactio
78.
by zkomp 9y ago
As far as I know, in my experience. Stored procedures in postgres are good when you really use the database and care about the data, you need transactions, need to handle races and concurrency etc. Whereas ORMs break down at this point or p
79.
by zkomp 9y ago
you solved isolation decoupled much of the db logic from app-logic and made security easier you can deploy schema changes independently you can change everything and the app should not notice
80.
by zkomp 9y ago
There are several such tools, which are specialized and thus tend to perform a better job than orms (who try to do everything) But I would recommend writing, reviewing and deploying migrations by hand, esp for critical parts of the schema (
81.
by zkomp 9y ago
I disagree. ORMs dont bring value, they dilute value and piles abstractions upon apstractions. Your application becomes hard to maintain, database hard to refactor, queries slow. ORMs seems nice for simplified problems but becomes a horribl
82.
by zkomp 9y ago
No. You should really wind up with a DAL. Define some stored procedures for accessing and working on the data and use only stored procedures. No need for ORM, and no inline sql logic in your application code.
83.
by zkomp 9y ago
But why do you need these containers of data, when you could have more direct access to both the data itself and the whole set (not individual objects, nor collections of objects) I dont like ORMs but did struggle some years trying to use
84.
by zkomp 9y ago
I disagree. It is not at all a design mistake in sql. You can have or forbid null values in tables. And you need that for many things. It is properly designed. Rust or functional languages show you do not generally need null references, you
85.
by zkomp 9y ago
(As the other comments already said:) null references are not the same as null values. A database sometimes needs to model this case: the value is unknown: maybe the paper file you digitized was corrupted or destroyed, or other valid reason
86.
by zkomp 9y ago
In sweden, yeah, two things: there has been much, too much, batshit-insane anti drug/prohibitionist propaganda for decades. And the fact nations are bound by the UN Convention that mandate prohibition. Politicians are retards who rathe
87.
by zkomp 9y ago
Smaller changes tend to be safer and should break less. The less you change at one time, the better and less bugs which are easier to spot and fix. But if safety does not matter, or its pure crap anyway. Then refactor away. Proper review of
88.
by zkomp 9y ago
"Essentially, even one or two weak reviews in a chain of reviews can break the entire consensus system with a catastrophic bug. Hopefully, this can be an object lesson in making sure critical changes are reviewed very thoroughly. Stay
89.
by zkomp 9y ago
Just want to add one thing about swagger: please think through your API if you are to design an API, the tools will not think for you and you can fool yourself instead... Swagger will not magically solve anything. I have seen and experience
90.
by zkomp 9y ago
Yes absolutely: this very magic is precisely what is so horrible and imho a rabbithole of insanity. It is CORBA resurrected with XML. In my data oriented mind, the primary thing that matters is the data that is sent, the second is other sem

More ›