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
-
Today I learned:
`/usr` stands for “universal system resources” not “user”
`/dev` stands for “device” not “development”
Had no idea.30 -
Today I learned.
FACE:B00C is used in the ipv6 address of v6.facebook.com
I'm impressed, well done4 -
Had to wake four people up at 2 am to fix a crashing service.
10/10 would deploy to production on Friday night again.
24 -
Saying yes to people who want a website for $100.
I've learned my lesson, all brand new websites now start at $1000.9 -
A few years ago:
In the process of transferring MySQL data to a new disk, I accidentally rm'ed the actual MySQL directory, instead of the symlink that I had previously set up for it.
My guts felt like dropping through to the floor.
In a panic, I asked my colleague: "What did those databases contain?"
C: "Raw data of load tests that were made last week."
Me: "Oh.. does that mean that they aren't needed anymore?"
C: "They already got the results, but might need to refer to the raw data later... why?"
Me: "Uh, I accidentally deleted all the MySQL files... I'm in Big Trouble, aren't I?"
C: "Hmm... with any luck, they might forget that the data even exists. I got your back on this one, just in case."
Luck was indeed on my side, as nobody ever asked about the data again.5 -
Life lesson learned:
If your girlfriend asks you what SO means, it's "Significant Other",
NOT StackOverflow.7 -
What I learned in the machine learning course so far, all the Buzzwords can be replaced by "statistical mathematics".5
-
I had a manager who wouldn't allow me to use bootstrap modals because he learned somewhere that adblockers block popups.
7 -
Things I learned this week so far:
Programmers consider talking to a rubber duck a totally normal thing4 -
Today I learned Slovakia is in fact a version control system, not country.
Things you find on Wikipedia these days.. 🤔
8 -
I learned that the technologies I use for my side projects are cooler than the side projects themselves.
-
Things I have learned:
-NEVER trust a group of people not to reply all to a large email
-NEVER trust a group of people not to reply to a group text
Screenshot is from yesterday, and violates my second lesson learned (Not my group text, not my fault)
5 -
"Senior Engineer/Dev/etc." is just the title for the guy who's learned from making the most mistakes.2
-
If there's anything I've learned till now then that's: You should know how to Google the *RIGHT* thing
Things I haven't learned: How to Google the *RIGHT* thing2 -
#1 life lesson I learned from coding?
Maybe not coding specifically, but I learned the difference between problem solving and solution finding.
Its helped me in a lot of areas of my life. Made friends and made enemies.
4 -
Yesterday I spent some time on the meta site for dba.stackexchange.com and found this one guy with 1 rep raging about how his questions aren't getting answered and how is answers are the best etc...
"I have 17 years of experience as a dba, blah, blah, blah, my answers are correct, blah, blah"
He got pretty destroyed by the mods and other users about how shit his answers were and how they weren't factually correct etc...
This just continues to show that no matter how much experience you have you won't always be right.
Same goes for my senior at work, he has 10 years more experience than me (I have 2) and he still asks for my point of view and help without being a dick about it.
I hope we'll all keep being nice people unlike that Stackexchange guy...2 -
I learnt to navigate in Vim 🤩.
Ik it's not much. But had heard so much about Vim and Emacs (tho still don't know why are they so popular, or how to use them), but I kept my distance after the first time I could not quit the application.26 -
Working with someone who just learned Git.
Woke up this morning to 200 .DS_Store files on master.
-.-12 -
I learned how to solve some problems using XOR.
This might be like when I learned to love regex.
*loud laugh reminiscent of Vincent Price in the Thriller music video*
What am I becoming?13 -
Completed Flexbox Froggy.
Finally Learned FlexBox , would recommend it 100%.
From: flexboxfroggy.com
12 -
Programming helped me realise, that I'm growing.
Since I've learned git long time ago, all my projects are archived and I can get back to them. When I look at my old code, I can see, how much I've learned, and how much more of a developer I've become.
And it motivates me to keep going.4 -
Pro tip:
Make sure you can RECOVER from your backups.
It's all well and good backing this and that up, but make sure that when the shit really hits the fan you can recover.
I've now 4 days into recovering a raspberry pi that ran:
Pi-hole
Snort
DHCP
VSFTP
Logwatch
Splunk forwarder
Grafana
And serveral other things... I've learnt my lesson4 -
Started a new job this week.
Just learned that my manager strictly prohibits while loops and "if else" statements.23 -
Basically script-kiddy-copy-pasting some C++ until I understood how it worked lol (and then learned it properly)3
-
I learned that there is no undo button in sql after wiping clean 1074 rows of data... #fmdl actually just #fm8
-
My coworker and I are both novice programmers: we both know a little about several languages.
So it's really cool when we learn something new from each other. I learned how to properly open a file in Python, and he learned that "\t" is the tab character.
It's a Win-Win for both of us!2 -
learned how to use dd! also getting into MUDs!
anyone else know of a good graphical mud client aside from mudlet?
9 -
"took you long enough" gave me a computer at five - was programming at 6, learned Python and Ruby by 10.3
-
Google Doodles : A place where I learned history of my country and world more than I've learned in my history class.
-
I installed Arch Linux and IM LOVING IT!!!!!!!!!!!!!!!!!!!
Learned so much already, best decision I’ve ever made17 -
After using Linux every day for 3 years today I learned that listing directories requires the execute permission.
In a misdirected attempt to solve my problems I also learned the basic concepts of SELinux before realising that SELinux is disabled on the host and not present on the guest.11 -
#1 life lesson learned from coding:
Don't work on projects for the government or any authority EVER!6 -
Django was the first web framework I learned. I didnt understood the praises for its documentation ... Until I started using Flask...3
-
!Rant
The moment you understand something, that you read the documentation instead of searching for the exact answer to your problem. -
Just learned how to solve linear recurrence problems with matricial calculations. This is absolutely wonderful.7
-
For fuck sake Facebook test your shit before you update!
Lesson learned, never update Facebook pods ... or even better never use Faceshit!
1 -
That turtle IDE thing we learned in middle school. I tried to make a game with that. Would not recommend.3
-
Wanted to use particles.js in my project aaaaaand I just learned the whole library O.O Time flies when you're having fun.
-
Yesterday I learned there was a chat feature in StackOverflow. I learned this because I finally for once in my life have StackOverflow reputation.
Discussing my excitement:
“Guess what topic it was.”
“Was it regex?”
“It WAS regex!”4 -
I just learned Javascript doesn't have tuples and nearly cried and/or vomited all over my keyboard. Pls no.12
-
I'm the kind of person that says "Fuck python, worst language, fuck C#, Java, Golang", assembly and C are superior.
But I have learned my lesson; Yesterday I learned enough C# to be able to make a windows app that connects to a another app via sockets. I tried first to do it with C++ but my app looked like shit and took me about a whole day to make. Then I tried with C#, got the App working on an hour, now I'm delighted with C#. I guess I have to be open-minded.8 -
!rant
I take my words back, teenage devs are not necessarily destinied to stay single. That's what I learned last week.5 -
One thing I've learned in the past year. Never start working on a task that's based on a lot of assumptions.3
-
Just "learned" that Singleton is a good design pattern with no disadvantages. And in MVC the model should be a singleton.
FML :^)4 -
Learning through documentation.
I learned one thing.... That how I can copy paste any thing in my code and comment it as "magic happens here do not touch."
Yeah thats my code learned from documentation (image below )
-
I started my part time job as a tutor today. Yesterday (while preparing) I learned how a browser actually renders a page and bunch of other stuff. Don't get me wrong, I kind of knew it. But not in such detail that I could ever explain it... even though I work in web development since 2011
This will be fun, I wonder what I will learn next2 -
<insert bear grylls meme>
Improvise. Adapt. Overcome.
Lesson learned: take measures before buying parts
4 -
w3schools around the age of 15. The rest I learned through my study and from friends (learned NodeJS from a friend for example)
-
Before I learned to use the gui and they saw a program cli: meh, ok sarcastically. After I learned the gui even if the program does absolutely nothing: wow! You have a future.1
-
Well I learned quite a lot about GUID/UUID from this Microsoft Engineer post:
https://blogs.msdn.microsoft.com/ol...3 -
Just learned display css properties. Took me long enough to make a damned HTML template.
Me no likes front end :(5 -
Learned HTML with a 50ct book from a 1 €-shop. Got interested in forums and learned PHP by analyzing phpBB and Itschi (you probably don't know the latter). Learned Java through school though it was only the basics. Now I'm a full stack developer at a Norwegian company. Fully self-taught.1
-
'Hey, I've learned proogramming from this book[...]' - said nobody ever while being honest to himself.3
-
How I learned different languages...
C->C++->HTML&CSS->JAVA->Android->python
.
.
PS Still learning more...7 -
Getting a job opportunity w/o a degree and only knowing what I learned as an ... obsessive ... hobby4
-
code code and code. There's no better way to learn other than practicing the material learned from docs.1
-
Knitting. It's absurd how technical a skill it is, and I definitely didn't realise that when I learned it!3
-
At first it seemed harsh, but then I learned that he committed code like
if (a == b)
return true;
else
return false;
9 -
Just learned that unicode U+14269 is the "troll" unicode character. I feel like this should be used more.
2 -
wk142: geekiest non-dev activity
Definitely music production. Especially when using real instruments and capture their audio, so everything is quantized (i.e. fixed to time grid) and very tightly recorded. I make metal, 'tis a precise genre. For one riff it sometimes take 20 takes, since I record 4 times my guitar.
I've learned for the past 10 years how to compose, mix, masterize, but also learned how to sing, learned how to play the guitar, learned how to compose drums and using my keyboard to play drums (people are often surprised I can play double kicks @ 230 bpm) so that I can have a basic drum layer to further edit
Pretty geeky, not a common subject I talk to people about :D2 -
Just learned how chained liste in C worked (I learned everything before but I was traumatised of the liste..) . It makes me excited.1
-
Learned via iOS tutor overnight to build a basic single page app. Told I can able to learn fast. Started as intern at a startup. Learned rapidly because I was the only one who building the entire product.
-
If there is anything I learned from Robert Martins in The Clean Architecture book is that: Marketing geniuses are fucking useless11
-
- Played with and learned Scratch
- Learned some Python, made some weird little programs
- Learned C, using two good books: K&R C and Zed Shaw's "Learn C the Hard Way" (back when it was still in development and was free to read on the internet)
- Made LOTS of programs in C
- Came back to Python when I wanted to learn network programming
- Learned some Racket/Lisp, Bash scripting along the way
- Now I use all of the above, minus Scratch -
If there's one thing I've learned from a-hole co-employees, it is to avoid ending up being like them.3
-
#1 life lesson learned from coding: There are things I just can’t be good at no matter how hard I try.3
-
Business Continuity / DR 101...
How could GitLab go down? A deleted directory? What!
A tired sysadmin should not be able to cause this much damage.
Did they have a TESTED dr plan? An untested plan is no plan. An untested plan does not count. An untested plan is an invitation to what occurred.
That the backups did not work does not cut it - sorry GitLab. Thorough testing is required before a disruptive event.
Did they do a thorough risk assessment?
We call this a 'lesson learned' in my BC/DR profession. Everyone please learn by it.
I hope GitLab is ok.2 -
The one thing I've learned most about developers is that developers like their lasagna more than their spaghetti.3
-
Are "HTML Developers" real? I think they are just young geeks under 17 who learned something new on the internet.3
-
Some people browse YouTube when they're bored..
I browse GutHub. Found this yesterday 😂
https://github.com/1337/...3 -
I've been writing various forms of OOP for three years and just now learned exactly what static means
-
Hidden pixel just scratched my finger while I was wiping the screen with my palm. Lesson successfully learned.1
-
Well I learned about sockets before I learned about REST so take your pick of any early project that got server data by opening a socket and requesting information that way every time a client connected.1
-
I just started a new job today and I fucking love it. I've learned more in a day than I do on a weekly basis in school. It's difficult but exciting as fuck to actually be able to use the technologies you've learned in a professional context.
-
Today I learned what actually happens if you don't close your database connections (because you forget) after you've used it. Feck all happens for the first 9 requests, and after that error 504 😂
1 -
Just learned how to write a for loop in kotlin and I now want to burn Java to the ground. When I first learned for loops in Java my brain almost imploded.2
-
Learned how to make Command Line Tools using python because of this fun weekend project.
Link - https://github.com/itsron717/XKCD1 -
TIL: PHP is also the name of a currency.
And compared to USD one PHP is worth about as much as the community makes it seem.6 -
When I just learned about PostgreSQL, I was pronouncing it like "postérgé", like protégé
why am I so cringe13 -
Today I learned:
In Java, you're supposed to compile a source file in its package one directory up, outside of its package. You can't compile the source file in its own package directory, for it will state "cannot find symbol" on files in the same package, even though they're in the correct package directory. That can be quite confusing at first.
Given the following directory structure:
|_
|_ \pkg
|_ _ Src1.java
|_ _ Src2.java (interface with static method)
and the following source:
package pkg;
public interface Src2 { static void doStuff() { ... }; } // assuming JDK8+, where static default methods are allowed
package pkg;
public class Src1 { public static void main(String[] args) { Src2.doStuff(); } }
..being inside the pkg/ directory in the console,
this won't work:
javac -cp . Src1.java
"cannot find symbol: Src2"
However, go one directory up and..
javac -cp pkg/*.java pkg/Src1.java
..it works!
Yeah, you truly start learning how the compiler works when you don't use the luxury of a IDE but rather a raw text editor and a console.1 -
I was thinking about the problems one of our clients faced with the launch of their project the other day, because things were rushed, stuff was omitted and in the end they could not meet the launch date, and I started making a list of hard lessons I learned over the years that would have helped them avoid this situation.
Feel free to add yours in the comments.
- Never deploy on Friday
- Never make infrastructure changes right before a launch
- Always have backups. Always!
- Version control is never optional
- A missed deadline is better than a failed launch
- If everything is urgent, nothing is important
- Fast and cheap, cheap and quality, quality and fast. Only one pair at a time can be achieved
- Never rush the start or the end of a project
- Stability is always better that speed
- Make technical decisions based on the needs of the project two years from now
- Code like you will be the only maintainor of the project two years from now. You probably will...
- Always test before you deploy
- You can never have too many backups (see above)
- Code without documentation is a tool without instructions
- Free or famous does not necessarily mean useful or good
- If you need multiple sentences to explain a method, you should probably refactor
- If your logic is checked beforehand, writing the code becomes way easier
- Never assume you understand a request the first time around. Always follow up and confirm
There are many more that should be on this list, but this is what came to mind now.2 -
Which is the secret rule that you've learned in your (dev) life?
My favourite one is "it works? Don't touch it."5 -
Learning the subprocess module in python, because os is deprecated. its a shame because i had just learned os
6 -
Went to an "Hour of code" event with my dev friends and learned how to do the snake game in javascript.
-
I started out as a data entry guy. I learned VBA because dealing with thousands of products in excel by hand was a pain in the ass. Among other things, I wrote a macro to combine multiple products into an importable Magento custom product. From there I learned HTML, CSS, JS, and PHP and never looked back.1
-
Just learned about the Linux watch command today. `watch -n 1 ls -l` OMG, where have you been all my life?3
-
My first series... now off to work. Let me know your thoughts and if I'm right... or way off
“What I Learned From Studying Algorithms and Data Structures (AlgoDS 1)”
https://medium.com/@allanx2000/...3 -
Sharing my first published blog post on medium entitled: "My First Competitive Programming: What I learned" https://medium.com/@youawesum/...
:) -
Lesson learned today :
Don't get lazy and muscle monkey hanging out your laundry..
Like your code, you'll eventually regret monkeying it.1 -
Managing a small team - poorly.
I was in charge of testing a legacy calculations engine together with two scientists, for whom I set up a python and interop environment so they could test the engine easily.
The two were very excited at the thought of validating the calculations and in fact found many bugs.
I was very supportive, told them to fix the bugs and gave them a pet on the back.
All three of us were happy the legacy engine is shaping up, that's until my boss heard of it, and boy did he grill me hard for it.
Turns out our efforts were highly unappreciated by the client, whose only request was that we test the engine and report the bugs. Not to fix them. My goodwill cost the company a lot of money, since the client paid by the hour, and was now due a refund. Crap.
It took me a year to finally understood the moral of the story. Which is to always respect the client's wishes and convey maximum transparency to him. -
After going through the regular process of talking to HR/Recruitment and passing the casual interview with a team-mate for cultural compatibility, I got the task of grilling a candidate on some technical matters. This being a PHP job, we got to talking about PSRs (PHP Standards Recommendations).
As he seemed to take pride in his knowledge of PSRs, I decided to focus more closely on that.
So we got to a recomendation regarding dependency injection containers. Nothing special, and he seemed to know his stuff. At that point, he made a statement that parts of that recommendation were a bit stupid.
Now, I hate to put people in their place, but his statement did not match what that specific PSR stated. So I gently tried to correct him. The candidate, being on fire thus far, pointed out that I should trust him on this, as he clearly knew his stuff.
Again, I didn't like having to do this, but I also did not like him having a misconception about a topic he was, otherwise, really on top of...
So I asked him to trust *me*, as I was one of the writers who contributed to the standard.
The true test here, of course, wasn't if he knew all the minutia of every standard but how he would react to being corrected.
We, as developers, are wrong all the time. Its how we learn and evolve. So being able to accept that is vital.
Sadly, he did not respond too well and sunk into a bit of a sullen silence. At first I though maybe I'd scared him or that he was afraid of having made a gaff but it soon turned out he genuinly did not like being wrong.
Sadly, I had to advise against hiring him.2 -
Always always always restart command prompt after changing path variables!
Learned this the hard way after struggling for like 2hrs1 -
Today I learned.
In php if you cast a string to array you get an array with one value: the string.
20 -
Went to college for 4 years learned very basics of everything. Started first job and just learned by doing, thank God for the Internet you can learn everything else you need from there.
-
Learnt a lesson today:
Never try out new hotkeys in a SQL query editor window.
Or if you do, at least make sure it's not connected to anything important :)
I was trying out new hotkeys and accidentally executed a SQL deploy script to rename something in multiple stored procedures in a large system.
Thankfully - so I saw after my heart stopped - it was only our QA db so not too bad, just a couple of devs set back.
Who woulda thought ctrl-l would execute :O -
I have just learned java language. Can anyone tell me some small projects that will help me as a beginner?10
-
Recently learned about this term... I'm going to be using this from now on.
http://urbandictionary.com/define.p...4 -
Oh, Ubisoft
Relying on your UShit cloud saves was a terrible mistake
20 hours of AC Origins and 9 hours of Far Cry 5 lost because I trusted your piece of shit service would do something right9 -
Windows used to run windows
Then Windows learned to run linux
Then windows learned to run android
// TODO learn to run macos
// TODO learn to run ios
Isn't windows becoming a Frankenstein?8 -
Anyone here here has used pluralsight? Really powerful platform for learning IT stuff, I have learned tons with it3
-
It reaaaally annoys me when my business logic is sound but the data is corrupted.
For example, find duplicates in a HashMap<String>.. but I didn't take into account the input could contain a space either before or after.. so I end up wondering: if a HashMap only contains unique keys, how come the count of items in the map is the same as the count of the input keys?! Well.. spaces were the culprit.
"12345" != "12345 ".. and therefore the Map sees it as two distinct keys..
What an annoying bug.
Lesson learned: 1) Sanitize input first and never trust it. 2) Never make assumptions16 -
I just learned a new error code: error 40, it means user error since they sit 40cm from the screen6
-
Started by seeing an example of script in Batch and trying to recreate it, then I learned HTML, some CSS and JS and made HTA programs, then a little Visual Basic because I liked the idea of desining your own GUI in Visual Studio so easily, then I started High School and forgot almost all I learned. Sad story...
-
I literally can't believe that your project even runs without this technology I just learned about yesterday
-
This month I learned that account confirmation via email is a hard thing to do for a lot of users.3
-
!rant
Any hololens or virtual reality / augmented reality developers here?
If so, mind sharing "lessons learned" experiences with VR / AR programming?3 -
Today I have practically learned the concept of geometric progression. A db table of 5 Gb now it's 500 Mb.3
-
* Create S3 Bucket
* Enable versioning
* Setup lifecycle to delete small temporary objects after 7 days
* Wait 7 years
* Say "Wow, I was fucking stupid, and I've learned a lot since then."
* Write devRant post
* Profit with lower monthly AWS bill1 -
Never ever again I start a project without fully declared technical requirements.
I coded a website with grav cms and they ported my beautiful work to shitty handmade coldfusion backend.1 -
Never realized how often I use rubber duck debugging until I learned there was a name for it ͡° ͜ʖ ͡°1
-
Just figured out "code map" and "code clones" on VS 2015 (don't ask me why I didn't know these features)
Thought I should try it on my newly created application for a client (+/- 1500 lines of code C#)
Came across 1 duplication, 0 unreferenced classes or members and no circular references
I'm just awesome -
I've just learned that I got admitted to MSc in Games (technology specialisation)! Holy shit, it's so good!2
-
Lesson learned when I started working: never try to proove yourself customers will just try to abuse it.1
-
First assignment after I learned about if-else-then and for loops: draw swastika with modifiable width variable2
-
Learned Actionscript in school as it was the language used to teach programming fundamentals to students...I actually enjoyed the syntax and the switch between flash and flash builder.
I feel like an idiot though because after I learned it I discovered no one uses Actionscript and I sort of disregarded what I learned and now I've forgotten how to use it and how to work within the environment :(4 -
When did you first learned about that under the share menu there is a save image for image rants? :)3
-
I was in Chemical Engineering and had a class about algorithms. The teacher barely knew about C but learned some basic programming. Afterwards I switched to Systems Engineering and learned Java. I feel old... xP
-
- Learned how to use Git properly;
- learning how to use SASS and building the stylesheet of this all by myself;
- Learned how to reuse my code all over the project;
- Made my first design pattern and ruleset to create and maintain a project. -
hello. i'm a software engineer with about 4 years of experience, worked with c++.
a couple of months ago i started learned web dev, and now i have learned html and css, next is js.
i'd like to ask advice what on how to proceed, what to learn next? should i learn or build something? follow tutorials?
thanks8 -
!rant
Just learned that Kotlin has extension properties to go along with its extension functions. Anything else I'm missing?1 -
I'm curious to know having learned and gotten comfortable with PHP. Is it actually on the decline?13
-
And I thought I knew a lot about practical git... But today I learned about fixup commits and autosquash. Awesome!
-
I have something ethnical controversal in the making. I learned to shut up about the project. That's how i learned people fear and hide a lot1
-
Learned to program by shutting myself in my dorm room with a Shareware Modula-2 compiler and a well-written tutorial.
-
just learned the hard way to always provide unambigious absolute (or relative, but with checking) paths to files....
-
What are your easy things learned hard way ?
(It could be related to dev or anything else in live)6 -
You may have learned the latest frontend framework, but in software engineering I'm Zach Hill, and you're a snare drum1
-
We had to choose a workshop class for middle school and I chose computing because I was already familiar with all the components, but the last year we learned QuickBasic so that's where I learned programming logic. Later in highschool we had a bit of Visual Basic and HTML. Then learned some C and Java in college.
The truth is that I never learned any language in-depth and I've been winging it with the basics for longer than I should. A good understanding of loops and control flow lets you get away with a lot of things. -
Lesson learned .. never use sailsjs
Magic data loss
Laggy as fuck (832ms)... php5 runs better than this(210ms)
memory leaks -
Me: * Not having fun writing hundreds of tests/assertions for an API *
Also me: * Submitting changes without running my tests *
Production: * BROKEN *
RUN YOUR EFFING TESTS EVEN IF THE CHANGES ARE SMALL OR STRAIGHTFORWARD OR SIMPLE OR WHATEVER -
Optics matter. You could be doing a shit job (as a developer), but if you keep up the good optics with the boss, agreeing to build a calculus app in the future, even though the multiplication api you are currently working on keeps throwing error, you'll look good.2
-
Learned just enough Groovy to call a Python script and pass args to it. I have no problem with that.
Top Tags
Weekly Rant
View