Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "perfection"
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
- Sleep 7h+ each night (you think you don't need it - but you do!)
- drink NO coffee (you've slept enough!)
- pair-up (you're not as good as you think)
- get a grasp on the problem (it's time will spent!)
- communicate constantly (you're not alonw especially)
- refactor just as much
- learn from you partner
- celebrate even small accomplishments (you need success!)
- go home and do something else (your pet project does not need more than 5hrs per week!)
- repeat (because repetition makes perfection!)20
"Let's do some pair programming! It will be fun!"
... Fuck no.
Either I start coding and you open a beer, or the other way around. And sure, I do not mind doing each other's code reviews. I respect your feedback.
But I can't look over your shoulder while you misspell keywords. When I write code, I search, try, debug and play at a high speed.
I'm an impressionist/surrealist writing messy passionate functions, breaking lots of things with broad paintbrush strokes before finishing it into detailed perfection. I remember all the places in the code I need to work on, and cover everything with tests.
You're a baroque coder, sometimes even a hyperrealist, with your two-finger 10 wpm typing, writing code strictly line-by-line, decorating every statement with the right checks & typehints in advance. You can not keep two functions in your head at the same time. You write tests reluctantly, but you hate that I barely plan. You plan everything, including your pee breaks.
As a coworker I respect you.
But there is no bigger hell than pair programming with you.14
curl cheat.sh — get an instant answer to any question on (almost) any programming language from the command line
do curl cht.sh/go/execute+external+program to see how to execute external program in go
And this question: why I actually should I start the browser, and the browser has to downloads tons of JS, CSS and HTML, render them thereafter, only to show me some small output,
some small text, number or even some plot. Why can't I do a trivial query from the command line
and instantly get what I want?
I decided to create some service that will work as I think such a service should work.
And that is how wttr.in was created.
Nowadays you probably know, how to check the weather from the command line, but if not:
(curl wetter in Paris if you want to know the weather in Paris)
After that several other services were created (the point was to check how good the console
can solve the task, so I tried to create services providing information
of various nature: text, numbers, plots, pseudo graphic etc.):
curl rate.sx/btc # to check exchange rate of any (crypto)currency
curl qrenco.de/google.com # to QRenco.de any text
And now last but not least, the gem in this collection: cheat.sh.
The original idea behind the service was just to deliver a various UNIX/Linux command line cheat sheets via curl. There are several beautiful community driven cheat sheet repositories such as tldr, but the problem is that to use them you have to install them first, and it is quite often that you have no time for it, you just want to quickly check some cheat sheet.
With cheat.sh you don't need to install anything, just do:
curl cheat.sh/tar (or whatever)
you will get a cheat sheet for this command (if such cheat sheet exists inf one of the most popular community-driven cheat sheet repositories; but it surely does).
But then I thought: why actually show only existing cheat sheets? Why not generate cheat sheets or better to say on the fly? And that is how the next major update of cheat.sh was created.
Now you can simply do:
and get your question answered
(cht.sh is an alias for cheat.sh).
And it does not matter what language have you used to ask the question. To be short, all pairs (human language => programming language) are supported.
One very important major advantage of console oriented interfaces is that they are easily
programmable and can be easily integrated with various systems.
For example, Vim and Emacs plugins were created by means of that you can
query the service directly from the editor so that you can just write your
questions in the buffer and convert them in code with a keystroke.
The service is of course far from the perfection,
there are plenty of things to be fixed and to be implemented,
but now you can see its contours and see the contours of this approach,
console oriented services.
The service (as well as the other mentioned above services) is opensource, its code is available here:
What do you think about this service?
What do you think about this approach?
Have you already heard about these services before?
Have you used them?
If yes, what do you like about them and what are you missing?26
Things I wish I could tell my 18 year old self.
1) Accept you will make mistakes.
2) Truly learn the language you are using.
3) Write idiomatic code for the language you are using.
4) Be upfront about not knowing something.
5) Don't let not knowing something stop you from learning it.
6) None of us knew X until we learned it.
7) Understand your strengths and weaknesses as a developer, play to them.
8) Be willing to try new things.
9) X language isn't ALWAYS the best choice, X paradigm isn't ALWAYS the best choice. Choose wisely.
10) You won't know everything, but you might know more than others.
11) Your ideas and ego don't matter more than ensuring the product works.
12) "Perfection is the enemy of the good [enough]" - Voltaire
13) "Perfection is not achieved when there's nothing more to add, but when there's nothing more to remove." - Einstein.
14) Conflicts happen, deal with it.
15) Develop a toolset and really learn them.
16) Try new tools, they may prove better than what you were using.
17) Don't manage your own memory unless you absolutely have to, you are probably not smarter than the collective intelligence of the team that built the various garbage collection methods.
18) People can be dicks, especially online.
19) If you are new and people are being dicks to you, did you skip past the irc message about etiquette? If you did, you're the dick in this situation.
20) It can be tough, but it is fun, so have fun!6
A few of Stux's !dev pet peeves
1) People that walk slow as fuck in the middle of a side walk. Like hurry uppppp. I've gotta get 0.5 miles in like 8 minutes and you blocking the walkway doesn't help.
2) People that don't understand how side walks work. Treat it like the fucking road. ⬇️⬆️ Is the pattern in which you should walk. It's not rocket science.
3) People that start walking up the bus steps as I'm clearly walking forward to get off. Ffs let me off and THEN get on you stupid bitch
4) people that bike or ride their skateboard/longboard around campus but are moving slower than I am while walking. If you're gonna do that hop the fuck off and carry the damn thing.
5) people that don't try to solve an issue with their code on their own BEFORE they call the professor over. (There goes the !dev lol)
6) people that act like their favorite musician or athelete or actor or anyone fucking famous they play kiss ass with can't be criticized. Just bc they're famous and/or good at what they do sure asf doesn't make them perfection and I retain the right to voice my opinion.
My name is Stuxnet and you're watching Disney Channel.14
Non dev related but: release my first track 😊
I'd love to create something which is near musical perfection for myself 😃
There's a couple of tracks which come close for me but not 99 percent yet.37
You refactor after there's code. You can't have clean code if there isn't code to be cleaned to begin with. Code first. Think of perfection later.5
Avicii died. 😞😢
At just 28.
He got me through some tough and grueling times. I still use his tunes while coding. I'm still shocked that he left so early. But he made it count. He might've lived short but he lived large.
I'll miss him. I'm sad that he left so early. But his work will live on. I hope to become as good at programming computers as he was at using them to make music. His music was perfection. RIP.13
Just got myself a shiny new MacBook 12".
It’s perfect. The pure perfection.
I got zero lags in every app I use. I type faster than on my mechanical keyboard. Everything is super smooth.
I’m never coming back to Elementary OS. I’m sorry tho, Elementary is great, but macOS is better.22
Linux 5.3.xx ? NO. TOO OLD
Linux 5.4 rcx ? NO. Better but still not perfect.
Linux Next ? NO. Still not it.
Linux Next + manually merging GPU and other stuff i need manually ? PERFECTION
3 in 1
If your project needs more than three sentences to describe and the budget is not in the high four digits or preferably five, then you're clearly not fucking paying enough
Clients that just write a "?" after you wrote a very detailed tutorial, which even a fucking skunk could do, if given a fucking mouse and keyboard, are just the fucking laboratory perfection made retards
I just LOVE IT when my internet drops out for under a minute, so windows doesn't notify you yet and your sftp client trashes both local and remote files
> Worst work culture you've experienced?
It's a tie between my first to employers.
First: A career's dead end.
Bosses hardly ever said the truth, suger-coated everything and told you just about anything to get what they wanted. E.g. a coworker of mine was sent on a business trip to another company. They had told him this is his big chance! He'd attend a project kick-off meeting, maybe become its lead permanently. When he got there, the other company was like "So you're the temporary first-level supporter? Great! Here's your headset".
And well, devs were worth nothing anyway. For every dev there were 2-3 "consultants" that wrote detailed specifications, including SQL statements and pseudocode. The dev's job was just to translate that to working code. Except for the two highest senior devs, who had perfect job security. They had cooked up a custom Ant-based build system, had forked several high-profile Java projects (e.g. Hibernate) and their code was purposely cryptic and convoluted.
You had no chance to make changes to their projects without involuntarily breaking half of it. And then you'd have to beg for a bit of their time. And doing something they didn't like? Forget it. After I suggested to introduce automated testing I was treated like a heretic. Well of course, that would have threatened their job security. Even managers had no power against them. If these two would quit half a dozen projects would simply be dead.
And finally, the pecking order. Juniors, like me back then, didn't get taught shit. We were just there for the work the seniors didn't want to do. When one of the senior devs had implemented a patch on the master branch, it was the junior's job to apply it to the other branches.
Second: A massive sweatshop, almost like a real-life caricature.
It was a big corporation. Managers acted like kings, always taking the best for themselves while leaving crumbs for the plebs (=devs, operators, etc). They had the spacious single offices, we had the open plan (so awesome for communication and teamwork! synergy effects!). When they got bored, they left meetings just like that. We... well don't even think about being late.
And of course most managers followed the "kiss up, kick down" principle. Boy, was I getting kicked because I dared to question a decision of my boss. He made my life so hard I got sick for a month, being close to burnout. The best part? I gave notice a month later, and _he_still_was_surprised_!
Plebs weren't allowed anything below perfection, bosses on the other hand... so, I got yelled at by some manager. Twice. For essentially nothing, things just bruised his fragile ego. My bosses response? "Oh he's just human". No, the plebs was expected to obey the powers that be. Something you didn't like? That just means your attitude needs adjustment. Like with the open plan offices: I criticized the noise and distraction. Well that's just my _opinion_, right? Anyone else is happily enjoying it! Why can't I just be like the others? And most people really had given up, working like on a production line.
The company itself, while big, was a big ball of small, isolated groups, sticking together by office politics. In your software you'd need to call a service made by a different team, sooner or later. Not documented, noone was ever willing to help. To actually get help, you needed to get your boss to talk to their boss. Then you'd have a chance at all.
Oh, and the red tape. Say you needed a simple cable. You know, like those for $2 on Amazon. You'd open a support ticket and a week later everyone involved had signed it off. Probably. Like your boss, the support's boss, the internal IT services' boss, and maybe some other poor sap who felt important. Or maybe not, because the justification for needing that cable wasn't specific enough. I mean, just imagine the potential damage if our employees owned a cable they shouldn't!
You know, after these two employers I actually needed therapy. Looking back now, hooooly shit... that's why I can't repeat often enough that we devs put up with way too much bullshit.3
That feeling when you see your deployed code running smoothly is probably more satisfying (almost orgasmic) than it should be...???1
And here's the thing: Trovalds is no superhuman being or something. Gates didn't do the impossible. They all had this "uh fuck that I may correct that later" moment.
Don't strive for perfection, do stuff outta passion my dudes and dudettes.5
//Kind of not a rant. IDK what it is.
Yeasterday i spent almost all day building a 3D printer to perfection. (TEVO Tarantula PRO)
By that i mean all axis are exactly 90 degress.
Not 90.1. 90.
And good lord it payed out.
IDK how they managed to make metal printer for 188Euro but well they did and it prints as good as PRUSA.
I started print after calibration and it is near perfection. Other then salmon skin effect which i will fix with new drivers TMC2208 ofcourse.
Now it will be really perfect printer. Oh and i can print BIG things now.
235x235x250mm is a lot.9
So at this startup i was single iOS dude age 34, android had 1.5 dudes, one older, one you ger. That 0.5 younger was tech director, really good, so they churned for two guys. Millenial, nice guy, never making conflict, just being sleazebag.
Nobody explained to boss why iOS was always late with features, even when i complained. So i got help, 10 months later, project was unpolished but stable, codewise. Now i interview and hire a guy, age 27, who was all yeah dude no problem, and that being my first interview, i fell under his friendly appearance. I ignored a fact that he didn’t know 90% of stuff i was asking him, because he was so friendly and outgoing and we will do anything attitude.
The guy knew very little, was childish and irresponisble. He showed at work at noon. He started telling me what to do, his senior collegue who started the project. He argued about everything that i would tell him. So i spent three to four hours a day charting with him, because we were in different cities. He had two uears of experence, but he was below junior level. And he refused any of my advices for learning in free time. No, he said, thats my free time, you will not tell me what to do. Well, how do you plan on being better, i asked. He said, i learn by doing. But, since he was at his job only six hours a day, instead of eight, and since he was productive only for 2, i guess he was lazy.
He would deliver a UI he would make, without business logic, and tell it is done. Then clients would call me and ask why text fields are not saved..
This all took me month to understand. I lost time, i lost trust, and soon he was fired.
But, soon i was fired also, replaced by another two devs who i had interviewd and formed a team. I was discarded as trash, just like that. I have even worked overtime to catch up with android guys, unpaid.
Took me year to recover mentally from this.
Lessons learned: be objective when interviewing. Job is business, not friendship, trust no one, keep neutral on work. Leave honesty for someone else, honesty will be used against you. Never criticize two girls in office who disturb developers by talking about sex and dicks all the time, dressed sexy, they are girlfriends of people ranked above you. Leave code perfection for your projects.3
Im coming for you.
I will bake you to the perfection.
And then without a piece of mercy i will eat you.8
Does anyone else have this neverending drive for perfection in their software? One that has consumed every personal project, causing rewrite after rewrite so it would finally be perfect. Only to realize that perfection is impossible you are the guy who just wasted his entire weekend and has yet to finish a single project.3
//If you dont own TEVO tarantula or 3D printer in general or are not looking into buying one the scroll past. But well if you want to read it go on.
So since some of you may have or may want to buy TEVO tarantula(3D printer for 300$ for those who dk).
I will put here a small list of upgrades that are just must do:
1. Part cooling fan.
I see a lot of people on Reddit and elsewhere with printing on tarantula without part cooling and the resoults are horrible tbh.
It takes 2 hours to print and the fan costs 2$ at most and the quality is 1000% better. Not kidding.
2. Second Z rod
I still wait for my second rod but i have hacked my printer kind of with second rod that's smooth and use that for now and the auto leveling gets precious as hell. And quality gets better too.
The acrylic brackets that come with it are shit to say the least. After printing part cooling get some wood board that's cheap and print brackets and screw the brackets into the wood. It makes the printer stable as fuck. No more weird sounds.
4. This is few upgrades that are not must but help a lot too.
Y and X belt tensioner. Belts are supposed to be tight on X and Y.
Big bed and autolevel. This is just a personal thing but its good to have it as you dont have to level the bed every time and you have bigger space to print on.
Oh yeah replace the green shitty sensor with BLtouch. Oh good 3D printer god is it much better.
Glass bed. I will just tell you to get mirror cut to exact bed size and clamp it on. Really helps a lot since that AL bed on tarantula isnt great.
E3D V6 extruder. One of the WOW upgrades here from my opinion. No plastic leaking anymore. Just perfection. Even the clones are good.
And dammit flash new version of Marlin on that printer. Oh boy is it much better.
With all this put on the printer. Sure its price goes up. But most parts are 3D printed its not much.
Most people i talked to who have tarantula dont upgrade it too much and thats a mistake. they cant go more then 40mm/s and i can do 70-90mm/s with still nice quality. But yeah i keep it at 70mm/s just cause its better.
And yes upgrading motor drivers to the ones on Prusa MK3 help a shit lot with lot of stuff i cant tell anything since i dont have them yet. 11$ per piece and i need 4 of them is kind of pricey.
I hope people will find this useful.7
The new iPhone is gonna have an odd number of pixels in width. I can already feel the anxiety of trying to achieve pixel perfection.7
Einstein supposedly has a quote attributed to him: "Perfection isn't achieved when there is nothing left to add, but when there is nothing left to remove."
I find that I aggressively refactor code where I can to only what is absolutely required. It does also have the knock on effect of reducing scope of bugs, when the code is smaller there's only so many places bugs can be.
Tesla claimed to have the ability to create designs in his head and only built things once he was satisfied that it worked in theory first, now it's rare I can do that, but I will use a repl to prototype or test modules in isolation before just hacking on the actual code.
Jobs, I mean, I know he didn't code but he was always insisting on designs that looked good and was generally uncompromising in his design centric view.
My friend, she was my Starbucks barista for a while but I've slowly been teaching her code and she's taught me a lot about how to teach others to code, she also happens to be my favourite student.3
AMD you have done amazing fucking job. 4.20 and gnome lagged a little sometimes.
4.21 mostly smooth as butter and when updating to GNOME 3.32 its just perfection. AMAZING.
Not only they did FreeSync and other amazing shit in kernel and mesa but now my Raven GPU can clock up to normal speeds as it wants and not only beign stuck at 400mhz core and 933mhz memory. Core is at 400mhz but its not used too much and memory clocks helps a fucking lot. When i hit it with load it goes up to normal clocks normally. AMAZING.
From a few years of programming experience, I come to know that "we cannot write perfect code."
What I mean by this is no matter how perfectly you write code, but if you have a peek on that code after about 3 months, you will be like, "I could have done a lot of things in a better way." Provided the code is atleast of 100 lines.
It has given me a great understanding of how important perfection is. At school everyone said, "you spend too much time perfecting everything" or "spread your* effort, rather than spending lots of time on one thing and rushing another." But now, in programming, knowing where to put the time and effort is the most useful skill I could ever need.
Also, I can barely use the mouse correctly anymore, except when playing video games.
*Here, my Google Keyboard suggested: legs, wings, Marmite. 😕1
1. Nothing lasts forever and you always need to be prepared for change.
That might be technology acquired by other company and dropped completely by all of people or new technology take over the market for a year and is gone after that and no one remember about it.
2. If you go opposite way then all of people around you that might be actually the best way.
That learned me to always look around for new stuff cause this small stuff that people make today can be big company next day just cause they got annoyed by things and start something new.
3. Trust nothing that you see.
Bugs are everywhere
4. Quality and speed doesn’t matter when you start doing something but consistency matters a lot.
When you start doing something you suck and you need to be ok with fact that you’re going to make lots of stupid mistakes and learn from them.
When you start new prototype you don’t need dozen tools to finish it, you don’t need performance or perfection, you need consistency to finish it.
"Sometimes I think about comments as a time machine that I use to send important messages to future me."
- Douglas Crookford
"I prefer to make the structure of my programs self-illuminating, eliminating the need for comments."
- Douglas Crookford
..come on Douglas, make up your mind!
"I'm not always successful, so while my programs are awaiting perfection, I'm writing comments."
Soooo i have just spent 4 hours "fixing" my 3D printer because my parts werent sticking to bed and fucking up.
I have cleaned the bed.
Leved the bed.
Replaced the nozzle.
Adjusted Unified Bed Leveling points to perfection.
Nope still not sticking. WHAT THE ABSOLUTE FUCK ?
OK OK maybe the temperature is wrong. Even tho thats unlikely.
Set it higher so better chance of sticking. (200C to 210C).
Still not sticking.
skgjnsdghdgj lhg s;lkhglkj sdg
OK you know what. I need this small cube done so i will just replace the filament for silver one.
Print sticks just perfectly no issue at all.
Wait. Nooooooooooooo. NO NO NO NO NO NO NO NO NO NOOOOOOOOOO NO.
It was filament the entire fucking time ? WTF ?
I have used the one that doesnt stick for month and no issues. WTF ?
You know what ? I dont care anymore.
I will just not buy that one anymore and fuck it.
Now looking at me 4 hours ago i should have tried different filament as second thing but oh well.
Now i know.
We learn from our mistakes after all.18
"But using XYX is better and it's not hard to set up!"
No, fuck you and your recommendations.
It's too time consuming to set up that blazing-fast minimalistic modular shit, because I know I'll want to configure it to perfection until I bang my head against my tiny keyboard when I have finally realised that all the config I went througu only achieved the same outcome as the 'bloated' software I was originally using.
So, fuck you.
I'd rather get on with my life and get some work done.
It's not like I wasn't aware of XYZ in the first place; I'm not using it because I know what's more important to get my shit done.2
Agency hires me to convert a 4 column + sidebar + pattern backgrounds email to responsive, for a big client, I make a redesign, simplifying it (less columns, flat...) to avoid issues, client insists, exactly the same design is needed.
I tell him its almost impossible but I will try, and try, and try, many times, but on their old Outlook, some email parts are not aligned (just that), try, and try, many hours, many days beyond budget... all the times since first explaining that perfection is not possible with all possible email clients, and like 7% is using outlook... At that point, and before, email was so well.
Finally I put an end to this, tell them to pay and leave me alone, as they didn't take my advises and warnings serious, not my fault.
This story is nothing until the discovery I made today: the agency had signed a contract with the client, a bank, in that contract there was the obligation to replicate exactly the same design and should be perfect in all email clients...3
When you spend more time renaming variables, class names, properties etc.. to achieve perfect code and patterns rather than actually solving the problem. I'm bored now...
Some common themes I have observed:
1. Why is this API using XML? It should be JSON.
2. Why are they using old shit? It should be new shit.
3. Why are they mixing new shit with old shit?
4. Why is the technology being used not fitting my sense of perfection and order?
What happens when JSON is the old shit? What happens when a new format is adopted that solves some corner case issues with JSON? What if those corner cases were solved by using XML, or a mix of XML and JSON? What happens when all the new shit is the old shit?
We will still be using the new old shit and listening to fucking noobs complain about mixing, matching, and abusing everything ever written. Oh JSON, how quaint and limited. Why did anyone ever use that? Fucking senior devs...10
Having an eye for detail and being annoyed by slight imperfections is extremely annoying at some times.
Yesterday I spent the evening setting up elementary os on my private laptop and I wanted to start coding a new personal project after setting up my IDE.
I ended up spending the evening trying to fix the font of my ZSH terminal which annoyed me so much but was absolutely not blocking any progress. Moral of the story: sometimes you just gotta let go3
Once again tried to switch from iOS to Android. I love the freedom and all but the problem is that the freedom ends just when you are about to reach perfection.
It's like having amazing sex and just when you are reaching an orgasm, your partner gets a headache and you have to finish by doing everything yourself.
So I'll continue with iOS - doing it in the dark missionary style. Not as exciting, but at least I know what I'm getting and somekind of satisfaction is guaranteed.4
Ugh, Why cannot I just make a simple module instead of deciding to include all the bells and whistles. Especially when it isn't even for that much money :(
My perfection is really annoying sometimes.2
I absolutely treasure the bug reports we get from users. Nothing helps bring the product closer to perfection than the informed critique of end-users.
Recently, however, this one dude is filing a new fucking report every time he encounters the same fucking bug. "X happens for operation Y on file A"
"X happens for operation Y on file B"
"X happens for operation Y on file Z"
Jumping Jesus Christ, man, I'm pretty sure we can identify a pattern after the first two!
I don't expect him to know about the work we do to reproduce a problem after one report but fucking hell, have some faith that we'll get the picture after two or three.
These are fully detailed bug reports too, so it's not like he's just being a troll.1
Ah I love that movie.. Hero, from 2002. I've seen it in the cinema three times. It's a real marvel, especially the scene where the forest turns red right after Snow killed Moon.
I also like how the quotes are adaptable:
Martial arts and programming are quite different, but they are based on the same principle: striving for highest perfection.
The essence of programming reveals itself through study and meditation.
(The latter one is also one of my favourite lines at work when being asked how come I know some esoteric stuff: it revealed itself through study and meditation.)5
I got inspired to make my code as closest to perfection as possible for me by my uncle. Seriously - he was real handyman.
Once he had an accident in his car (I think it was Škoda 100) because of the drunk pedestrian. The car engine was ruined, as like back of the car. He disassembled the car bolt by bolt (he was writing all the actions in his notebook). He then bought exact parts and paint (which wasn’t easy in 80’s Poland) and fixed the car alone in his garage.
Even tho everyone was telling him to give up, it will not work, etc. the car started at the first try and you couldn’t spot any damage. Even the paint on the body was matched 1:1.
This story inspires me to don’t give up and try to do my job as best as possible - even if everyone else says I can’t do it.
One of the great lessons I've learned in this career was to: "Stop rewriting up that code to perfection and start moving on to better things. Keep moving ahead. That code will be replaced and get messy again anyway."
But that doesn't mean you should write bad-designed or sloppy code.2
My coworker has been freaking out that our company doesn't do Agile or Scrum right and it will negatively impact his career. He claims that some elite company will want him to prove he worked in well oiled Agile machine. He also claims his last company had it down to a T yet he voluntarily left so they couldn't have been that damn spectacular.
I'm on my 7th company and no one does this shit "right", everyone makes it up. Also it's impossible to prove that you worked in a perfect environment to a different employer, if they even care at all. If someone asks, just tell them what they want to hear because no one actually works in this mythical world of Agile perfection.1
While trying to fall asleep, I came to the conclusion that a solution to privacy would be an encrypted p2p messenger. You'd need a dns-like system that can tell the peers how to contact their communication partners. Then I searched for one, and there was a good looking one, but it wasn't open source. looks secure otherwise, but perfection looks different.
Can anyone recommend something similar to kripter/tell me why it would be secure/insecure to use their service instead of, say, signal? Not that I truly NEED this, but I at least want to try it :)5
!rant Everybody blame guys for using different IDEs, languages, tools or libraries. But what we all have in common is the feeling of perfection, when you code a function of 30, 50, 100 or 200 lines of code and it runs without errors on the first run 😍1
Saw this quote and I felt like maybe it is not just me that needs to see this today :)
“Don't let perfection become procrastination. Do it now.” - Danielle LaPorte1
"When graphic designers got bored with the perfection offered by the newly arrived computers that could render artwork to within a tiny pixel, they rebelled by writing programmes that randomized individual letters and whole pages every time a printer processed them. A designer who didn’t like what a copywriter had delivered even set that text in illegible pictograms and icons." - Erik Spiekermann1
Had one of my spookiest meetings today. Mr git master still had the dailies in the calendar, but he's the scrum master without a scrum and I was the only one to join. Some bitter remarks alluded to the fight with my boss, but otherwise he was mostly going on about how we should build a docker container to automatically build our build system and how to achieve this perfection in his previous company they needed three month - while our current project is already due in December including testing. I don't know.. still - theoretically he seems to know his stuff, but in the end you have to compile shit and make it fly, or at least not let it drown to heavily.
Anyway, awkward silence setting in, when he's still talking on and my boss enters the meeting room. Some heavy sand in the works.
Should I rejoice like them?
For those of us OCD Sheldon Cooper types out there, programming can get very annoying.
For example, I want to do everything as efficient as possible but sometimes situations require "live with it" or "quick and dirty" solutions, which grinds my teeth because I'm not applying perfection in everything and a laid back attitude is against my personality, much like Sheldon. It's the same annoyance as when Penny knocks twice but not thrice at the door.
This sure is easier for brogrammers.5
Are there any Objective-C programmers out there? What's it like to program in? Does it combine the best parts of C and Smalltalk into the ultimate expression of programming language design? Or is it an unholy abomination?4
Is there actually a technology/framework/library everyone loves to use without saying "this should be like xxxx" or "they should have done it like xxxx" in a language?1
I usually review my code and if it doesn't look right it needs improving (even if it works). I hate when I see code that I know is flawed. My coding skills are weak but it's easy to spot crap code