AboutDevOps Undergraduate ECE student Interested in Theoretical Computer Science, Mathematical Logic and Computability
SkillsJS, C/C++, Haskell, Common LISP, Python, C#, Java, PHP, GoLang, lambda calculous, category theory, Mathematical Logic and whatever it takes to dominate the world... 😎
Joined devRant on 6/7/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Since I have seen a lot of people uploading this kind of stuff lately, here is Xiaomi's test in production, back in 2017 November...1
I bought a new carbon fiber bike (I am into cycling the last two years) and it is fantastic. Lightweight, it feels responsive as hell and really easy to sprint on. BUT, I am fucking sick and I can't ride it to train... All I can do for now is looking at it. FML.8
Archbang, Archlabs or Manjaro?
I am interested in using i3 as my wm. And because I will install it in my daily driver laptop, I want it to be reasonably stable and not with breaking updates.
Any thoughts and / or recommendations?11
Could somebody please help me understand why the fucking hell does JS (I am talking about node.js, so backend) use 32bit integers in setTimeout and setInterval? I mean, I understand most of the choices regarding the language (I have chosen programming languages design and principles for my studies) and I am happily using it for almost 4 years. But I came across an occasion that I had to use big numbers in those functions and it took me a lot of time to figure out why the fuck my code was not working as it was supposed to.
If anyone has a good reason please elaborate. In the meantime I'll go punch some shit to calm down.10
I prefer starting from theory and then proceed with practicing. For example, to learn haskell and deeply understand it, I started by taking a course in category theory and I already have a degree in computer science and then start writing actual code. The same with JS. I started with theory for JIT compilers and studied how V8 works, how it utilizes event loops and how they are implemented in the kernel. Then I started experimenting with code and demos. It's a success path for me, that has worked every time with every new technology.2
!rant Just random thoughts
Funny things aside, our job is very important when it comes to influence people through ads, well presented "studies", quizzes and polls that contribute on people's decisions. I think we all have some kind of story that we can more or less relate to what is described in the article below.
It would be wise to think twice not only about algorithms, UX and implementation details but also about ethics. We should not have as our primary goal to make the browsing experience more pleasing but safer and easier to avoid scams and traps.
Your thoughts on the topic?
A place where you can evolve your skills, competitive and that you're respected.
And NO FREAKING CLUELESS PROJECT MANAGERS that do not understand how software is "born" and expect you to catch insane deadlines...
One night, after one very stressful week of production code fixes (I was working on a game with some friends and I created the network infrastructure for P2P and database communication from scratch), I was at my gf's house. After we fell asleep, I stood up and screamed right at her something like "I fucking already told you how X works and how to communicate with Y. Learn to write code properly and after double checking yours then you shall ask me for a non-existing 'bug' fix. Learn how to properly write event based code and use polling you moron!". After that I turned to the other side and fell asleep immediately.
When I saw her the next morning sleeping in the couch, I could not understand why... Only after she described to me the whole incident I started laughing.
After that I just took two weeks off the project and after that period I never actually worked the same way (so hard) in my free time with them.1
I am sure this has happened to all of us in some extent with some variations.
Colleague not writing comments on code.
Ask him something like "How am I suppose understand that piece of garbage you have written when there is no comments or documentation?"
This keeps happening for a long time. Some time after, I write a kernel module using idiomatic C and ASM blocks for optimizations (for some RTOS) and purposely not write neither documentation nor comments.
When he asked for an explanation, I answered to everything he questioned as general as I could for "that trivial piece of code".
After that he always documents his code!