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
-
We had a Commodore64. My dad used to be an electrical engineer and had programs on it for calculations, but sometimes I was allowed to play games on it.
When my mother passed away (late 80s, I was 7), I closed up completely. I didn't speak, locked myself into my room, skipped school to read in the library. My dad was a lovely caring man, but he was suffering from a mental disease, so he couldn't really handle the situation either.
A few weeks after the funeral, on my birthday, the C64 was set up in my bedroom, with the "programmers reference guide" on my desk. I stayed up late every night to read it and try the examples, thought about those programs while in school. I memorized the addresses of the sound and sprite buffers, learnt how programs were managed in memory and stored on the casette.
I worked on my own games, got lost in the stories I was writing, mostly scifi/fantasy RPGs. I bought 2764 eproms and soldered custom cartridges so I could store my finished work safely.
When I was 12 my dad disappeared, was found, and hospitalized with lost memory. I slipped through the cracks of child protection, felt responsible to take care of the house and pay the bills. After a year I got picked up and placed in foster care in a strict Christian family who disallowed the use of computers.
I ran away when I was 13, rented a student apartment using my orphanage checks (about €800/m), got a bunch of new and recycled computers on which I installed Debian, and learnt many new programming languages (C/C++, Haskell, JS, PHP, etc). My apartment mates joked about the 12 CRT monitors in my room, but I loved playing around with experimental networking setups. I tried to keep a low profile and attended high school, often faking my dad's signatures.
After a little over a year I was picked up by child protection again. My dad was living on his own again, partly recovered, and in front of a judge he agreed to be provisory legal guardian, despite his condition. I was ruled to be legally an adult at the age of 15, and got to keep living in the student flat (nation-wide foster parent shortage played a role).
OK, so this sounds like a sobstory. It isn't. I fondly remember my mom, my dad is doing pretty well, enjoying his old age together with an nice woman in some communal landhouse place.
I had a bit of a downturn from age 18-22 or so, lots of drugs and partying. Maybe I just needed to do that. I never finished any school (not even high school), but managed to build a relatively good career. My mom was a biochemist and left me a lot of books, and I started out as lab analyst for a pharma company, later went into phytogenetics, then aerospace (QA/NDT), and later back to pure programming again.
Computers helped me through a tough childhood.
They awakened a passion for creative writing, for math, for science as a whole. I'm a bit messed up, a bit of a survivalist, but currently quite happy and content with my life.
I try to keep reminding people around me, especially those who have just become parents, that you might feel like your kids need a perfect childhood, worrying about social development, dragging them to soccer matches and expensive schools...
But the most important part is to just love them, even if (or especially when) life is harsh and imperfect. Show them you love them with small gestures, and give their dreams the chance to flourish using any of the little resources you have available.22 -
"So what are your hobbies?"
Me: "programming"
"No i mean your real hobbies, besides the work you do"
Me: *awkward silence*7 -
29-year veteran here. Began programming professionally in 1990, writing BASIC applications for an 8-bit Apple II+ computer. Learned Pascal, C, Clipper, COBOL. Ironic side-story: back then, my university colleagues and I used to make fun of old COBOL programmers. Fortunately, I never had to actually work with the language, but the knowledge allowed me to qualify for a decent job position, back in '92.
For a while, I worked with an IBM mainframe, using REXX and EXEC2 scripting languages for the VM/SP operating system. Then I began programming for the web, wrote my first dynamic web applications with cgi-bin shell and Perl scripts. Used the little-known IBM Net.Data scripting language. I finally learned PHP and settled with it for many, many years.
I always wanted to be a programmer. As a kid I dreamed of being like Kevin Flynn, of TRON - create world famous videogames and live upstairs my own arcade place! Later on, at some point, I was disappointed, I questioned my skills, I thought I should do more, I let other people's expectations make feel bad. Then I finally realized I actually enjoy a quieter, simpler life. And I made peace with it.
I'm now like the old programmers I used to mock 30 years ago. There's so much shit inside my brain. And everything seems so damn complex these days. Frameworks, package managers, transpilers, layers and more layers of code. I try to keep up. And the more I learn, the more it seems I don't know.
Sometimes I feel tired. Yet, I still enjoy creating things and solving problems with programming. I still have fun learning. And after all these years, I learned to be proud of my work, even if it didn't turn out to be as glamorous as in the movies.30 -
It finally hit me the other day.
I'm working on an IoT project for a late-stage ALS patient. The setup is that he has a tablet he controls with his eye movements, and he wants to be able to control furnishings in his room without relying on anyone else.
I set up a socket connection between his tablet and the Raspberry Pi. From there it was a simple matter of using GPIO to turn a lamp or fan on or off. I did the whole thing in C, even the socket programming on the Pi.
As I was finishing up the main control of the program on the Pi I realized that I need to be more certain of this than anything I've ever done before.
If something breaks, the client may be forced to go days without being able to turn his room light on, or his fan off.
Understand he is totally trapped in his own body so it's not like he can simply turn the fan off. The nursing staff are not particularly helpful and his wife is tied up a lot with work and their two small children so she can't spend all day every day doting on him.
Think of how annoying it is when you're trying to sleep and someone turns the light on in your room; now imagine you can't turn it off yourself, and it would take you about twenty minutes to tell someone to turn it off -- that is once you get their attention, again without being able to move any part of your body except your eyes.
As programmers and devs, it's a skill to do thorough testing and iron-out all the bugs. It is an entirely different experience when your client will be depending on what you're doing to drastically improve his quality of life, by being able to control his comfort level directly without relying on others -- that is, to do the simplest of tasks that we all take for granted.
Giving this man some independence back to his life is a huge honor; however, it carries the burden of knowing that I need to be damned confident in what I am doing, and that I have designed the system to recover from any catastrophe as quickly as possible.
In case you were wondering how I did it all: The Pi launches a wrapper for the socket connection on boot.
The wrapper launches the actual socket connection in a child process, then waits for it to exit. When the socket connection exits, the wrapper analyzes the cause for the exit.
If the socket connection exited safely -- by passing a special command from the tablet to the Pi -- then the wrapper exits the main function, which allows updating the Pi. If the socket connection exited unexpectedly, then the Pi reboots automatically -- which is the fastest way to return functionality and to safeguard against any resource leaks.
The socket program itself launches its own child process, which is an executable on the Pi. The data sent by the tablet is the name of the executable on the Pi. This allows a dynamic number of programs that can be controlled from the tablet, without having to reprogram the Pi, except for loding the executable onto it. If this child of the socket program fails, it will not disrupt its parent process, which is the socket program itself.13 -
Me : You should try this app, its great!
Friend: What is about?
Me : A place where programmers and developers tell jokes and complain to each other
Friend : But you can do that i real life too
Me : But now you don't have to leave your computer to do that1 -
So my friend started a YouTube channel, being the motivational man I am I encouraged him and made him a logo for his channel.
It started here, he called me a bazillion times every single day asking me to make stuff like Channel banners, intros.
He even went so far to call my design bad and that I could do better.
I'm definitely losing my hold on my generosity, it's like this with every single fucktard I help. It's like programmers don't get to have a life, people pitch me stupid ideas at every party.. Having a casual conversation a guy starts talking about an idea.
Oooh... And the worst part they say you can have 60% and just give them 40% 'MINORITY' share for coming up with an idea I could pull up from my arse instantaneously
Next time he asks me something I'm gonna fuck him up or just charge him a bazillion dollars... FUCK FUCK FUCK... REALLY GOT TO BUY THAT STUPID STRESS CUBE15 -
When i was studying Engineering, I used to wonder how programmers works straight 3,4 days without sleep and all.
With today, I completed my 3rd day, with just 2 hours sleep in the last 70 hours.
Now I get it,
This is.. passion,
This is.. love,
This is Life.16 -
As most of you already know, I'm a writer. I've noticed the similarities between writing and programming:
1. Tabs vs spaces.
2. Both typically spend all their time with a single project.
3. Coffee... (Unless you're a tea lover like me.)
4. Both typically have no life.
5. Debugging is hell for programmers and editing/revising is hell for writers.
6. Strict clients for programming and strict editors for writing.
7. Semicolons... They're useful but everyone despises them.
8: Emotions. Programmers are angry at their code. (Why won't you work?) and writers feel depressed about their writing. (Why did you die?)
9. War of the programs. For programmers: Vim vs VScode vs Atom vs Sublime and etc. For writers: MS word vs Google docs vs Libre office and etc.
10. Online forums. Stack overflow and Writer's digest.
11. Typing... Typing... All day long.
These are only a few similarities. I've noticed a lot more than this.16 -
The Absolutely True Story of a Real Programmer Who Never Learned C.
I have a young friend named Sam who is quite a programming prodigy. Sam does know C! I need to make this clear: he’s not the titular programmer.
But a couple years ago Sam told me a story about a different programmer who never learned C, and I liked it so much that right on the spot I asked his permission to repeat it. (I could never just steal such a tale.)
Sam wasn’t always a programmer—actually he started in his later teens, in part because he was more of a jock, and in part because he was related to programmers and wanted to do his own thing. But, like all great programmers, once he was bitten by the bug he immersed himself completely in it.
One day Sam happened to be talking programming with his uncle, who was also a programmer but from way, way back.
“Hey,” said Sam, “I’m learning this language called C. You must know a lot of languages, did you ever study C?”
“No,” said the uncle, to Sam’s surprise. “I am one of the very few programmers who never had to learn C.”
“Because I wrote it.”
Oh, Sam’s last name is Ritchie.
What I love about this story is the idea of Dennis waiting Sam’s entire life to deliver this zinger. Just imagine sitting on a line that good, watching your nephew grow up and waiting, waiting until the one day he finally starts learning to code. Did he work on the line in his head at night? Like, “Hmm, how should I word it so I can deliver the punch line perfectly? Should I say ‘I never took a class on C?’ Nah, too awkward…”
The great thing about geniuses is how much effort they put into everything.
Courtesy : Wil Shiply.5 -
!rant
I love the fact that some programmers will put there heart and soul into a project and spend there entire life working on it to only have no recognition or earn a single cent.
Yet the man who invented toilet paper literally wiped his ass and made millions...
I love how the world works! :-D5 -
What was the biggest lies you heard about programming or programmers life.
Mine was: “programming is easy and high paying job.”
No it is not.12 -
Hello everyone, this is my first time here so hi! I want to tell you all a story about my current situation.
At 18 while in the military I was able to get my first computer, it was a small hp pavilion laptop with windows 7. The system would crash constantly, even though I would only use it for googling stuff and using fb to talk to people. 5 months after I got it and continuously hated it decided to find out why and who could I blame (other than myself) for the system making me do the ctrl alt del dance all the time....
Found out that there are people called computer programmers that made software. Decided to give it a go since I had some free time most days. Started out with c++ because it was being recommended in some websites. Had many "oh deeeeer lord" moments. After not getting much traction I decided to move to Java which seemed like an easier step than C++. Had fun, but after some verbosity I decided to move into more dynamic lands. Tried JS and since at the time there was no Node and I was not very into the idea of building websites I decided to move into Python, Ruby, PHP and Perl and had a really great time using and learning all of them. I decided to get good in theoretical aspects of computer programming and since I had a knack for math I decided to get started with basic computer science concepts.
I absolutely frigging loved it. And not only that, but learning new things became an obsession, the kind that would make me go to bed at 02:40 am just to wake up at 04:00 or 06:00 because the military is like that. I really wanted to absorb as much as I could since I wanted to go to college for it and wanted to be prepared since I did not wanted to be a complete newb. Took Harvard CS50, Standford Programming 101 with Java, Rice's Python course and MIT's Python programming class. I had so much fun I don't regret it one bit.
By the time I got to college I had already made the jump to Linux and was an adept Arch user, Its not that it was superior or anything, but it really forced me to learn about Linux and working around a terminal and the internals of the system to get what I want. Now a days I settle for Fedora or Debian based systems since they are easier and time is money.
Uni was a breeze, math was fun and the programming classes seemed like glorified "Hello World" courses. I had fun, but not that much fun, most of my time was spent getting better at actual coding. I am no genius, nor my grades were super amazing(I did graduate with honors though) but I had fun, which never really happened in school before that.
While in school I took my first programming gig! It was in ASP.NET MVC, we were using C#, I got the job through a customer that I met at work, I was working in retail during the time and absolutely hated it. I remember being so excited with the gig, I got to meet other developers! Where I am from there aren't that many and most of them are very specialized, so they only get concerned with certain aspects of coding (e.g VBA developers.....) and that is until I met the lead dev. He was by far one of the biggest assholes I had ever met in my life. Absolutely nothing that I would do or say made hem not be a dick. My code was steady, but I would find bugs of incomplete stuff that he would do, whenever I would fix it he would belittle me and constantly remind me of my position as a "junior dev" in the company saying things as "if you have an issue with my code or standards tell me, but do not touch the code" which was funny considering that I would not be able to advance without those fixes. I quit not even 3 months latter because I could not stand the dick, neither 2 of the other developers since the immediately resigned after they got their own courage.
A year latter I was able to find myself another gig. I was hesitant for a moment since it was another remote position in which I had already had a crappy experience. Boy this one was bad. To be fair, this was on me since I had to get good with Lumen after only having some exposure to Laravel. Which I did mentioned repeatedly even though he did offer to train me in order to help him. Same thing, after a couple of weeks of being told how much I did not know I decided to get out.
That is 2 strikes.
So I waited a little while and took a position inside another company that was using vanilla PHP to build their services. Their system was solid though, the lead engineer remains a friend and I did learn a lot from him. I got contracted because they were looking for a Java developer. The salary was good. But when I got there they mentioned that they wanted a developer in Java...to build Android. At the time I was using Java with Spring so I though "well how hard can this be! I already use Android so the love for the system is there, lets do this!" And it was an intense, fun and really amazing experience.
-- To be continued.10 -
6:30pm: "You programmers have no life at all. Spending the whole day infront of a computer! "
6:31pm: "Hey could you please loan me some money, I am so broke right now"
*Me singing in my head*: 🎵🎵Young, dumb and broke4 -
Real life job interview…
Manager: what about this problem? Could you solve it? (Showing me a problem about scanning a 2d array to find a value written on a piece of paper)
Me: sure! Just give me a piece of paper and I will write a solution.
Manager: no need for that. I don’t have the knowledge to check that anyway… if I wanted you to solve it I would have called one of my programmers.
…
Manager: do you have any question about the company?
Me: What do you exactly do in the company? I wonder what is the purpose of a person that makes questions about things he doesn’t know.3 -
I remember my first "Software Engineering 2" class at University. The teacher, a pompous son of a bitch that later on gave proof of his vast ignorance, greeted us with
"so ... You call yourselves programmers, right? What's the biggest program you have ever wrote? Something along the 100, maybe 200 lines of code? ..... If you've never written at least a MILLION lines of code software, you're not a software developer"
Even at that time, with my lack of experience in software development, I had that feeling in my guts telling me "writing myself a 1M lines of code software .... Brrrr that's something I hope I'll neve have to do in my life"
Turned of he was one of those dinosaurs stuck with the love for gargantuan monoliths of software like they used to do.
Just to dive you the whole picture, the course had ZERO software development and focused only on how to manage wonderful waterfall projects, how to write all types of software documentations and the final project was ... Writing a ton of documentation so boring and useless that even he didn't care to read through.
we still laugh at the episode when another group asked us to borrow one of our documents and after one day they asked "hemm ... Have you really sent this to the teacher?" "yes, why not?" ".... at page 23 someone left a comment saying 'what the fuck is this shit?'"5 -
Most of things I'm about to say are experienced by almost 99% of developers in Africa including my country so I'm going to make it a more general rant.
As an African developer, life is both exciting and frustrating at the same time. Some of the challenges that make life difficult for developers in Africa include:
1). Slow Internet Speed: The internet in Africa can be extremely slow and unreliable, making it frustrating to work on projects that require large file downloads. This is a serious challenge for freelance developers who work from home.
2). Unstable Electricity: Frequent power outages due to inadequate infrastructure, insufficient investment in energy production and distribution, and political instability makes it difficult for developers in Africa to work consistently. Most times I get frustrated because you can experience black out at anytime of the day which could last for hours to days automatically rendering you useless if you have no power backup generator at home.
3). Low Pay: While the opportunities for software developers in Africa are quite high, the salary is often disappointing. Many talented programmers end up seeking better opportunities overseas. In fact I quit my full-time job because of this reason.
4). Lack of Support for Tech Start-ups: There are few venture capital firms in Africa willing to invest in new ideas, which makes it difficult for tech start-ups to get off the ground. It's just sad, you can have an idea and just die with it.
So in summary, it's not a walk in the park to be a developer in Africa, but despite all of that I am glad to be a part of the African journey, having the opportunity to had work at a tech agency firm on various projects ranging from healthcare to finance, I find it rewarding to know that my work has contributed to a better future for my continent. 🤞6 -
How does programming influence a programmers daily life?
1. We start counting from zero.
2. We observe software more than using it. What is the algorithm behind it? Which Data structure is used?
3. Greeting people with "hello world".
4. Assigning variables to people.12 -
I hate the mentality that our only hobby as programmers should be coding. Sorry but I enjoy crochet, reading, video games, and fashion. I'm not dedicating my entire life to coding. If that means it's more difficult to get a job so be it. I'll dedicate some time to coding but not all my time. I hate the kids i went to college with who would judge you if you github account didn't have green squares every single day. Sorry I just can't focus on coding that much. I need a fucking break sometimes. I can't just be a coding robot. Maybe im not meant to be a programmer. Maybe that's why I still don't have a job when I graduated 11/20 and it's 02/02 but fuck. I can't just be a program robot. (Sorry I'm a little drunk and sad)25
-
That moment when you come out of your zone & discover you neither had breakfast or lunch and the playlist has stopped hours ago!2
-
Met colleague at work
Him: You programmers don't like sleeping at all. You should try to sleep and look fresh like me ... Blah blah blah... (You get the picture)
Me: *just smiles and watch him go*
(But what I really wanted to say)
Me: 'Well you know what, most programmers don't sleep much not because sleep deprivation is fun or we're in some kind of cult where it's some daily ritual. But when they need to send in an update; usually on a feature to make YOUR life easier OR just can't seem get their code to run right, and they keep telling themselves; "5 more minutes", "I have a good feeling about this modification" the minutes add up and before you realize it morning! And that's why some of us look like s*** in the morning'
(And then turn around to leave only to come back really quick like I just remembered something)
Me (again): "And don't think that we enjoy it. At least the ones I know don't. It's simply a fr****** work hazard!"5 -
Yesterday, I tried to code without googling to see how far I can go. After 20 minutes of coding I run into a problem. I just couldn't make my angularjs app to work with ASP.Net MVC antiforgerytoken. I tried my best to solve it but no luck.
After 2 hours I finally gave up and connect my laptop to network and search for answer, within a few seconds. Google give my this link: http://ojdevelops.com/2016/01/....
After only few minutes I finally make my code to work. And I realized that there is no way I can figure this things out using only my head. I still need the help of community to get things done.
So my question is. During the 80's and 90's how did the old programmers get themselves unstuck when problem like this arrive?
8 -
Stack overflow is overrated
With that I mean that a lot of people think that stack overflow is the best thing that every programmer has and can't live without it. That if stack overflow is down, nobody is able to write a single line without bugs. That 47.24% of a programmers time is spent searching on stack overflow. Sure, it is helpful for finding answers, and some are very good at explaining stuff, but it's not essential. I made an account when I started coding, because it "sure is the most important thing, right?", but the only thing I have done with it is changing the profile picture, because I simply don't use stack overflow that much. When I search my problems on Google, I mostly find the answer on some specific forum for that library I'm using, or more often, in the official documentation for it, no need for stack overflow. I'm not trying to say that it is not useful at all or that it should be taken down because nobody uses it, but that it is not essential in every programmers life.9 -
I feel like there are more and more people who only THINK they can program, but in reality they barely can make the “Hello, world” program. Many of them come from all of these “online courses”, I’m not saying that from there come only the bad ones, but many of them are bad programmers, who just think that one or two courses is good enough.
You have to gain experience by doing actual work, not by doing pre-baked exercises. In real life most of things you have to solve with your imagination - Stackoverflow will only provide you some raw draw!4 -
** Programmers Speak **
Don't know much about real life,
But Relationships in Laravel are important. -
I spent over a decade of my life working with Ada. I've spent almost the same amount of time working with C# and VisualBasic. And I've spent almost six years now with F#. I consider all of these great languages for various reasons, each with their respective problems. As these are mostly mature languages some of the problems were only knowable in hindsight. But Ada was always sort of my baby. I don't really mind extra typing, as at least what I do, reading happens much more than writing, and tab completion has most things only being 3-4 key presses irl. But I'm no zealot, and have been fully aware of deficiencies in the language, just like any language would have. I've had similar feelings of all languages I've worked with, and the .NET/C#/VB/F# guys are excellent with taking suggestions and feedback.
This is not the case with Ada, and this will be my story, since I've no longer decided anonymity is necessary.
First few years learning the language I did what anyone does: you write shit that already exists just to learn. Kept refining it over time, sometimes needing to do entire rewrites. Eventually a few of these wound up being good. Not novel, just good stuff that already existed. Outperforming the leading Ada company in benchmarks kind of good. At the time I was really gung-ho about the language. Would have loved to make Ada development a career. Eventually build up enough of this, as well as a working, but very bad performing compiler, and decide to try to apply for a job at this company. I wasn't worried about the quality of the compiler, as anyone who's seriously worked with Ada knows, the language is remarkably complex with some bizarre rules in dark corners, so a compiler which passes the standards test indicates a very intimate knowledge of the language few can attest to.
I get told they didn't think I would be a good fit for the job, and that they didn't think I should be doing development.
A few months of rapid cycling between hatred and self loathing passes, and then a suicide attempt. I've got past problems which contributed more so than the actual job denial.
So I get better and start working even harder on my shit. Get the performance of my stuff up even better. Don't bother even trying to fix up the compiler, and start researching about text parsing. Do tons of small programs to test things, and wind up learning a lot. I'm starting to notice a lot of languages really surpassing Ada in _quality of life_, with things package managers and repositories for those, as well as social media presence and exhaustive tutorials from the community.
At the time I didn't really get programming language specific package managers (I do now), but I still brought this up to the community. Don't do that. They don't like new ideas. Odd for a language which at the time was so innovative. But social media presence did eventually happen with a Twitter account that is most definitely run by a specific Ada company masquerading as a general Ada advocate. It did occasionally draw interest to neat things from the community, so that's cool.
Since I've been using both VisualStudio and an IDE this Ada company provides, I saw a very jarring quality difference over the years. I'm not gonna say VS is perfect, it's not. But this piece of shit made VS look like a polished streamlined bug free race car designed by expert UX people. It. Was. Bad. Very little features, with little added over the years. Fast forwarding several years, I can find about ten bugs in five minutes each update, and I can't find bugs in the video games I play, so I'm no bug finder. It's just that bad. This from a company providing software for "highly reliable systems"...
So I decide to take a crack at writing an editor extension for VS Code, which I had never even used. It actually went well, and as of this writing it has over 24k downloads, and I've received some great comments from some people over on Twitter about how detailed the highlighting is. Plenty of bespoke advertising the entire time in development, of course.
Never a single word from the community about me.
Around this time I had also started a YouTube channel to provide educational content about the language, since there's very little, except large textbooks which aren't right for everyone. Now keep in mind I had written a compiler which at least was passing the language standards test, so I definitely know the language very well. This is a standard the programmers at these companies will admit very few people understand. YouTube channel met with hate from the community, and overwhelming thanks from newcomers. Never a shout out from the "community" Twitter account. The hate went as far as things like how nothing I say should be listened to because I'm a degenerate Irishman, to things like how the world would have been a better place if I was successful in killing myself (I don't talk much about my mental illness, but it shows up).
I'm strictly a .NET developer now. All code ported.5 -
Somebody made a fake review on my app! That's how I dealt with him 😂
The app is "My Classes" on app store
6 -
//Random Mr. Robot thought//
So this picture and this quote in general has been in my mind quite recently. The first time I saw this scene it just passed through my mind as just a wierd quirk of elliot. But upon further thinking, I question that given Elliot is someone who specializes in network security in a sense. A part of which focuses on finding exploits in networks or even software in general( basically finding the worst in them). And the more I think about that,the more I come to realisation that just like most programmers mix together logic in their life in dealing with people, this scene stands out as an example of just that happening with Elliot and what perhaps, makes him such a good hacker. Perhaps we could all learn from this, or perhaps I'm just looking too much into this. Eh.
4 -
My ex-boss who had 35 years of experience in IT Industry, didn't know one single fucking coding language, obviously had no clue about source control or anything even remotely related to computers, and had been project manager of a project having over 1 million lines of totally undocumented code split into 389 files with no apparent structuring. All variables were either alphabets or names of programmers who developed them.
Code was in Python 2 and had bugs/line ratio ~= 5.
He asked to write a 'wrapper' class and somehow run it in Java and fix all bugs automatically. (insert Shia LaBeouf's magic GIF here)
When I said it doesn't make sense, he said you should put in hard work and do it, and not give excuses.
Time given to do this - 1 hour :-P
Good thing I quit that shit place and that pathetic moron. Love my new job and life! :D
Seriously managers should trust their developers and allow some degree of freedom. It helps a lot.4 -
I finally got a job at a tech company (although it's not a tech job) with a very good work/life balance.
Therefore, I plan on getting more serious about properly learning how to program in my spare time, also because, being a tech company, programmers are all over the place and are generally willing to talk about code.
I must say that while job hunting, devRant has been very useful to me since it allowed me to understand what kind of environment I'd like to work in. So far, the first few weeks of work have been great.
Ah, and the view from the office is unbeatable.
7 -
Wake Up. Cook. Eat. Work. Clean. Meetings. Work. Eat. Work. Netflix & Chill. Sleep. Repeat. 😎😝
How does your Work from Home look like?🧐
9 -
Not really a programming story... but a story about how programmers problem solve in real life.
Mods, sort me out if I'm out of line. Anyway, here goes.
So, my wife and I are arguing about whether or not the garage has insulated walls.
"It doesn't have insulated walls", I say, "I've been up in the rafters and their's no insulation there, so there's probably none in the walls."
"Well, why can't you just check", my better half responds, "You could just punch a hole in the wall to see."
Me, taking about 300ms to process this statement. Looks over, and punches a hole in the wall.
"See, no insulation!!!" I say triumphantly.
"What. The. Fuck. Did you just punch a hole in the wall for???"
deerinheadlights.gif
"Um, because you told me to?"
"Well I didn't mean to use your hand, I meant to get a small drill so the hole wouldn't be enormous."
"Well you didn't say "get a small drill", you said "punch"!
And as a laid down to sleep, on the couch, that night I still insist she told me to do it. And while I patched that hole, I still thought it was her fault. And to this day I still think it's her fault.
You cannot give a programmer these vague instructions and expect appropriate results.5 -
This belongs to the small bunch of things that makes me feel that life is beautiful.
For a pretty long time, I wanted to learn Haskell, and recently I really fell in love with the category theory. Now how exciting is that when you found that you can learn them both?
I just started it, and I guess it's a pleasure for any programmer who doesn't whine about math. It's free to read:
https://bartoszmilewski.com/2014/...
Or to build 😉
https://github.com/hmemcpy/...
4 -
As a final year student it makes me feel proud about things I do now, back in 2014 I was newbie to programming and after the years of study ( I skip collages in order to study by my self at home since my syllabus is too old for me to keep up with new technologies. ) I still feel like shit against brilliant programmers on the internet.
My journey untill now was frustrating and side by side it was fun too, I have spent several days to figure out very minor problems in my programme which made me forced to learn even more in order to avoid silly mistakes in future.
Those four lines of output were really true worth of that forty lines of code.
Every one of us, in their entire life at least once had thought about which programming languages to learn first and yes I was one of those guy who used to search on Google, watched YouTube videos and asked seniors for the same advice but soon I realized it's never enough to completely learn even one language. Each and every programming language is based on similar logical structure. No matter how different it's syntax is it won't make much of a difference.
I am thankful to internet and all of those guys who make video tutorials, help on q&a forum (stack overflow) , publish posts on website and all of IT community guys. I made it this far it's all thanks to you and I know it's just beginning of spectacular journey ahead.2 -
probably the one who sent me 3 mails within 10 minutes regarding 3 different positions, and all were addressed to someone else (Hello, Mr. Completely Different Name), so i replied telling him that's not me, and gave him the info to fix it in their db. he apologized profusely and said he fixed the error.
Next day I got two mails for another two positions, with the same incorrect name.
Or the one with whom I had half an hour phone "interview" for a specific position, they couldn't answer even the most basic technical question about the project, but invited me to an in-person interview and said my questions will be answered there, the phone interview was just to make sure they don't send completely offtopic people to the interview with the client (so far acceptable).
On the in-person interview, it was partially a repetition of the phone one, but okay, lady from the company is talking to me first time in her life. We get to the part where I can ask my questions, so I ask those basics about the project again, and her answer is:
"Oh, i don't know, i'm not a technical person, you'd have to ask that to the technical person from the company, I'm an hr person from the recruiting company."
"Wait... so... not only was this whole meeting a waste of my time, but you also lied about what it is, when you scheduled it with me on the end of the phone interview?"
"Well... it wasn't a waste of time, we like to meet the candidates in person before we forward them to actual interviews in the company, to make sure that they're not completely offtopic."
"... and how exactly do you think you'd be able to evaluate that, since you're not at all a technical person and know nothing about the project??"
" Well, i talk to programmers a lot, so i've picked up quite a bit of the terms."
...7 -
Could this be the programmers life +dating a programming language and for food add especially coffee. I feel it applies to me in a way.
1 -
At a party, discussing possible projects with some other programmers there.
So, does that mean I have no life outside of developing?7 -
Work from Home was not the cup of tea for most of us before Covid-19. 😱
Some really love working in the comfort of their home like your oh-so-lovely HR and some are scratching their heads like your beloved Project Managers.😂
The Designer is loving his space. 😍
Tester is enjoying some good naps in between the working hours. 😴
and... What do you think programmers would be doing? 🧐
Well.. well.. well.. Programmers don't really feel any change. Coding then and Coding now. 😎
How's your Work From Home Going?
4 -
I feel like "programmers are not computer technicians" joke is kinda overused lately. It doesn' matter if we are not technicians, we are very knowledgeable in computers and people knows that. People of course will try to get help from you when they can so it's not a wonder that they ask you to help with something they are not confident. Everyone that exercises practical professions lives through that. If your sister-in-law is a mathematician it's normal to ask for help if you are not able to come up with the right algorithm for the task. People depend on each other. That's how we survive.
But I'm not saying start helping everybody that can't open a pdf file. Just know who to choose to help. If they are a capable person or someone that's a part of your everyday life they will most likely repay you when you are also in need. Believe me everyone needs help time to time.3 -
Making your build site go live at 12am, stay up til 2am working on bugs, wake up at 5am to continue working on bugs.
The programmers life1 -
Programmers life reaching final day! [Spanish comic] [Don't need to know Spanish to understand] it only say the day of the weeks... you gotta understand
-
🪙 The golden age of tech is coming to an end. We currently live in a world of tech built by engineers and great minds; both Windows and Linux are great in their own ways. PCs are the peak of engineering, both desktops and laptops because of how versatile, powerful and universal they are. They serve engineers, designers and end users. You can do anything you can imagine; because the great people who built it, did it in such way that they themselves could use and enjoy it.
📱 The tech of the future will become ever more limited. The next generation of humans will use Chrome OS gladly and not even feel limited because they never experienced the freedom provided by a true personal computer device. Android OS is already getting ever closer to restricting 3rd party APK installers. Big tech will do everything they can to limit freedoms and make everyone use cloud, where they can charge $ for every damn click.
☎️The consumer-facing tech will become increasingly dumbed-down over time. The programmers and engineers will be still able to use "true" tech, but only for work. In everyday life, they will have to be content with the dumb limited tech.
And there is nothing we can do to stop it.9 -
Wondering how many of you have ADD/ADHD, diagnosed or not. I've heard people say that many programmers have ADD or ADHD and that it generally makes them a better programmer. I myself have ADD and I feel like it makes me a better programmer, but I have to work harder at paying attention to my wife/social life.24
-
! rant
Sorry but I'm really, really angry about this.
I'm an undergrad student in the United States at a small state college. My CS department is kinda small but most of the professors are very passionate about not only CS but education and being caring mentors. All except for one.
Dr. John (fake name, of course) did not study in the US. Most professors in my department didn't. But this man is a complete and utter a****le. His first semester teaching was my first semester at the school. I knew more about basic programming than he did. There were more than one occasion where I went "prof, I was taught that x was actually x because x. Is that wrong?" knowing that what I was posing was actually the right answer. Googled to verify first. He said that my old teachings were all wrong and that everything he said was the correct information. I called BS on that, waited until after class to be polite, and showed him that I was actually correct. Denied it.
His accent was also really problematic. I'm not one of those people who feel that a good teacher needs a native accent by any standard (literally only 1 prof in the whole department doesn't), but his English was *awful*. He couldn't lecture for his life and me, a straight A student in high school, was almost bored to sleep on more than one occasion. Several others actually did fall asleep. This... wasn't a good first impression.
It got worse. Much, much worse.
I got away with not having John for another semester before the bees were buzzing again. Operating systems was the second most poorly taught class I've ever been in. Dr John hadn't gotten any better. He'd gotten worse. In my first semester he was still receptive when you asked for help, was polite about explaining things, and was generally a decent guy. This didn't last. In operating systems, his replies to people asking for help became slightly more hostile. He wouldn't answer questions with much useful information and started saying "it's in chapter x of the textbook, go take a look". I mean, sure, I can read the textbook again and many of us did, but the textbook became a default answer to everything. Sometimes it wasn't worth asking. His homework assignments because more and more confusing, irrelavent to the course material, or just downright strange. We weren't allowed to use muxes. Only semaphores? It just didn't make much sense since we didn't need multiple threads in a critical zone at any time. Lastly for that class, the lectures were absolutely useless. I understood the material more if I didn't pay attention at all and taught myself what I needed to know. Usually the class was nothing more than doing other coursework, and I wasn't alone on this. It was the general consensus. I was so happy to be done with prof John.
Until AI was listed as taught by "staff", I rolled the dice, and it came up snake eyes.
AI was the worst course I've ever been in. Our first project was converting old python 2 code to 3 and replicating the solution the professor wanted. I, no matter how much debugging I did, could never get his answer. Thankfully, he had been lazy and just grabbed some code off stack overflow from an old commit, the output and test data from the repo, and said it was an assignment. Me, being the sneaky piece of garbage I am, knew that py2to3 was a thing, and used that for most of the conversion. Then the edits we needed to make came into play for the assignment, but it wasn't all that bad. Just some CSP and backtracking. Until I couldn't replicate the answer at all. I tried over and over and *over*, trying to figure out what I was doing wrong and could find Nothing. Eventually I smartened up, found the source on github, and copy pasted the solution. And... it matched mine? Now I was seriously confused, so I ran the test data on the official solution code from github. Well what do you know? My solution is right.
So now what? Well I went on a scavenger hunt to determine why. Turns out it was a shift in the way streaming happens for some data structures in py2 vs py3, and he never tested the code. He refused to accept my answer, so I made a lovely document proving I was right using the repo. Got a 100. lol.
Lectures were just plain useless. He asked us to solve multivar calculus problems that no one had seen and of course no one did it. He wasted 2 months on MDP. I'd continue but I'm running out of characters.
And now for the kicker. He becomes an a**hole, telling my friends doing research that they are terrible programmers, will never get anywhere doing this, etc. People were *crying* and the guy kept hammering the nail deeper for code that was honestly very good because "his was better". He treats women like delicate objects and its disgusting. YOU MADE MY FRIEND CRY, GAVE HER A BOX OF TISSUES, AND THEN JUST CONTINUED.
Want to know why we have issues with women in CS? People like this a****le. Don't be prof John. Encourage, inspire, and don't suck. I hope he's fired for discrimination.11 -
Programmer OAth. Just read on a github repo
0. I will only undertake honest and moral work. I will stand firm against any requirement that exploits or harms people.
1. I will respect the learnings of those programmers who came before me, and share my learnings with those to come.
2. I will remember that programming is art as well as science, and that warmth, empathy and understanding may outweigh a clever algorithm or technical argument.
3. I will not be ashamed to say "I don't know", and I will ask for help when I am stuck.
4. I will respect the privacy of my users, for their information is not disclosed to me that the world may know.
5. I will tread most carefully in matters of life or death. I will be humble and recognize that I will make mistakes.
6. I will remember that I do not write code for computers, but for people.
7. I will consider the possible consequences of my code and actions. I will respect the difficulties of both social and technical problems.
8. I will be diligent and take pride in my work.
9. I will recognize that I can and will be wrong. I will keep an open mind, and listen to others carefully and with respect.4 -
There's a classic joke about how programmers check both ways on a one way street because users are so stupid.
Well I took a walk on my break and literally 30 seconds from the door to my building someone was going the wrong way on a one way street.
Does art imitate life, or does life imitate art?7 -
Dev goals for 2018? Oh my..
#1: Never have to post my own question on Stack Overflow.
#2: Stop fixing everyone's computer for free.
#3: Stop coding while intoxicated (at home worry - don't worry ;)
#4: More side projects.
and..
#5: Buy more coffee varieties 😂😂😍 -
Food and Programmers life:
Spaghetti —> My Code
Pizza —> We are spending the night working in the office
Power Drinks —> delivery date is tomorrow morning
Candy —> extra task
Coffee —> bug massage
Water —> wash your face, we have meetings in five minutes
Truffle —> fu** BlockChain
KitKat —> upgrade your phone please
Lollipop —> one more time please
Marshmallow —> do you like some Nougat?7 -
There's this thought that keeps popping up in my head more frequently recently.
We are people who do heavy mind work. Our quality of life directly depends on our ability to come up with solutions. We've been training our minds for years, for decades, to get to the point where we are now.
Now stop for a moment. And imagine. You wake up one morning and you realize you can no longer code. You forgot all of it. You still can copy-paste answers from SO, but you don't know what questions to ask to get to those answers.... Your mind has pulled the DROP TABLE PROGRAMMING;COMMIT; stunt. From hero to zero in just 1 night.
You have no clue what happened, no idea whether you will recover. How does that affect your identity? Would you still try to climb the programmers' tree to the sweet spot you are in now? Would you choose some simpler profession instead, considering your age and time required to master that other profession? If you choose another profession - what would it be?
What would you do with your personal projects? You can't continue them yourself obviously... Would you let them die with the loss of your skills?
How closely is your profession related to your identity?
Now that I consider myself a person who's quite good in the field, this is becoming one of my fears. Sadly, it'll most likely come true someday. Either some accident or just old age, or even diseases/conditions at younger ages - there are so many things that could mess up your mind - the sole tool critical for our profession [to the picky ones: lumbers can't swing axes w/o hands, postman can't deliver mail w/o legs, politics can't lie without tongues, and we, engineers, cannot build with our minds even slightly off].7 -
Long time ago, people who sacrificed their sleep, family, food, laught and other joys of life were called saints now, they are called programmers.1
-
Hello and welcome, to a presentation in which I will tell you my thoughts on the shortcomings of modern day computers and programming practices.
Computers are based on a very fundamental and old idea, folders, and files, a file is basically a concrete amount of data, whereas a folder is a group of files, and it comes from the real life concept of files and folders, now it might be quite obvious already that using a concept invented in 1898 by a guy called Edwin G. Seibels, might not be the best way for computers to function in the year 2020, but alas, it is.
Unless of course, you step into the world of a programmer.
A programmer’s world is much different, they use this idea of a data structure, or in simpler terms, an object. An Object is just like what you would think of as an object in your head, something with different properties that you can think about in different ways, for example your mobile phone, it has a battery percentage, it has a screen size, it has free space available. Programmers use these data structures to analyse data very quickly, like finding all phones with a screen size bigger than a certain size for example.
The problem is that programmers still use files and folders to create the programs that use these objects.
Consider this example.
Let’s say you want to create a virtual version of a drink bottle, consider what properties it will have, colour, volume, height, width, depth, material, etc..
As a programmer, you can leverage programming features and change the properties of a drink bottle directly, if you wanted to change the colour, you just say, drink bottle “dot” colour, equals blue, or red.
But if the drink bottle was represented as a file, all the drink bottles data would be inside the one file, so you would have to open the whole file, find the line or section of the file that has the colour data of the drink bottle, and select it, highlight it, delete what’s there, and type in your new value.
One way to explain this better is to imagine a folder that now represents the drink bottle, imagine adding a new file into that folder that represents each property I described before, colour, volume, etc.., well now, you could just open that folder, find the file for colour, either by looking with your eyes or you could do a file search in the folder for a file called colour, open it, and edit the value inside. This way of editing objects is the one that more closely represents the way programmers and a program itself interacts with objects inside a running programming language.
But the thing is, programmers don’t use the folder/file way of creating objects and putting them into programs, because it would be too cumbersome, they just create 1 file for an object, or have lots of objects in a file, and create all the objects in 1 file, and then run the program which creates the objects, then when they stop the program, it deletes the objects. So there is no actual link between the object in a file and the object that the program creates by reading the data from that file, if you change the object in your program, it does not get saved to the file.
So programmers created databases to house these objects, but there is still a flaw in databases, they are hard to interface with, and mostly databases are just used to send data or retrieve data from, programmatically, you can’t really browse a database the way you can browse the files on your computer. You can, but database interfaces are not made to be easily navigated the way files and folders are.
As it stands, there is no way to store objects instead of files on your computer and interact with them in complex ways the way programmers can inside the programs they create.
If the idea of an object became standard the way a file and folder is standard, I think it would empower human’s a great deal to express things far more easily and fluidly than they can today.
Thanks for reading.8 -
Oh no AI can destroy hummanity in the future! It is like skynet and such... Bad! It will be the end! FEAR THE AI!
Yeah so i cant sleep now so im writting a rant about that.
What a load of bullshit.
AI is just a bunch of if elses, and im not joking, they might not be binary and some architectures of ML are more complex but in general they are a lot of little neurons that decide that to output depending on the input. Even humans work that way. It is complicated to analyse it yes. But it is not going to end humanity. Why? Because by itself it is useless. Just like human without arms and legs.
But but but... internet.... nukes... robots! Yeah... So maybe DONT FUCKING GIVE IT BLOODY WEAPONS?! Would you wire a fucking random number generator to a bomb? If you cant predict actions of a black box dont give it fucking influence over anything! This is why goverment isnt giving away nukes to everybody!
Also if you think that your skynet will take control of the internet remember how flawless our infrastructure is and how that infrastructure is so fast that it will be able to accomodate terabytes per second or more throughput needed by the AI to operate. If you connect it to the internet using USB 2.0 it wont be able to do anything bloody dangerous because it cant overcome laws of physics... If the connection isnt the issue just imagine the AI struggle to hack every possible server without knowing about those 1 000 000 errors and "features" that those servers were equiped with by their master programmers... We cant make them work propely yet alone modify them to do something sinister!
AI is a tool just like a nuclear power. You can use it safely but if you are a idiot then... No matter what is the technology you are going to fuck shit up.
Making a reactor that can go prompt critical? Giving AI weapons or controls over something important? Making nukes without proper antitamper measures? Building a chemical plant without the means to contain potential chemical leak? Just doing something stupid? Yeah that is the cause of the damage, not the technology itself.
And that is true for everything in life not only AI.5 -
*revving chainsaw noises*
Today I started nuking leftover project code.
At the end, some projects shrunk by roughly up to 40 % .
Can anyone explain to me why programmers have such an awful hoarding syndrome?
Why do you keep shit that might unleash complete havoc cause it hasn't been touched since years and noone knows id it still works?
It's like having a leg with gangrene and keeping it cause "it doesn't look that bad".
For fucks sake. Clean up and remove shit when it's not necessary anymore.
Reason why I did a bloody gore massacre in nearly a dozen projects... After all the rework of networking, it's finally evident which projects have a bad / nasty behaviour of "fucked up" connection handling (HTTP 1.1).
And when my gory massacre removal goes life, I think 25-35 % of persistent connections on the loadbalancers will vanish. Maybe even more, since some very nasty stuff was in some projects.
Like "let's implement monitoring without having any clue about how monitoring works and even less clues about how TCP/ HTTP works."
*Bangs devs heads on table*
Stop. Doing. Stupid. Things.
For fucks sake.
:@ :@12 -
I honestly don't understand people who genuinely believe formal schooling will cover all the basics they need to know to do a real-life job, and still get barely passing grades on all relevant subjects.
I genuinely don't understand people who copy GitHub projects to pass classes, and graduate from a university with goddamn StackOverflow instead of a brain.
Whom I understand even less are people who don't do anything major-related on their spare time.
I mean, change your fucking major, do what you actually like, do things that actually light your nuts with passion.
Please don't waste my time pretending you are in it not just because it's potentially well-paid and "cool".
Please don't waste my time being my coworker.
Yes, I'm looking at you, trendy wanker with a CS degree and no personal projects.
P.S. Junior here. Yes, I'm full of hatred for all the "real programmers" in the industry out there. I hoped for a better experience.
P.S.S. I mean absolutely no offense to people using either GitHub or StackOverflow outside of the aforementioned context.10 -
I'm bored af working on crappy php56 legacy apps written by short sighted programmers, makes my life miserable, but the pay is pretty good for a remote job which is pretty rare in here. Meanwhile I'm interested on exploring fundamental stuff on computer science and experimenting new techs.
I'm thinking about doing a PhD but too afraid if I can't finish it or the future opportunity isn't good enough since I live in 3rd world country in southeast asia. Also it probably takes ±8 years to finish it including the preparation.
I have no question, but it would be great if you have some advice.1 -
There has been a post today about the existence of too many js frameworks. Which reminds me of this awesome post https://hackernoon.com/how-it-feels...
At first I thought someone was corpseposting, as it is my understanding that the js ecosystem is calming down a bit. But then I noticed that post got almost 20 upvotes. So here's my thoughts:
(I'm not sure what I'm ranting about here, as it feels kinda broad after writing it. I think it's kinda valid anyhow.)
I'm ok with someone expressing frustration with js. But complaining about progress is definitely off to me.
How is too many frameworks a bad thing?
How does the variety and creation of more modern frameworks affect negatively developers?
Does it make it hard to understand each of these new frameworks?
Well, there's no need to. Just because it has a logo and some nice badges and says it will make you happy doesn't mean you should use it.
You just stick to the big boys in the ecosystem and you'll be fine for a while.
Does it make you feel compelled to migrate the stack of every project you did?
Well, don't. If you don't like being on the bleeding edge of js, then just stick to whatever you're using, as long as it's good code.
But if a lot of companies decided to migrate to react (among others frameworks), it's because they like the upsides: the code is faster to write, easier to test and more performant.
In general, I'm more understanding/empathic with beginner js programmers.
But I have for real heard experienced devs in real life complain about having to learn new frameworks, like they hate it.
"I just want to learn a single framework and just master it throughout my life" and I think they're lowering the bar.
There's people that for real expect occupying positions for life, make money, but never learn a new framework.
We hold other practitioners to high standards (like pilots or doctors), but for some reason, some programmers feel like they're ok with what they know for life.
As if they couldn't translate all they learned with one framework to another.
Meanwhile our lives are becoming more and more intertwined with technology and demand some pretty high standards. Standards that historically have not been met, according to thousands of people screaming to their devices screens.
Even though I think the "js can be frustrating" sentiment is valid, the statement 'too many js frameworks is bad' is not.
I think a statement like 'js frameworks can go obsolete very quickly' is more appropriate.
By saying too many js frameworks is a bad thing you're
1) Making a conspiracy theory as if js devs were working in tandem to make the ecosystem hard,
But people do whatever they want. Some create packages, others star/clone/use them.
2) Making a taboo out of a normal itch, creating.
"hey you're a libdev? just stop, ok? stop"
"Are you a creative person? Do you know a way to solve a problem in an easier way than some famous package? it doesn't matter, don't you dare creating a new package."
I'm not gonna say the js world is perfect. The js world is frantic, savage, evolves aggressively.
You could say that it (accidentally) gives the middle finger to end users, but you could also say that it just sets the bar higher.
I liked writing jquery code in the past, but at the same time I didn't like adding features/fixing bugs on it. It was painful.
So I'm fine with a better framework coming along after a few years and stealing their userbase, as it happens almost universally in the programming world, the difference with js is that the cycle is faster.
Even jquery's creator embraced React.
This post explains also
https://medium.com/@chrisdaviesgeek...13 -
many many times in the past I had this impostor syndrome in various situations but I never lost faith in my dev skills!
you have to be humble to realise that this situations are fine and that you will learn something from it (not necessarily tech things, but also how life works). Also you have to realise that development as everything else in life is just never ending learning endeavour! When you accept all of that, impostor syndrome goes away forever.
It's been around 3 years since I felt like impostor for the last time because I accepted who I am as a person.
It crawled up on me last week in a different way - I was thinking of myself - what if I am just really good at googling things and understanding how those things work but I am also very capable problem solver so I can understand the principle and apply it to my code.
Then I realised - ok, that's what programmers do! So that's the story of how the impostor syndrome actually become confirmation syndrome!
Folks, believe in yourself, be forgiving to yourself as we all were there, give yourself some time as people don't become good developers overnight - and this is OK.3 -
I was once handed a very old PHP project that I had to make some changes to. I thought it would be a piece of cake. But the moment I looked at the code, I knew it wasn't going to be easy. It was so poorly written, it took me hours to figure out what was actually going on. Now these were the times when I was already quite disturbed mentally and emotionally, and this shitty PHP code only made it worse. At one point, I was like, fuck this shit I'm gonna quit this job.
Thankfully, the client soon emailed that the requested changes weren't needed anymore.
I personally have nothing against PHP. I have created some amazing stuff with it. But it's the programmers that don't follow the best practices that piss me off. I mean, how fucking hard can it be to write clean code. You might save your time today by taking shortcuts but you'll make life hell for the people who might have to maintain your code in the future. -
2019 goals...
Launch my app in Play store
Build more projects
Make work fun for client
Earn more
Learn learn and learn.... -
"The only way to learn a new programming language is by writing programs in it." - Dennis Ritchie
So, how are you learning - By writing programs or by Ctrl + C, Ctrl + V? 😛
3 -
Graduating from school, To find out that there are much (much) better coders, programmers etc. Out there. Made life all the more interesting.
-
So guys you all remember or know or will know how it is to be a student. Not that much money around, have to be responsible for the first time of your life and I don't know since we're all programmers here our Desktop/laptop that we invested our money on for the university is our life.
Recently I have found out that something is up with my laptop. My Ram should have been 8GB but it shows only 4. I almost fainted, I thought the seller caught an idiot (me) and sold it like that. So I decide, for some reason, to buy 2x8gb ram so I can have 16 since its the max support of the system.
I open the laptop and what to see but my laptop had 2x4gb in there.
Regardless I installed the new ones to find out what else but my PC is now showing just 8gb.
"Calm down Nick" I said maybe GPU uses it but no it only shows 4gb ram, the same amount the laptop came with so I guess it's integrated.
So now I can only think that the problem is occurred because my Father, dropped the laptop when I specifically told him to not have it in dangerous high places. I Googled around but everyone is talking just swaping the ram chips well yeah I did that 100 times, still the same.
Tl;Dr I'm freaking out because theres something up with my laptop9 -
I don't like most of the people around me (programmers). I find most of them boring and with a really "flat" personality with no interests other than coding. I enjoy coding myself but sometimes I feel that I don't belong to this community. There is more in life than just your job.1
-
Embracing the change
meanwhile implementing change number: oh wait, Forgot the count 🥵🤯
Ever happened?
2 -
Web code editors are shit for interviews!!
I was given a timed interview test to code on a hackerearth’s code editor. First of all I have never used hackerearth’s code editor because they suck. The problem was very simple and I cleared the round anyways when an actual human saw my code. But my point is why are programmers creating shit editors for other programmers in a timed environment. I couldn’t figure out for the life of me how the fuck I should take an input and output that in this shit editor. The code logic was ready but the test cases failed.
So Should I be learning about hackerearth’s shit code editor in an interview with a timer or should I be judged on the code logic in the specified time?
I seriously find these web code editors most of them annoying. Cause they aint good enough. You need time figuring out the tools first and then code the logic.
Usually in your job you’re gonna use the editor of your choice. Not a fucking shit fucked half arsed hackerearth code editor. My rant is for those of you if you’re taking interviews on such platforms, be there. Don’t rely on those platforms. This automated crap is still crap.4 -
I feel I need to write some side project summary somewhere.
So here it is about 3 months later:
- deleted 90% of code I created during last 3 months
- rewrote backed 5 times
- 200 lines POC still waiting to put in any meaningful architecture on frontend
- frontend part after aurelia, next, gatsby, react I think it would be vue powered by nuxtjs
- forced myself to buy food for whole week and don’t go out (except go running ) before I finish at least what I wrote on whiteboard
Now some positive news:
- there is not much left to be fucked up, removed or unnecessary added
- I think I got a plan
- this is probably first side project that makes me happy for such long time
- there is some probability it would help people and this is what I want to do in my life
Most important is that I know it would take at least half a year to do basic version of it and I don’t care.
Wish me luck so I can put some sneak peak after next 3 months. -
Alright fellow sweaty programmers, mama Kiki is here to teach you the basics of hygiene.
TEETH
- If you have a toothpaste prescription, use it.
- Every single whitening toothpaste is a scam. Don’t use them.
- Every single over-the-counter toothpaste that decreases sensitivity does work. If your teeth are sensitive, use it.
- Otherwise, buy the cheapest name-brand toothpaste.
- Use dental floss. As long as it’s flat and waxed, the cheapest one will do.
- When flossing, never move the floss back and forth as if you try to saw through your gums. Just put the floss in, then out. Repeat if necessary.
- Don’t put your toothpaste on your toothbrush. Put a small amount of it directly in your mouth with a bit of water. Close your mouth and spread toothpaste all over your teeth using a rinsing motion, as if it was mouthwash. Now your teeth are completely covered.
- When brushing teeth, don’t use -90°/0°/90° angles. Use -35°/35°. This way you will spend less time while getting better cleansing. Bristle ends should touch where your teeth meet your gums.
- Get yourself a tongue scrubber. Scrub your tongue until what comes off of it is clean. Dirty tongue is why your breath smells bad, not dirty teeth.
- After you’re done, don’t rinse! Spit the toothpaste out, but let its residue stay there. The remineralization process is now started. If you follow the routine, you don’t need mouthwash at all.
- Drinking/eating sugary things, not washing your teeth and going straight to bed is the best way to get cavities ASAP. In your mouth, sugar quickly turns into the kind of acid that we use for soldering. It can strip the oxide layer off of copper. Do you know how after you drink Coke, your teeth become almost squeaky clean? That’s this. If you like sugary drinks, carefully drink them using a straw. Rinse immediately after you’re done drinking & eating.
SHAVING
- Get yourself an old-school safety T-razor, the one that takes suicide blades. It will last a lifetime. Mühle and Merkur are good manufacturers (not affiliated). Once you have it, for the rest of your life, you will only buy blades. This is the most environmentally friendly way to get a clean, close shave. Electric razors save water, but they often contain batteries.
- Because of how violently electric razor’s blades hit hair while cutting it, they chip your hair. This leads to your freshly grown hair being sharp, rough and unpleasant to the touch. The manual razor, on the other hand, produce clean edges. When your hair grows back, it will be softer than what you get with an electric razor.
- Feather brand blades (not affiliated) are the sharpest in the world. The sharper the blade, the less traumatic it is. Watch T-razor tutorials on YouTube. There are different shaving techniques that will get you a killer shave.
- T-razor blades last considerably longer than their modern soyboy single-use counterparts.
- Because of a single blade construction, T-razor almost never leaves irritation.
- Basically, modern single-use plastic blades are horrible for the environment, and they’re almost a scam for how much you get for your money. They’re only rivaled by printer ink. Use them only for intimate shaving, as they’re considerably handier down there.
- Always shave after hot shower.
- Before shaving, dry the skin surface. Apply shaving foam on dry skin only, as it contains chemicals that make your hair softer. When diluted, they’re not as effective, and shaving unsoftened hair is almost always unpleasant and dangerous.
- After applying the foam, wait about a minute for the foam to work. If the skin gets irritated, don’t wait for as long, or perhaps try a different foam brand.
- Before shaving, thoroughly clean your razor with hand sanitizer or ethanol. Ideally, it should be sterile. Using boiling hot water is also a good option, just be careful with it.
- After shaving, rinse off foam, immediately dry your skin with a clean towel, then apply aftershave. After applying it, don’t touch your skin until it completely dries. If you follow this routine, your skin won’t get any pimples, guaranteed.
- Scrubs won’t help you. Don’t use them.
More in the comments!11 -
I love commitstrip comic. There are others like Dilbert, devhumor, turnoff etc. Some are not continued now like Programmers life, which was also good. Which are your favourite comics related to dev?4
-
I almost everytime these days start counting from zero in real life and f**k up the calculations and recalculate and do the same mistake. I hate programming.
Happy programmers day -
I dare you to share your worst burn-outs , ever experienced ! And what are you doing now , to prevent it ?
2 -
"If you need motivating words, don't do it!"
It means that,
"If you are discouraged by someone telling you not do it, then you weren't probably meant to do it in the first place."17 -
They say that we are weird,
they say we don't have passion,
they say we don't have life,
they say we are a sacrifice for the world
.
.
I say we are the best mind who can save the world from its own. WE ARE PROGRAMMERS!!!
(except for C# programmers of course)5 -
Well today i went to grab a coffee at starbucks saw my best friend working decided to buy him one too i sit down we start talking and i saw him using visual studio code and asked him why don't you use vim and answered "vim is for programmers that don't know what to do with their life and cant decide what ide they like" i didn't think twice and slapped the shit out of him fuck him. I think i might need a new best friend.12
-
Anyone considered substance use to make you a better programmer? Personally I struggle with concentration for more than 6 hours a stretch and I just started vaping with no nicotine but I just read this and maybe it's what I need?
https://selfhacked.com/blog/...
I don't drink or do drugs but life is so competitive I think maybe I need an edge against prescription adderall programmers rising in the ranks....4 -
So, the story starts with me getting a job. Full-time job for the first time in my 21 years old life. After short conversation about how amazing this company is, after countless lies and stood questions they decided to hire me. I had to get come on Monday a week later with everything prepared.
So of course I did that and got to my workplace on designated time. Turned out nobody was expecting me, nothing was prepared for a new programmer and everyone seemed angry at me for no apparent reason.
After long talk with my new boss I got some less than 100$ pc with CPU that couldn't handle virtualization and expected me to work on software that needed extensive use of virtual machine.
PC is of course filled with all kinds of spying software that uses most of the resources. IT teams only job is to check if programmers are working their assess off for at least 8 hours a day.
I've filled a ticket about granting me access to Debian machine on the mainframe so I could work. No response for two weeks. I've lost hope already.
I have to work on open space with more than 30 engineers. Screams, phone calls, alarms, all at once, all the time. My colleagues seem to not care and I can't understand how.
I was tasked with rewriting major application because old developer did some half assed piece of burning shit. It took him more than one year, I'm finishing it in less than two weeks.
Of course nobody except for me is preparing any kinds of documentation. I had to reverse-engineer whole API for alarm system.
Salary is less than a junior programmer should earn.
But I'm stuck here for at least a year because nobody's here wants a guy whose only experience is as a freelancer. -
!rant
I'm not sure if it's good or bad, but lately I've lost that "love" for code, not coding itself, but the code in projects.
Because most of the time the projects are inherited, there is never enough time, It's always a priority. And let's be honest, most of the time programmers don't like others code. (Is it God Complex?).
What I do notice with this "new" philosophy it is that I do not stress when I do not like some development, I ask the "bosses" if there is time to change it or if we continue with how it is. I learn that it should be done better and I continue my life5 -
Fuck you "hackers"! You make my life miserable...
No longer can anyone simply enter their user name and password to enter an online app...
Now we as programmers have to leap from one fiery hoop on the precipice of a death defying cliff to another acidic hoop in some mystical forgotten cavern of the underworld just so our users can log in securely to our app... sigh... I'm looking at you Auth0 and Microsoft SSO / AAD !!!111oneeleven
I mean wtf even is a nonce?!
https://urbandictionary.com/define....
**gosh**
11 -
Entering 2021 strong with more knowledge and more experience 💙💪
2020 was a year of learning.
It taught us the value of time, to believe in ourselves, to make the best use of what we have, not take anything for granted and always keep learning.
Only then we can overcome our biggest fears
Wishing you all a very Happy New Year 2021
11 -
Oh my gosh, no one really knows here what is programming. Even teachers, which claim to be professionals in the subject doesn't know shit except for the basic theory. Nothing in practice.
It was evidenced by the largest job skill competition of Finland (Taitaja) that's for my-aged students (18). And yeah it's not higher education studies, just second degree, but that's where you should get the necessary practical skills for your work life.
The category I participated was website development, which is the only software development category.
It was a public event that is focused on showcasing different jobs. Well, what do programmers do, a viewer may ask. Even the responsible teachers and juries couldn't really answer properly. They just showed the specs we were following to create the crappiest of websites the short period of development time.
So we consume coffee and produce HTML, is that accurate representation of the whole industry?
All the other winners of different categories get a lot of job offers from companies when they win. I won gold last year (bronze this year) and I didn't get a single offer. Who would be interested in human HTML generator who can only make static websites anyway?
Programming is about problem-solving, not about graphic design and writing content.
And just to give you an idea the scale of the competition: last year I made a total of ~2000€ for the victory. And it is super easy if you just know what you are doing. That being graphic design and the making of a static page with a pinch of functionality.1 -
Critical Tips to Learn Programming Faster Sample:
Be comfortable with basics
The mistake which many aspiring students make is to start in a rush and skip the basics of programming and its fundamentals. They tend to start from the comparatively advanced topics.
This tends to work in many sectors and fields of Technology, but in the world of programming, having a deep knowledge of the basic principles of coding and programming is a must. If you are taking a class through a tutor and you feel that they are going too fast for your understanding, you need to be firm and clear and tell them to go slowly, so that you can also be on the same page like everyone else
Most often than not, many people tend to struggle when they reach a higher level with a feeling of getting lost, then they feel the need to fall back and go through basics, which is time-consuming. Learning basics well is the key to be fast and accurate in programming.
Practice to code by hand.
This may sound strange to some of you. Why write a code by hand when the actual work is supposed to be done on a computer? There are some reasons for this.
One reason being, when you were to be called for an interview for a programming job, the technical evaluation will include a hand-coding round to assess your programming skills. It makes sense as experts have researched and found that coding by hand is the best way to learn how to program.
Be brave and fiddle with codes
Most of us try to stick to the line of instructions given to us by our seniors, but it is extremely important to think out of the box and fiddle around with codes. That way, you will learn how the results get altered with the changes in the code.
Don't be over-ambitious and change the whole code. It takes experience to reach that level. This will give you enormous confidence in your skillset
Reach out for guidance
Seeking help from professionals is never looked down upon. Your fellow mates will likely not feel a hitch while sharing their knowledge with you. They also have been in your position at some point in their career and help will be forthcoming.
You may need professional help in understanding the program, bugs in the program and how to debug it. Sometimes other people can identify the bug instantly, which may have escaped your attention. Don't be shy and think that they'll make of you. It's always a team effort. Be comfortable around your colleagues.
Don’t Burn-out
You must have seen people burning the midnight oil and not coming to a conclusion, hence being reported by the testing team or the client.
These are common occurrences in the IT Industry. It is really important to conserve energy and take regular breaks while learning or working. It improves concentration and may help you see solutions faster. It's a proven fact that taking a break while working helps with better results and productivity. To be a better programmer, you need to be well rested and have an active mind.
Go Online
It's a common misconception that learning how to program will take a lot of money, which is not true. There are plenty of online college courses designed for beginner students and programmers. Many free courses are also available online to help you become a better programmer. Websites like Udemy and programming hub is beneficial if you want to improve your skills.
There are free courses available for everything from [HTML](https://bitdegree.org/learn/...) to CSS. You can use these free courses to get a piece of good basic knowledge. After cementing your skills, you can go for complex paid courses.
Read Relevant Material
One should never stop acquiring knowledge. This could be an extension of the last point, but it is in a different context. The idea is to boost your knowledge about the domain you're working on.
In real-life situations, the client for which you're writing a program for possesses complete knowledge of their business, how it works, but they don't know how to write a code for some specific program and vice versa.
So, it is crucial to keep yourself updated about the recent trends and advancements. It is beneficial to know about the business for which you're working. Read relevant material online, read books and articles to keep yourself up-to-date.
Never stop practicing
The saying “practice makes perfect” holds no matter what profession you are in. One should never stop practicing, it's a path to success. In programming, it gets even more critical to practice, since your exposure to programming starts with books and courses you take. Real work is done hands-on, you must spend time writing codes by hand and practicing them on your system to get familiar with the interface and workflow.
Search for mock projects online or make your model projects to practice coding and attentively commit to it. Things will start to come in the structure after some time.4 -
Girlfriend complains about how I'm always on my laptop, coding, and how I'm not spending enough time with her.
I tell her that my laptop is not the NUMBER ONE thing in my life, but She is.
Little does she know that as a programmer, I start counting from zero6 -
When people write me at 5am on Slack or Skype, they think, how nice and organized my life is that I am getting up early. Truth is, I have not slept yet. Programmers never sleep they just check their eyelids from inside. It's easier to stay awake till 6am, than to wake up at 6am!2
-
if (rant || disappointment) {
timeSinceLastOpenedTheWhatsApp = 4 weeks;
noOfMsgReceivedInLast1Week =0;
}1 -
wonder what life must have been like for programmers before there was version control..
http://blog.plasticscm.com/2010/11/...
Top Tags
Weekly Rant
View