Me : it's my new android app, this app lets you store daily routines and is very fast.
Dad : where's the money?
Friends : so now you will get a job at Google 😱
Girlfriend : install this on my iPhone
Mom : You are genius. Now get the groceries I asked you for.

I’ve battled depressed I failed to realized I had for many years. I didn’t love myself, I forgot what it felt like to love myself, and then one day my life turned around out of the blue. I believe my turning point was when I realized that I wasn’t alone and that people did care about me. I just wasn’t motivated especially after almost losing my cousin to suicide 3-4 months back. It changed my DNA, my personality, everything about me changed until I told myself that I had enough.

Today marks the 4th month where I last had a cup of coffee, soda, or junk food in general because in all honesty it was just making my depression worse. Today also marks the 4th month I’ve been going to the gym without fail and I’ve now noticed how far I’ve come. I love myself more than ever now and I am VERY goal oriented as well. I have one more year left until I get my bachelors degree in Software Development and soon after I’ll go in for my Masters and who knows what I’ll do after that.

It’s all uphill from here and by sticking to my new routines I am feeling a lot better as the days and months pass.

Attached is my progress thus far, left is from when I felt at my lowest and right is the progress I’ve made so far with improving myself and where I am at now.

I love myself, I love those that love me, and I LOVE feeing AMAZING like I do now when I wake up every morning waiting to see what the day has in store for me 😄❤️

When you realize the only way to optimize your C++ code is to start writing asm routines...

I'm working on the project with the weirdest combination of technologies ever:
Vue.js on the frontend, FORTRAN 77 on the backend. :D
(Plus a thin Spring MVC layer that converts the f77 routines into REST API)

Is that a message describing windows altogether, or just the copying routines... Can't figure that one out.

I hate when someone throws at me some task all of sudden with a tight deadline.

Wednesday was one of those days.

manager: we want to remove all the offices because of our tight budget this year (multimillionaire company, lol), everyone will use office 365;

me: ahn... ok, but everything was already tested? Some macros, routines, old documents can be a big problem, as far I know (I don't use M$ at home, servers are Linux, so I really don't know about that). I can do some tests, only will need some real documents to make sure everything will do fine;

manager: yeah, yeah, everything will be fine, the high management already decided, don't worry, just remove the offices in the company, ok?;

me: alright...

*me deploys the remotion script in every f*cking machine*

48 hours later...

manager: well... everyone is complaining about the office 365, random complains, can you attend all the calls and reinstall if you can't solve the problem?

WTFFFFFFFFFFFFFFFFFFFFFFFF!!!!!

[RAGES INTERNALLY]

"please copy these 32767 bytes to VRAM" → infinite bytes copied, entire address space destroyed.
"please copy these 32768 bytes to VRAM" → 4 bytes copied

thank you, TI, for making the shittiest possible routines that are infinitely picky.

Welp, its official, with Debian Buster adoption into our mainline, we are officially switching from Sys-V-Init to SystemD.

I still do not know how I feel about it.

From the professional point of view - Its a relief. SystemD has so many more neat features that make the life of a sysadmin easier. If any, I love that it tracks the uptime of a service, making it incredibly easy the last time it crashed / restarted...

On the other... I just... Am kind of afraid where the whole systemd environment will go with time... And... I guess... I am also worried about how much systemd is taking over in the system itself... It will mean learning quite a few new services, debugging routines and such...

A new era of GNU/SystemD/Linux is upon us.

Started reading this book completed 15 chapter in 21 chapter. Now reading co-routines. Wonderful book, lot of internal stuffs
PS: skipped chapter 4 text vs bytes.
Which book to read next ?

A primary investor in the company I work for drops by every few days and always smokes cigars in the coffee room and shuts the door..

My coffee and his cigar routines have never collided before today, I'm now trying to figure out the lowest impact server or utility I can shutdown that will cause enough panic to get him out.

I did a project once and it came back to haunt me - this is how I got the job I have now:

I was already working for the company, in the second year of my vocational training as an electronics technician when I got a assigned The Project.
In brief, The Project was a kind of measurement automation implemented with some arduinos. I was tinkering with them at the time in my free time so they must've thought 'Hey, great, she can do that, so she can also do The Project!'

Just that I couldn't - after investing nearly a year, getting frustrated because of the lack of time, support, knowledge etc. The Project died quite unceremoniously and I resumed my training normally.

I just wish devRant already existed back then, it'd have made up for some spectacular rants - The Project was fucking nerve-wrecking due to incoherent behaviour by some hardware and I had to battle the whole big, ugly thing more or less alone as an apprentice.
If it hadn't died at the time it did I feel like I would've brutally murdered it with a shovel - that is, if someone actually would've cared enough to buy me a shovel.

But it ended and I let it go.

In the last year of completing this vocational training, my feeling of "This is not enough" and growing boredom with the routines of my future job had manifested. I wanted to go back to university but also continue working at the same time.

I wasn't ready to do freelancing nor did I want to quit at that time - most people there are amazing and I'm still learning much from them - so I asked early for a student position and got one.

And to get some continuity in my work, it wasn't just any student project I was assigned to but The Project. It came back alive, laughing at me, leaving bodies of dead electronics in its wake, after all these years.*

And that's how I got my current job.

*(They asked me if I was OK with it and they dropped the Arduinos and other hardware in exchange for a bit more software. Also I have a team of great engineers which I can ask for help anytime should I get stuck, so I got that going for me which is nice.)

I've spent a lot of time messing around with C, having struggled with object-oriented programming (due to not really knowing how best to structure things, not knowing when to apply certain design patterns).

When writing C code, I'd write OOP-esque code (pass around a struct to routines to do things with it) and enjoyed just making things happen without having to think too much about the overall design. But then I'd crave being able to use namespaces, and think about how the code would be tidier if I used exceptions instead of having every routine return an error code...

Working with Python and Node over the past couple of years has allowed me to easily get into OOP (no separate declaration/definition, loose typing etc.) and from that I've made some fairly good design decisions. I'd implemented a few design patterns without even realising which patterns they were - later reading up on them and thinking "hey, that's what I used earlier!"

I've also had a bit of an obsession with small executable files - using templates and other features of C++ add some bloat (on Windows at least) compared to C. There were other gripes I had with C++, mostly to do with making things modular (dynamic linking etc.) but really it's irrelevant/unreasonable.

And yes, for someone who doesn't like code bloat, working with Node is somewhat ironic... (hello, node_modules...)

So today I decided to revisit C++ and dust off my old copy of C++ in a Nutshell, and try to see if I could write some code to do things that I struggled with before. One nice thing is that this book was printed in 2003, yet all of its content is still relevant. Of course, there are newer C++ standards, but I can happily just hack away and avoid using anything that has been deprecated.

One thing I've always avoided is dynamic_cast because every time I read about it, I read that "it's slow". So I just tried to work around it when really if it's the right tool for the job, I might as well use it... It's really useful!

Anyway, now I've typed all this positivity about C++ I will probably find a little later on that I hit a wall with what I'm doing and give up again... :p

The "click" moment always feels fucking amazing. TI made some retarded ASM routines (as usual) for drawing various things to the screen, most of the time whatever you try to draw takes upwards of 3 frames at 15MHz to draw. A LINE KNOWN TO BE 100% STRAIGHT SHOULD NOT TAKE 1/3 OF A FRAME TO PLOT EACH PIXEL OF. I managed to get it down to 300-some cycles per pixel on the 2 i've messed with, which still isn't great, but it's a massive increase in efficiency, so fuck it, i'm happy. The "click" was when I managed to get a serious optimization working that took over 3 hours to debug.

Go, because go routines and channels.

For a long time I was of the opinion that pointer variables in C/C++ should have the asterisk immediately after the type name (e.g. int* foo).

Eventually I became convinced that it makes more sense to have it before the variable (e.g. int *foo).

Now I find routines that return pointers look weird, e.g.: void *allocate_something() so I am considering adopting the original style I used.

The only advantage of having the asterisk before the variable name I am aware of is that it is easier to remember to add an asterisk if you define more than one pointer on that line.

Anyone else find it hard to settle on code style guidelines for their own personal projects?

uh-oh, I've made the amazonian gods mad by activating my vpn on my phone at the wrong time at the wrong place. (please don't send delivery drones nuking me)

I thought my alexa routines and other things vanished because of an update of sorts, but it was because it switched to another vpn region, so I've setup the same stuff again only to get like two reminders at the same time they used to be, guess I now have to either stick to the region or deactivate vpn, remove the old reminders and go back lol

It is funny that every non-programmer person refers any code computer executes to as "app".

Just wrote a script which does some routines during startup of PC for a friend of mine. Cringed when he said "Thank you for the app."

So I'm on orders for the Marine Corps, and this one guy thinks he's a programmer because he made a "program" in excel for dispatching our equipment. He's complaining that he's just fixing bugs. I take a look at his VBA code and see literally 1000 lines of if statements bundled into one function. (Or I think they're referred to as sub routines in VBA - it's been a while since I worked with it).

I try to give him some tips and pointers since he's literally just manually checking. Each. F'ing. Cell and a million nested if statements. Tried giving tips on making reusable code, and he has the cojones to tell me he knows what he's doing and doesn't need my "help". Granted I'm higher ranking than him and he also answers in a disrespectful manner.

End rant.

ECMAScript is everywhere, so I thought: Let's do even more inappropriate and insane things with it ;)

...Like using Duktape (small ECMAScript engine) and exposing LoadLibrary/GetProcAddress along with some helper routines to describe the routine's argument types and return type, and finally providing a routine to invoke those routines.

It's a very rough prototype that can handle up to 4 arguments in a 64-bit Windows environment.

Next "todo" is structure handling which will initially be a case of stuffing data into a Buffer() object.

I'm not sure what exactly I'm trying to do with it or why...

i had an epiphany today, in a discussion with the software architect of our new project.

i'm having the epic job to design & implement a prototype for a C++ library in a new software project and collected some inspiration in our "old" software, where i'm maintaining the module that fulfills the same functionality (i thought). i've been maintaining this module for around a year now. i analyzed the different features and stuff to consider and created a partial model of the new library.

when i showed it to the architect today, he was like "oh my god, no no no, you don't need all this functionality, this shall not be part of the new library!"

this was the moment when i realized how deeply fucked up the code base of the old module is.

imagine it like this:
you want to automate the process of making yourself a good ol' cup of coffee.
the reasonable thing would be to have

- a smart water boiler where you set parameters water temperature and amount of water to be fetched from the water supply
- a smart coffee bean grinder where you can set type of beans, amount of beans and grinding fineness
- a component where water and ground coffee are joined to brew the coffee, where parameters like duration, pressure etc. are set
- a milk tank where amount of milk, desired temperature and duration / speed of foaming can be set
- a sugar dispenser where amount of applied sugar can be set
- optionally, additional modules with spices, syrup, ice cubes, whatever for your very personal coffee experience

on requesting a coffee, you would then configure and orchestrate all components to your wishes to make you a fine cup of coffee. you can also add routines like "makeCappucchino()", "makeEspresso()", or whatever.

our software is not like this.
it is like this:
- a smart water boiler consisting of submodules that know how to cook water for e.g. "cappucchino with sugar" or for "espresso without sugar, but with milk and ice cubes"
- 5 smart bean grinders that know how to grind beans for e.g. cappucchino, espresso, latte macchiato and for 73ml of water preheated to 82°C
- a very smart sugar dispenser that knows how to add sugar to 95, 98 and 100°C coffee and to coffee made of BOTH coffee arabica AND coffee robusta beans.

etc. etc., i think you're getting the gist.

when i realized this, it was like, right in front of my eyes, this terrible pattern emerged like a foul, corrupted caleidoscope of chaos, through the whole code base of this module.
i've already known how rotten from the core this code base is, but today i've actually identified a really bad pattern that i hadn't realized before. the whole architecture is so bloated that it is hard to have an overview of the whole thing. and it would require a LOT of refactoring to repair this pattern.
but i guess it would also be infinitely satisfying because i could probably reduce the code base for 30% or something...

but unfortunately, this is never going to happen, because screw refactoring.

it's a great feeling to start this new library from scratch, tho...

I struggle with naming things. Projects especially and particularly if I intend to make a library in C and want to prefix the routines with something.

How do you decide on a name for your software projects?

Does any of you know, what happens to Go-routines, when they are deadlocked by waiting on a channel and the channel isn't reachable anymore?
I'd assume they get garbage-collected since they'd just a few KB of memory when not in use but I can't find anything on it online.

People who don't smoke/drink often underestimate the power of smoke breaks that people take in the office.

To others it might seem like something colleagues do outside for 5-10 mins but it literally is not the case.

In 2018 at an office job I worked at, the HR, marketing head and a dev colleague all separately used to drag me out in the balcony at different times. They didn't wanna smoke with each other, just alone with me.

I knew everything about them starting from where they studied, their work history, their salaries, routines, their married lives, how they feel in and out of the office, what they are depressed about. More than anything I needed to know about them..

It didn't result in personal gains or anything but it wouldn't have happened if I was then a non smoker.

Remember that episode in Friends where Rachel had to forcefully take up smoking to socialize with her colleagues? It's completely true

I really shouldn't use devRant before going to sleep, but that's at least currently the only own and peaceful time I have during week days because of really busy school and work schedule. (Yey, it's weekend!)

If I don't realize that I should stop using devRant at night it moves my sleeping time so that I don't get enough sleep or I won't be able to wake up in a timely manner.

I just immerse in the reading, commenting or even ranting so that I forget the passing of time. Making thing worse is that when I'm writing something my inner perfectionism wakes up and I try to make the text as good as possible and so I get more and more active when I should be relaxing and getting ready to sleep.

Do not worry about my sleep. I'll probably just start to read a book instead. But when it's a good time to use devRant then... 🤔

When or how do you use devRant?
What kind of sleep routines do you have?

Aaaaarggghhh

Having to think about what and when to eat is such a fucking pain in the ass. I don't want to search for recipes. I don't want to think about nutrition. I don't want to count calories. I just want something to tell me exactly what to eat, when I should eat and what to buy. Same goes for workout routines. Just tell me what to do I'll do it. I want an autopilot for that sort of stuff so I don't have to ducking think about it anymore. It's such a giant waste of time to have to manually plan this shit through, I want to use my brain for other things like math or chemistry or Programming. In fact I don't even want to cook because I am alone and cooking for one person is so ducking pointless. I lost over 40kg in the last years. I learned my lesson, most things taste like shit now because I associate food with all the pain and depression that I had to overcome to achieve a normal weight and fit body. Food went from being a joy to being an annoying necessity. I got fit and I want to work out even more but I really don't want to think about this shit. The exercises and pain and hunger are all nothing but planning is my true enemy. It bores me to death, it's more painful than running until I break down I absolutely fucking hate it.

I am really close to start some kind of open source food planner where you can type in your goals ( weight loss, muscle gain etc.) In great detail with all kind of options ( vegetarian, vegan, allergies, budget, country where you live in for local recipes etc.) And it generates a food plan for you with exact details of where exactly to buy the ingredients how to cook them etc. No fancy Ui No bullshit ads for some kind of wonder drug nothing annoying. Something so easy that it can be used as an autopilot for ones fitness and life. Do what it says and you'll look decent, don't think about the rest. Having that would be so great and I could finally think about more important shit than this. Less overhead more time for things that can't be automated.

And Yes I know that this is exactly what a personal trainer would do, but I am not going to spend 600€ a month for someone to tell me exactly what to buy, what to eat and how to work out.

How are your exercise routines like?

So I was instructed today, after lunch, to spend an hour teaching a member of my team how to SSH, store keys, basic io routines, and create CRON jobs to auth our ECR registry by my team lead.. Why am I wasting dev time teaching someone how to use an operating system? Need I add, our primary Dev workspace is a spun up using vagrant using xubuntu. I just can't comprehend how this person has been using xubuntu as their primary OS for two months and doesn't know the SSH protocol. Much less how they landed a dev job without any prior experience with a *NIX based OS.

So, what are your most favorite methods of saving interesting articles about algorithms, functions or simply news so you can read them later when you have time? I find myself storing links to interesting web pages without really going back to them or remembering which link was what. I shifted to storing the links in evernote but it's still not what I'd ideally like to have...

If there are any recommended routines, apps or tools that make stored links insightful (like allowing me to add a quick description or automatically adding a sort of preview of the link), I would appreciate it!

Please note that this is primarily about saving a resource while I'm on the go or simply can't/don't want to spend too much time on the actions.

Wow Go is awesome, throwing some of its magic and making data ingestion that took one minute plus and make it run under 3 seconds.
Feels good

Fuck JavaScript!!!!!

I'm building an application using Vue with MaterializeCSS and i'm using moment to handle dates. i have to initialize datepickers with values at mount of the vue. i use variables to store the states. there are proper routines for intialization and setting of the pickers. the routines run. there are no errors. the pickers show values. no errors. but the fucking variables ar empty!!!! the pickers are not being set. holy mother of fcuking shitty js milk!

I write code as part of my job but also tend to have a lot of pet projects I think about in my spare time. A lot of those projects are not specifically targeted at solving an actual real problem but are just a curiosity (like my Duktape/ECMAScript thing that could import and call DLL routines.) I often find it difficult to choose which one to continue working on and end up not working on any of them because I can't decide which one is more interesting at the time! Or I get stuck and struggle to find a way around whatever roadblock I've hit.

My first computer exposure was on a mainframe (CDC Cyber 180). My university in Kerala, India had a collaboration with the Indian defence organisation DRDO. The operating system was something called NOS/VE, though as I remember it could run some Unix version virtually. I had Fortran 77 programs to be developed as part of the course. (finite element methods). As I remember, the machine had built in routines for the same. Screen was a green on dark terminal conected to the thing. No windowing or graphics.
Today kids have more powerful machines at home (or in their pockets). The famous computing power law be praised.

so I found out that i'm too stupid to understand floats... I look at the structure and my brain immediately smooths over. I just can't understand it for some reason. Even better: this shitbox calculator requires them for LITERALLY EVERYTHING. I can't even have it take a register and turn it into a float or anything, so I can't even operate on anything without massive assembly routines, and I just don't understand what the fuck any of it does or means.

i'm really not cut out for a programming job am i

This moment when you pressed your "Auto-Indent" Hotkey and the whole software doesn't run anymore. Later you realize that it's because of your Auto-Indent and even worse - you realize you have to code on top of the spaghetti code...

How do you manage your projects as solo developers, I find myself most of the time procrastinating. If you could share with me some insights about your routines I would be grateful and how you manage time in general?