AboutBachelor in CompSci working for a big company, hoping to get enough experience to actually work with something relevant and related to his interests.
SkillsLanguages: Python, C/C++, C#, R. Other Stuff: Unity, VR, Machine Learning and a bit of Robotics.
LocationManaus, Amazonas - Brazil
Joined devRant on 8/1/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Most of the code I write nowadays is for GPUs using a dialect of C. Anyways, due to the hardware of GPUs there is no convenient debugger and you can't just print to console neither.
Most bugs are solved staring at the code and using pen and paper.
I guess one could call that a quirk.12
I'm sorry, but who thought eslint or any linters for that matter were a good idea.
Started a new vue project using the cli, installed tailwind... oh what's that you don't like the line length... get out of here. It's an SVG and using a class-based framework. The hell.
Any way of removing eslint? I just want to code and not get bs warnings because of an svg length or because I add one to many classes.16
There's this one lead dev in our dpt who keeps posting pictures to our company's Teams 'general' channel with shit in the toilet after someone forgot to either flush or use the brush.
Caption usualy says "I don't mean to cause nausea to anyone, but we are all adults here and should know how to flush / use the toilet brush".
Does every company have this guy or are we the chosen ones?9
My Love I am writing to you from the front lines roughly 1 month into Microsoft Access. I hope you are doing alright and no harm has found you.
You might have heard the news that it has not been going well for us. The truth is we were not prepared in any way for this. We are constantly facing problems with the code and when we understand one function another two are referenced inside of that function.
The high command does not provide us guidance, truth be told I do not think they know what their application is doing. I am surprised we got this far. Our new objective is to focus our primary forces on the if/else and cases. The name for this assault is "Operation Logical Function" and I fear for my life as I do not know what is in those cases or where the road will lead.
Morale is very low, many of the soldiers spend time writing letters to their loved ones, recreating their blog for the 5th time or just daydreaming when they were free from this tyranny of legacy war.
For now , I long to be in your arms and smell your lilac and gooseberries cologne I love so much
My love and thoughts always with you , your John7
I like investigating hypothetical and unlikely future scenarios, so here it goes:
Let's say you are studying CS(BSc.) and you got an offer at google(or another FAANG company). Would you drop out to work for them? Why/why not?7
Here's a recent interview I had for an Android Developer job:
I: Interviewer, M: Me
I: hello, welcome
M: hi, thanks
I: do you know Kotlin?
M: yes, I've been working with it for 1.5 years and have written 3 projects in it
I: do you know RxJava, Dagger, Retrofit, and how to make Custom Views?
M: yes, I'm comfortable with them *explains*
I: do you know Room?
M: yes I do, I've done a lot of practices in it, but unfortunately have never needed to use it in production
I: what architecture do you use? Do you know MVP?
M: I'm currently using MVVM, but not MVP. I've debugged projects in it so I know what's going on in it
I: ok, do you have any questions for us?
M: how did I do?
I: I'm sorry sir, but you're not even a junior here
M: what? Why is that?
I: well you don't know Room and MVP?
M: I said I know them, just haven't used them in production.
I: well you have 3 years of experience but you dont even know Kotlin!
M: Kotlin was your first question and I said I have 3 projects in it. Did you even check the samples you asked for in the job posting?
I: SIR YOU'RE NOT A GOOD FIT FOR US, THANK YOU FOR COMING.
that time when you pass a cv of your friend who is as qualified as you were good 2 yrs ago to your boss and next thing you know he is being offered a much better position than you have3
Successfully upgraded my Arch Linux system without breaking any software.
It's a good start for today.5
I find that amusing that every spam comment on devrant have been posted only in that one rant. Also I cant downvote anything... and my reports dont work. So if you can please help me downvote those fuckers.3
I'm honestly happy that my toxic "senior" colleague is gone.
- Didnt learn a single thing in the last 10 years. Used godamn serverside rendering with Jquery / plain JS for a highly interactive business Web Application. Yeah boii, save that UI state in the relational database, good job.
- Every error in his shit was the error of someone else.
- Manipulative as hell. Type of guy that is your best buddy to gather information.
- Blocked entire technical progress in the Web department by manipulating people. Understandable. I mean if your legacy shit is gone...
- Kept backend developers from doing their job with unjustified complaints about structures... etc to justify that he needed an insane amount of time to implement simple things.
- Cried for every shit to be documented to the last bits. Did never do any documentation himself.
Fuck these people, honestly.1
Root has a deadline
I've been working on this CCPA ticket for awhile. Admittedly too long, but I'm new to the codebase and it's fucking sprawling. There has also been a lot of back-and-forth on the ticket.
Anyway, I've had a few blockers, such as how mailers work, the legal copy, where to put a admin-facing link to the dashboard, how to build the jira integration (and its creds), etc.
Quite awhile ago I asked Mr. Product, "Where should I put the ccpa dashboard link?" To which he responds: "I'll get you the answer today!" Awesome. Except he didn't. That day came and went without a peep. So, the next day I ask again: "Where should I put the ccpa dashboard link?" To which he responds: "I'll get you the answer today!" And that day comes and goes, too. I ask again, and you guessed it: "I'll get you the answer today." Repeat ad nauseam.
I also asked about the Jira integration and credentials. I got about the same treatment as above, but with a tiwst: they tell me to talk to / continue to bug Mr. H instead. Except Mr. H had been on PTO for weeks. Every time I ask, they keep referring me to him. A little over two weeks later (yesterday), I finally got a response from him. Yay! I was preoccupied with finishing the dashboard (which wasn't in the original ticket for some reason) so I didn't get a chance to look into it yet. After asking his boss three times, Mr. Product also finally (!!!) gave me a response on the link placement today, too! Though not directly: he discussed it with said boss in a group chat that I'm a part of, but never tagged me or told me directly. So, now I know where to put it (I think), but I have no idea how that area of the site is built (it's dynamic based on domain, login, and roles), so adding it will still be difficult.
The best part:
Today during standup, some lady I've only rarely seen before attends the meeting, doesn't say anything until the very end, and then announces that everything must be code-complete by tomorrow for release, and then promptly signs off.
For fuck's sake. I've had blockers on this for weeks, and now I need to finish it by fucking tonight?
I still don't know how to build the mailers (because translations and formats), nor how to actually send emails using them. I don't know how to modify the footer (dynamic, complex), how to add the admin-facing link (dynamic, complex), nor how build a Jira integration (haven't even looked yet). I just got unblocked on two of these fucking today. and it needs to be done and code reviewed by tomorrow?
No bloody way.
Maybe I should go back to my previous job. 😡19
I find it really annoying when someone insists that the develop branch is for production and not... development...5
Nothing better than your boss trusting you to work on mission critical stuff when you're a junior :) Feels good!7
We all know you can't "learn x programming language in a day" without travelling to the Arctic and catching a day that last half a year.
But what's the worst language to try and learn in a day?
I vote c++. Manual memory management, multiple inheritance, static compilation, operator overloading, and generally non-human syntax ( Like std::cout << "This is how you print!" << std::endl; ) make it a difficult one to attempt in a day.27
Toilets and race conditions!
A co-worker asked me what issues multi-threading and shared memory can have. So I explained him that stuff with the lock. He wasn't quite sure whether he got it.
Me: imagine you go to the toilet. You check whether there's enough toilet paper in the stall, and it is. BUT now someone else comes in, does business and uses up all paper. CPUs can do shit very fast, can't they? Yeah and now you're sitting on the bowl, and BAMM out of paper. This wouldn't have happened if you had locked the stall, right?
Him: yeah. And with a single thread?
Me: well if you're alone at home in your appartment, there's no reason to lock the door because there's nobody to interfere.
Him: ah, I see. And if I have two threads, but no shared memory, then it is as if my wife and me are at home with each a toilet of our own, then we don't need to lock either.
Recruiter: Hi practiseSafeHex, how are things? 😎
Bitch we aren’t friends. Where’s the job spec?9
So a few days ago I felt pretty h*ckin professional.
I'm an intern and my job was to get the last 2003 server off the racks (It's a government job, so it's a wonder we only have one 2003 server left). The problem being that the service running on that server cannot just be placed on a new OS. It's some custom engineering document server that was built in 2003 on a 1995 tech stack and it had been abandoned for so long that it was apparently lost to time with no hope of recovery.
"Please redesign the system. Use a modern tech stack. Have at it, she's your project, do as you wish."
Music to my ears.
First challenge is getting the data off the old server. It's a 1995 .mdb file, so the most recent version of Access that would be able to open it is 2010.
Option two: There's an "export" button that literally just vomits all 16,644 records into a tab-delimited text file. Since this option didn't require scavenging up an old version of Access, I wrote a Python script to just read the export file.
And something like 30% of the records were invalid. Why? Well, one of the fields allowed for newline characters. This was an issue because records were separated by newline. So any record with a field containing newline became invalid.
Although, this did not stop me. Not even close. I figured it out and fixed it in about 10 minutes. All records read into the program without issue.
Next for designing the database. My stack is MySQL and NodeJS, which my supervisors approved of. There was a lot of data that looked like it would fit into an integer, but one or two odd records would have something like "1050b" which mean that just a few items prevented me from having as slick of a database design as I wanted. I designed the tables, about 18 columns per record, mostly varchar(64).
Next challenge was putting the exported data into the database. At first I thought of doing it record by record from my python script. Connect to the MySQL server and just iterate over all the data I had. But what I ended up actually doing was generating a .sql file and running that on the server. This took a few tries thanks to a lot of inconsistencies in the data, but eventually, I got all 16k records in the new database and I had never been so happy.
The next two hours were very productive, designing a front end which was very clean. I had just enough time to design a rough prototype that works totally off ajax requests. I want to keep it that way so that other services can contact this data, as it may be useful to have an engineering data API.
Anyways, that was my win story of the week. I was handed a challenge; an old, decaying server full of important data, and despite the hitches one might expect from archaic data, I was able to rescue every byte. I will probably be presenting my prototype to the higher ups in Engineering sometime this week.
Client: I know other developers who would do the same and much more for much less.
Me: I am glad you chose to work with me instead.
Client: I mean I like the site but I still feel that the development process has taken longer than it should have.
Me: Well, it is within the time frame I had said I would be able to have the first version of the site running. I have also implemented quite a number of new features that we had not earlier agreed on.
Client: I think I'll pay (quotes less than 20% of the total cost ).
Me: That is less than the amount that you were to pay as the first instalment ages ago!!
Client: I mean I like the site, but I think it still lacks the X factor. I want ...*goes on to mention other features*
Me: While I take pride in making my clients happy, I believe this process should be mutually beneficial. You are constantly making requests for new features but are making no attempts to meet your end of the agreement.
Client: FYI, there are people begging me for this job.
Me: *Takes down the site.* I wish you all the best, I hope the other developers are up to your standards.
Client: *Literally ignoring the fact that I just quit*. I want (makes more requests).
I am simply going to ignore this one!!!!13
First I helped her with coding the Newton-Raphson method in Python (she has background in Mechanical Engineering).
Later I introduced her to the Linux world and she was amazed with the system responsiveness.
Now I am helping her with learning C (she is programming to Arduino but some concepts are hard for her because Python was her first language).
We are together for 4 years and going on.1
Sales employee Bob wants a clickable blue button.
Bob tells product owner Karen about his unstoppable desire for clickable blue buttons.
Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons)
Karen asks the button team how hard it is to build a button. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points).
These three scores are combined to give a priority score. The global buttonbacklog is sorted by priority.
Once every two weeks (a "sprint") the button team convenes, uses the ease scores to assign scrum points. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. They use the average of the last 5 sprints to calculate each developer's "velocity".
The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. Approximate due dates are assigned, Bob is a happy Bob.
What if boss Peter runs into the office screaming "OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR"?
Devs tell boss to shut the fuck up and talk to Karen. Karen has a carefully curated list of button building tasks sorted by priority, can sedate boss with valium so he calms the fuck down until he can make a case for the impact and potential of his pink button.
Karen might agree that Peter's pink button gets a higher priority than Bob's blue button.
But devs are nocturnal creatures, easily disturbed when approached by humans, their natural rhythms thrown out of balance.
So the sprint is "locked", and Peter's pink button appears at the top of the global backlog, from where it flows into the next sprint.
On rare occasions a sprint is broken open, for example when Karen realizes that all of the end users will commit suicide if they don't have a pink heart-spawning button.
In such an event, Peter must make Bob happy (because Bob is crying that his blue button is delayed). And Peter must make the button team of devs happy.
This usually leads to a ritual involving chocolate or even hardware gift certificates to restore balance to the dev ecosystem.23
Me: *sends email 45 minutes before a meeting*.
Boss: *20 mins into meeting*, any updates about the issues found yesterday?
Me: Yep I sent an email with an update on everything.
Boss: ok great, *shares screen*, *opens email*.
Ok want to walk us through it?
Me: ...... walk through my email?
Boss: Yeah we have everyone here in the meeting.
Me: ...... yeah I included all of them on the email.
Boss: Right, but it would be good to go through it for everyone’s benefit.
Me: *Reads email word for word, from the screen share*
I will now refer to him from this day forth as “The Time Vampire”.22
A guide to estimations.
1) don’t give an immediate answer. The first “timeframe” you give will be held against you and will result in overtime and working weekends.
2) think of a relevant piece of work and the time that took.
2.1) if it’s something you haven’t done before, add some adequate research time.
3) allow half a day of testing for every day of development.
4) add a day as buffer - this is good for on the fly bug fixes
5) calculate time
6) now give an educated estimate.
7) this should take you 5 seconds to get through mentally.
8) if scope creep occurs: goto:16
Goddamn I'm retarded to the next level.
Rebooted my phone a few days ago, some stuff didn't work well anymore and I'm looking for a new one which supports custom roms but I shouldn't spend too much right now so I thought I'd let it go for now.
Rebooted again last night and the network time wouldn't set properly so set it manually. Today I suddenly noticed that any app/page loading through a secure connection wasn't loading at all.
This to the goddamn point that my phone was becoming useless.
Started to search for a quick, cheap replacement supporting custom roms while debugging on and on.
I just (now) looked at the date and BAM, it hit me: I set it to one month earlier.
Mother of god I'm stupid. Brain fart to the max.14