Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
So I just completed reading this book and it was pretty awesome. Can anyone recommend me similar books? Which are not language specific but cover computer science concepts & is fun to read.10
>dreams something good
>mom wakes me up
>yells at mom
>gets shouted back
>thinks of dream again
>was soo good
I need some suggestions for a funny wifi name.
Preferably something tech related, but funny is the main priority lol47
X: So, do you have any weaknesses?
Y: Yes, I'm very honest.
X: But I don't think that's a weakness
Y: I don't give a fuck what you think2
As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.
I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.
These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.
Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.
All I want to say is:
No time was lost.
This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.
Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.
One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.
You don't notice the things you take back from your failures, they slip back sticking to you, undetected.
You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.
You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.
You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.
Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.
Please, for the love of code...
Start and fail as many projects as you can.30
Birdy birdy in the sky.
Dropped a poppy in my eye.
I don't worry, I don't cry.
I am just fucking happy that cows don't fly
How to Prank someone on Windows:
1: Take screenshot of desktop with cursor on the side so its not visible.
2: Set it as wallpaper
3: Hide desktop icons and taskbar
4: Go to mouse settings and invert it
I introduced git with hope that our team gets better
I introduced trello in hope that our team get better
I introduced gitlab in hope our team gets better
I introduced scrum in hope our team gets better
I'm losing hope...17
99% of my bugs are fixed whilst I'm in the shower
Honestly, I should just get a waterproof computer and write code in there15
A client that owns a restaurant wanted me to develop a webapp for the restaurant with 15-20 pages and table reservation feature. He wanted to pay me with a "free" dinner in the restaurant.19