Details
-
AboutLead developer and commonly annoyed person
-
Skillsjava,php,python,web,systems
-
LocationBarcelona
-
Github
Joined devRant on 10/16/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@linuxer4fun cpp is for wannabe' systems developers. Chapel is the real deal... :>
-
Ughu. And by default all adsl routers have open remote admin access to movistar office ranges... You have to love Spain.
-
:D
-
Xps for portability, latitude for some serious work
-
Movie plot I think
-
Here you go
-
Horribly slow this one... Also big size cup takes 2 runs. Takes ages.
-
Internship. Experience > literally everything
-
Use foreign keys with restricts. You are welcome.
-
@Clouded number of possible uses and adoption. There are very small number of fields and applications Python cant be used for - not just web, but also systems, science, etc. Node on the other hand is not so widely used, mainly because JavaScript and V8 is probably not the best platform for anything than some certain web use cases.
-
Python and django. This isn't even a real question cmoon.
-
Not even mad
-
Should not be bad... unless you have users using 3g/edge and a lot of mobile traffic and not very sane caching. Then its catastrophic.
People out there still pay for traffic. So be careful. -
Main event loop is single threaded. IO like disk access etc is separate threads. As long as you don't do anything serious, it will work... somehow. Otherwise, use a language with proper threading and spin up as many event loops as you want. Lot more efficient than having a shitton of node processes with their half arsed ipc.
-
Next thing you discover will be that WiredTiger is actually a separate library. And you can embedd it.
-
... and that special place is meeting explaining why this is not ok.
-
@h3ll no multi repo reviews and no evolution tracking. Checked a while back tho. If still the case then nope...
-
If you are using IntelliJ, you can use local history for these little accidents. Available from right click menu. You are welcome.
-
I presume hes a bit of an idiot, is he
-
Or an í
-
Asynchronous node 😂 lol.
-
More like ~20 years
-
@kong run. Run and never look back.
-
Have you seen their HANA thing? Omg.
-
@Justananon bs. I said that code coverage alone without asserts is worth shit. Am I wrong? Then op assumed I am working on something I am not.
Literally everyone can write test with 100% coverage on couple of hundred lines. Not everyone goes on to vote-whore about it tho.
Then again, other devs can also be morons. This is how we end up with test suites worth nothing. If thats not worth the title, idk what is. -
Yes, good job.
-
Enjoy your neck pain. Workspace should be arranged so that you would not need tilt and turn your head. This will make you turn your head like that possessed chick from scary movie.
-
@ac1235 there is time and place for everything.
-
I'm dismissing nothing quickly. Young's entire "expertise" comes from coining a term for a slightly dangerous practice that has been in use for decades, repackaging it and marketing it nicely, and getting some small endorsement from Fowler. He has little authority in the matter. Apart from just-out-of uni "superstar" developers who consider V8 the next best thing right after sliced bread and parallel garbage collectors, and have too much free time on their hands - nobody cares.
-
First of all, large code base does not automatically imply legacy or monolith code. Apart from unit tests, there also exists specifications, integration tests, e2e tests etc. On a more philosophical note, micro services and strong segregation is also not a golden hammer for all the use cases. As with everything, common sense applies, especially on scaffolding level.
As for the random JS dude you just linked - fuck for? That talk is garbage, makes plenty of assumptions (incorrect ones, might I add) and author obviously lacks experience in design and maintenance of large scale systems. Shifting or splitting complexity does not prevent it, it introduces even more complexity. Separation of concerns can and should be maintained instead of blindly hacking source code apart and introducing extra complexity and points of failure in a form of common management of parts, thus reducing resilience of whole business logic.