I don’t mind xml as long as I don’t have to read or write it. The only real thing I hate about xml is that an array of one object can mistaken for a property of the parent instead of a list
I don’t mind xml as long as I don’t have to read or write it. The only real thing I hate about xml is that an array of one object can mistaken for a property of the parent instead of a list
I’m going to suggest not using an ORM. I used three so far and it really likes to tell you what you can and can’t do when query builders can do the same thing by creating the SQL string for you. SQL is also very nice and easy (just parameterise all inputs to avoid the SQL injection)
Yeah, I 100% agree. For small projects most of the principles don’t matter as much because the complexity is just not there. For big projects you actually need to take a big ass tech debt loan to actually get things done on time and on budget.
The testing aspect I’m not as sold on either. I enjoy tests sometimes but they also come with increased development and maintenance cost. He emphasises unit tests but I’ve found that a few integration tests that use API calls to simulate a use case gets you most of the way there.
That being said I’ve seen raw HTML email string with hardcoded values in a 2000 line method that relies heavily on if statements. That one method probably breaks around 10 of his rules and I absolutely hate it. Very hard to add features to if you can imagine and incredibly noisy and hard to debug. Shouldn’t be like that but it is. I wouldn’t apply all of Bob’s rules but I would refactor it into a service with clear boundaries so I don’t have to deal with the function having “local globals” if you know what I’m getting at.
He wrote for example the books Clean Code and Clean Architecture which are IMO opinion really good books although I don’t agree with every point he makes.
Some really good points he makes are for example:
Those comes with examples. He’s a tad bit overly idealistic in my opinion. These books fail to mention a couple of things:
All in all though, very solid books. I read Clean Code in university and Clean Architecture in my first job and it really helped me wrap my head around different ways to solve the same problem. Excellent ideas but it’s not the holy truth. The only reason I remember all of these points is that I encountered all of them on the job and saw the benefit.
In my opinion new programmers should read it and take inspiration. Craftsman level developers should criticise and maybe pick up a few brain concepts to sort some concepts out in their brain. Experts will get little benefit though.
This one goes right to the feels. I’ve got pretty good experience with using SSR components to generate static html with components. I’m currently using dotnet and blazor where I can make email components like a button and an image as easy as that might sound.
I mean, if you’re really good at SQL these requests are doable in 10-30m + the time it takes to run and export.
Those are nice. Services that manage data are an example. Having the class also declare how to interact with the data is nice.
My most OOP pattern I like using is implementing an interface with an abstract class for “standard” implementation. Then implement abstract methods for a concrete thing.
And maybe you have some functions that interact with them but don’t keep them super public so they’re only used by specific modules/store/redux thingy?
Using classes is nice tbh. Using inheritance usually isn’t. Inheriting from inherited class should be forbidden.
But you have used objects I think.
I use vim macros. You can do some crazy formatting with it
I work 30 hours remote and cost of living is pretty ok.
In the Brolien universe it’s called Wheyland
Yeah, it’s so out of touch, at least put “192.168.1.*” or something. It’s very individualistic.
Depends on how what dummy proof is. Not being able to shoot yourself in the foot and main line success case is easily navigable by people that are bad with tech is dummy proof to me. Not possible with all programs ofc.
“LGTM, merged” 😏
I forked an opensource project to add a couple features for my wife. 😊
From Wikipedia I see that they plan to get it up to 16.8km or 55k feet high. This means that drag will basically not be an issue anymore at the cost of higher take off fuel.
Very interesting to see how this pans out since it would create direct flights between Sydney and New York.
My question now is about whether the the elimination of drag will save more fuel than getting the plane this high up into the sky.
Wow, the calculator analogy is excellent. I’ve done my fair share of getting an AI to answer with instructions on how to form a drug cartel. Now I realise it has the exact same feeling as writing BOOBS
on a calculator
People may hate on SOAP but I’ve never had issues with setting up a SOAP client