So a friend of Mine asked me to check their Mail server because some emails got lost. Or had a funny signature.

Mails were sent from outlook so ok let's do this.

I go create a dummy account, and send/receive a few emails. All were coming in except one and some had a link appended. The link was randomly generated and was always some kind of referral.

Ok this this let's check the Mail Server.

Nothing.

Let's check the mail header. Nothing.

Face -> wall

Fml I want to cry.

Now I want to search for a pattern and write a script which sends a bunch of mails on my laptop.
Fuck this : no WLAN and no LAN Ports available. Fine let's hotspot the phone and send a few fucking mails.

Guess what? Fucking cockmagic, no funny mails appear!

At that moment I went out and was like chainsmoking 5 cigarettes.

BAM!

It hit me! A feeling like a unicorn vomiting rainbows all over my face.

I go check their firewall. Shit redirected all email ports from within the network to another server.

Yay nobody got credentials because nobody new it existed. Damn boy.

Hook on to the hostmachine power down the vm, start and hack yourself a root account before shit boots. Luckily I just forgot the credentials to a testvm some time ago so I know that shit. Lesson learned: fucking learn from your mistakes, might be useful sometimes!

Ok fucker what in the world are you doing.

Do some terminal magic and see that it listens on the email ports.

Holy cockriders of the galaxy.

Turns out their former it guy made a script which caught all mails from the server and injected all kind of bullshit and then sent them to real Webserver. And the reason why some mails weren't received was said guy was too dumb to implement Unicode and some mails just broke his script.

That fucker even implented an API to pull all those bullshit refs.

I know your name "Matthias" and I know where you live and what you've done... And to fuck you back for that misery I took your accounts and since you used the same fucking password for everything I took your mail, Facebook and steam account too.

Git gut shithead! You better get a lawyer

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!

Juniors are a fun bunch to work with.
Over confident, hero complex of that fresh graduate high, and then thrown in to the real world! Where there hopes and dreams are crushed in minutes when they see what monolithic applications really look like!!

But don't let that overwhelm you, your not going to be changing all of it any time soon, hell some of this code hasn't been touched in 5+ years and still works without fail.

Don't stress about the work load, you can only write 1 line of code at a time anyway, and hell, even seniors make mistakes.

The key about being able to manage this beast is simple, break it! Because the more you break it, the more you'll understand how a project is put together, for better or worse. Learn from the examples in front of you, and learn what not to do in the future 😎

But more importantly, plan your changes, whiteboard the high level logic of what it is you want to add, then whiteboard in the current codebase and determine where to slice this bitch up, then when it all looks well and good, take out your scalpel and slice and dice time.
Don't worry, your changes aren't going to production anytime soon, hell, you'll be lucky to get past the first pull request with this working 100% the first time, and that's a good thing, learn from tour short comings and improve your own knowledge for the next time!

A lite story about how i was hired at 16 years old.
Me at 11. Modifying HTML templates to create a sign up page for a game. Me at 14. Created some worthless websites in the past (at a training), barely knowing the structure of HTML.
Me at 15. Made my first website for a customer (using WordPress for the first time, didn't know how to use it before). The website was selling apartments, it was looking very good and went on the first place on SEO. Got my first money (100E).
Me at 16. Made some other WordPress websites for other customers (one of them still haven't paid, the website was made way back in 2015), so i shut down the website and replaced it with a text saying "This website is currently down until the customers pays the developer".
Me still at 16. A friend of my mom sent my CV to multiple companies, to work as a intern to learn more, and one of them accepted me for a interview (a well known and one of the best company with 30~ people)
Went to the interview, asked me about what i realized, what i can do, about my knowledges in others languages etc (forgot to mention that i love the computers from young age, so i was very good in them, specially at the age of 11), so they were happy about it and asked called me for another interview with the boss. Went to it, the boss asked me some tricky questions, i answered them immediately, he was very surprised about my knowledge at that age and accepted me immediately. After working for 2 weeks, instead of hiring me as a intern for 4-6 months, they instead hired me as a normal person, as a front end developer, for an undefined date, making 250 E / Month (6 hours per day in summer)
Now, I'm in the 11 grade, working for them about 9 months, making 315 E / Month, working for 4 hours per day after school, the place is cool, my entire team (family) is very funny and very cool, and they asked me many times to help them with different problems they had and i fixed them immediately (they really didn't know some stuff which i knew). Worked on big projects and worked on some from scratch by myself and they were very happy about how it went.

TLDR: was talented in computers (software), I'm a fast learner, barely knew about making websites, hired as a front end developer at 16 yr.

Btw, I'm in love with DevRant, I'm feeling like home everytime i visit this community :').

P.S. Sorry for my bad English and the mistakes i made.

alert("Thanks for reading my first rant!");

1) Give every challenge a try.
2) failure is always an option.
3) learn from your mistakes.

That you should always admit you make mistakes and learn from them, instead of acting like you know everything arrogantly.

I've found sites like Udemy/Khanacademy/Codecademy/Brilliant/Edx to be very useful — possibly more useful than expensive education.

But they still need:

1. Better correction/update mechanisms. Human teachers make mistakes and material gets outdated, and while online teachers are rectified faster than classroom teachers, the procedure is still not optimal. Knowledge should be a bit more like a verified wiki.

2. Some have great interactive coding environments, some have great videos, some have awesome texts, some have helpful communities. None has it all. In the end, I don't want to learn a new language by writing code in my browser. It could all be integrated/synced to the point where IDEs have plugins which are synced to online videos, with tests and exercises built in, up to a social network where you could send snippets for review and add reviews to other people's code.

3. Accreditation. Some platforms offer this against payment, but I think those platforms often feel very old school (pun intended), with fixed schedules, marks and enrollments. Self paced is a must.

4. Depth is important. Current online courses are often a bit introductory. We need more advanced courses about algorithms, theoretical computer science, code design, relational algebra, category theory, etc. I get that it's about supply/demand, but we will eventually need to have those topics covered.

I do believe that for CS, full online education will eventually win from the classroom — it's still in its infancy, but has more potential to grow into correct, modern education.

I just got called into my bosses office. Apparently I was too "direct" with one of my code reviews and now the other developer feels put down and demotivated. All I did was point out some areas of the code that could be cleaner and more efficient, if you can't handle that maybe you shouldn't be a developer. If you can't objectly look at your mistakes and learn from them you won't be very useful either.
I am not your mother, I don't care about your feelings!

I don't mind if you down vote my answers on stack-overflow. But unless you leave a better answer or a comment explaining why, you are a fucking troll and an asshole.

I MEAN, YOU SHOULD TAKE A BIG STEP BACK AND LITERALLY FUCK YOUR OWN FACE!!!!

You aren't helping me or others learn from our mistakes by showing us the better way.

Online tutorial pet peeves
————————————

My top 10 points of unsolicited ranting/advice to those making video tutorials:

1. Avoid lots of pauses, saying “umm” too much, or other unnecessary redundancy in speech (listen to yourself in a recording)

2. If I can’t understand you at 1.5 - 2x playback speed and you don’t already speak relatively quickly and clearly, I’m probably not going to watch for long (mumbling, inconsistent microphone volume, and background noise/music are frequent culprits)

3. It’s ok to make mistakes in a tutorial, so long as you also fix them in the tutorial (e.g., the code that is missing a semicolon that all of a sudden has one after it compiles correctly — but no mention of fixing it or the compiler error that would have been received the first time). With that said, it’s fine to fix mistakes pertinent to the topic being taught, but don’t make me watch you troubleshoot your non-relevant computer issues or problems created by your specific preferences (e.g., IDE functionality not working as expected when no specific IDE was prescribed for the tutorial)

4. Don’t make me wait on your slow computer to do something in silence—either teach me something while it’s working or edit the video to remove the lull

5. You knew you were recording your screen. Close your email, chat, and other applications that create notifications before recording. Or at least please don’t check them and respond while recording and not edit it out of the video

6. Stay on topic. I’m watching your video to learn about something specific. A little personality is good, but excessive tangents are often a waste of my time

7. [Specific to YouTube] Don’t block my view of important content with annotations (and ads, if within your control)

8. If you aren’t uploading quality HD recordings, enlarge your font! Don’t make me have to guess what character you typed

9. Have a game plan (i.e., objectives) before hitting the record button

10. Remember that it’s easier to rant and complain than to do something constructive. Thank you for spending your time making tutorial videos. It’s better for you to make videos and commit all my pet peeves listed above than to not make videos at all—don’t let one guy’s rant stop you from sharing your knowledge and experience (but if it helps you, you’re welcome—and you just might gain a new viewer!)

Rather than singling out one person, I wanna present what I see as incompetent/stupid/ignorant:
- no will to learn
- failure to follow the very specific instructions & later asking for help when they FUBR sth & not even knowing what they did to fuck up in the first place
- asking how to solve stuff, then ignoring the suggestions & doing sth totally against recommendations
- failure to remember most basic stuff, especially if not writing it down to look at later when needed
- failure to check logs & 'google' stuff before asking why something isn't working the way they want it
- after two weeks, asking me how feature xy works, mind you they coded it, not me
- asking me why they did something in a specific way - WTF, am I a mind reader?! Who designed that crap?! Me or you?!!
- being passive/aggressive & snarky when told to do something or being asked why isn't it done already
- not testing their shit properly
- not making backups when upgrading (production) servers
- not checking the input value, no validation.. even after many many debacles on production with null ref exceptions
- failure to admit they fucked up
- not learning from (their) mistakes

I had a huge epiphany on Friday... not all developers enjoy coding.

Discovered when they brought down 2 of our environments, well told them what was wrong with the changes in their code that caused the environments to break, gave them links directly to the file in the gitlab repo that needed to be updated, and...

They fucking went home. The change would’ve taken all of about 30-45 seconds to update and they fucking left.

This person’s team lead come storming in pissed off because her manager is furious about 2 environments going down and preventing everyone else from being able to deploy their changes.

We provide the exact same details to the team lead about what needs to be changed, and advise that her team member took off....

30 mins later, her manager is storming up to us (devops/sre) livid as hell.

Explain the situation for a third time... manager is like, why can’t you guys fix it?

Look here you dense motherfuckers, we can fix the code. We can be the plumbers that clean up your shit. But what value do you gain as a developer if you don’t understand how the systems work and you keep pushing shit in?

Made the changes, fixed the environments, done right? Wrong.

The original developer made more changes not knowing what would happen and thoroughly fucked the environments again.

This dumb-fucking dumpster fire of a dude then sends us a slack message. “It’s down again, can you fix it?”

Our manager steps in and tells us to send him a link to the logs and have him fix it himself!

Thank goodness we have a badass manager.

Send logs, send repo file links (again), and send line numbers in the logs to try and help just a bit more. Dude goes almost the whole day without fixing it, environments are down, other devs are pissed, we throw this dude to the wolves. His manager starts to head over and was about to talk with my team lead when our manager steps out of his office and tells him the in’s and out’s of the situation and that our job isn’t to play log parser/error fixer for the developers. This dude that’s breaking the environments needs to be the one to fix the issue and his team lead should be aware of the problems and should have been able to correct his errors before it ever came to us.

The amount of hand-holding we do is ridiculous.

(Disclaimer, this one guy making some mistakes doesn’t sound too bad, but this is actually a common occurrence for like 40% of all of our developers)

We literally have interns still in college running circles around some of our full time devs. I know I’m not a developer, but for anyone that’s new-ish to developing, when you see shit like that please don’t lose hope. Those ass-hats got into programming purely for a paycheck, not because of passion.

Stick with it and your greatness will know no bounds 👍

As for you craptastic dipstick lickers, FUCK YOU!!! Go back to school and learn how to give a damn.

Here is the problem.

We all make mistakes. It's part of our lives and we learn a lot from it.

But you motherfucker, acting like an all-knowing being amongst all the developers. You think no one knows better than you. You learned something 2 years ago and you think nothing has been updated after that.

You make a mistake, you accept it and learn from it. But if you think you know everything, stop asking me to review your code. Fuck you, cocksucker.

One thing I learned over the years is that even when you think you can't do something or don't have the strength to do it, you actually can.

People do nothing better than to make excuses for themselves or blame others for the things they did without even considering that they could have done something about it.

The brain is a powerful processor to the point that when you think you're sick constantly your body will react accordingly.

Thing is though. If you don't take the opportunities that present themselves or don't look for them you'll probably get nowhere to the point where it could lead to depression.

Sure enough failures and mistakes happen all the time, ardly anything will go right the first time possibly leading to becoming demotivated and sometimes even depression.

Why? Because you forgot to think "what can I improve the next time"

A co-worker of mine keeps going back to his project he's working on because the boss has something in mind but somehow fails to translate it to him. He never stops to think what the desired functionality is compared to what it should do or look like (UI/UX). Eventually he snaps blaming the boss that he had to change it a couple of times.

This has happened multiple times since I started my Internship to the point where it just starts to irritate me.

Of course it's not always your fault but there are plenty of cases where it is or where you could have prevented it.

Mistakes and failures make you stronger only if you want to learn from them.

Have a good day

- hold yourself accountable for your mistakes
- keep track your mistakes and learn from them
- put thought in what you do
- be organised
- become comfortable asking for and offering help
- realise that some problems have no universal solution
- don't just copy what others do, but also think for yourself
- learn to be patient

Worst advice about programming...
My discussion with my company sistem admin :
Me : you must always think that users are dumb and will make mistakes (like putting letters when db saves as number)
He : users must learn, if they make such mistakes its their fault.

My claim: I learned early in school to always assume that users are stupid and will always find bugs and exploits by coincidence. So protect your code from bad imput

By still having the balls to continue making mistakes and learn from them

The company I work for offered a Javascript Course/Training for every developer to enroll, which happens to take place on 3 days. In the description it was ensured to be for everyone, doesn't matter if you are an expert or beginner: there's something to learn for everyone.

The company described him as a top coacher in Austria and that he is overbooked for 2 years. High in demand indeed. "Has to be good", I thought. As a relatively average JS developer, there has to be something to learn for me.

Sitting here the second day, I fucking regret to join this shit. I have never seen such a bullshit in my lifetime. Why the fuck would you even book this man, he doesn't even understand basic concepts of software engineering. Just reading down the script, opening the script on one laptop and showcaseing it on the other. When someone asks a question, there's a 70% chance he doesn't know the answer. It takes this scumbag 30 fucking seconds to define a function; probably making spelling mistakes alongside.

I don't even want to know how much this dude will make from this "coaching". Hoped that it'd get better over time but I don't see an improvement. Contacting my boss that I'll leave this "training".

I fucked up.

In my career, colleagues always looked up to me to solve everything. From day 1.
Hell, I have nicknames; « The Dad », « Machine », « The Beard »... when I meet a new group of devs at the bar they use those nicknames even if I have no clue who they are.

Result? I'm not allowed to fail and even if I do and try to take responsibility, no one ever blame me.

They see me as a fucking zen programming monk, all wise, patient and kind.

Oh boy here we go. I screw things up all the time and can never let go the guilt since I'm not allowed to take responsibility of my mistakes.

Once again I wake up after a night of stress working, trying to overcome analysis paralysis. I'm late. Supposed to have meetings with some fucking PHDs, fueling my imposter syndrome.

Can't even learn anything in those conditions.

Fuck they should call me the fraud.

i had to do a project with someone who isnt that good at programming. but for her to learn programming, i wanted to let her do part of the code even though i could have done it myself. so she wrote some code after 2 days without me intervening. then i checked out the code and it was total crap. it was ugly asf, it could have been optimized a lot more and a lot of variables were unnecessary and to think that the code was just around 30 lines in 2 days! when its not that optimized, they deduct points from the final grade and having useless variables and functions can also be a negative thing to the professors' eyes.

in the end, i rewrote the code myself because i wanted it to be better. my grade also depends on that code so i shouldnt be ugly asf.

i recognize my mistakes too and sometimes my code isnt as optimized as it can possibly be but imagine her code is waaaay fucked up.

p.s. it didnt even compile

Oh how I like devrant everyday more and more- can you imagine if every job kind would have something like .this? (e.g waiter.Rant) this is so inspiring how everyone is opening up and speaking about motivation, inspiration, fails, mistakes. We are not perfect and we should learn from each other, so the message the devrant unconditionally says is 'be opened ' speak up . P.s this is like coffee for thinking, stimulates to not just sit and work but think and inspire Do something bigger and share , Move your thoughts thank you devs especially founders

"Learn from the mistakes of others. You can’t live long enough to make them all yourself. " - Eleanor Roosevelt

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.

Good luck

I'm getting beat up pretty bad by Rust. I like it so far but man is it hard. Imposter-syndrome is almost making me lose motivation. Almost, but I won't quit, one day I'll get there.

I think the primary reason I think I'm having such a hard time is that I'm trying to learn stuff that prevents me from making some mistakes that I have never run into. I know a bit of the theory but no hand's on experience on double-free errors, memory leaks and weird low-level stuff. I read the documentation, mostly understand what stuff is for but when I go write code I'm just like "now what?". I don't have enough experience to know when and where to use some concepts and I'm super lost. I don't know where to start and the feeling of being completely overwhelmed by all sorts of new stuff is at the same time exciting and frightening.

I have never, as a programmer, thought something was hard. All of my past knowledge required dedication, work and patience, but I wouldn't say I ever felt something was *hard*. But Rust... damn. Rust is hard.

Hopefully at the end of this super steep learning curve I'll know a lot more stuff and have stronger "dev powers" and be one step closer to being as knowledgeable as some of you guys around here to whom I look up to.

Today a task was assigned to a coworker, he is a good guy, but one of those that never complain, never say anything, get there early, go to lunch at the exact same hour everyday, doesnt talk to anybody and gets off at exactly 6pm.

So, the task was submitted by QA, according to them, a disabled input could be enabled by going into the dev tools and enabling it...

So i went over the pm and told her (cos she is a cunt) that the ticket was just bullshit and that first of all, we had no control of it, but if that is the case, we can go over and add event listeners to all the inputs in the platform to avoid people changing them...like wtf?

Since she is a dumb cunt, she 'escalated' the task to the senior dev... he is also a total fucktard who doesnt know a shit. The dude said that the task was ok and we had to do it or not but it was better to do it, justifying the ticket in the most stupid and incoherent way... like wtf is to do with it? Tell the user to not go over the devtools and enable it? The fuckkkk

I felt like i was about to shit my kidney, seriously, but what can i do? It is not the first time things like that happen. The stupid fuck also let one of his friends add several migrations to change several tables columns just because of 'good practices' which in first place left the databas all fucked up and with fucked relations.

I'm just so tired of these fucks, incompetent motherfuckers... I told a friend about it and he said that that was nothing, it is worse when you have to work for banks and that the only thing i could do was to let it go and learn from it, to not do the same mistakes. Im thinking in quitting... what should i do?

Don't. Especially while you're not a senior specialist. It doesn't really matter bad company or good: they all have something bad, they all have something good. From the bad examples you will learn WHAT, HOW and *WHY* should not be done. From the good examples you will learn what and why works and how efficiently.

Next month I'm gonna be working on a project that is SO bad I will flood DR with rants. But I'm looking forward to it, because I know I will learn what else should not be done.

Better learn from their mistakes than your own

How do I help my colleague in fighting harrassment?
This is the story of a helpless employee facing everyday harassment. Im trying to help. Seeking for your thoughts

Backstory fast forwarded: My company acquired another company. So we handle all their projects and clients now, but its a completely new domain. So we needed new people. Hired 4 employees + 1 team lead to start with. But the project process got delayed and they were free for a month. So i took 2 of them in my project and gave them some small tasks to help us over. They loved working with my team and were learning new stuff apart from what they usually did. And we were also happy of their contribution. We became good friends. All of this was in March 2020 before covid-19 was taken seriously.

About my company: I love this company. I have been in this company for more than 4 years now. People are really nice. Parties and fun events. Lot of smart and ambitious people. So company and people are awesome.

Coming back to the story. Lets call the team the 4 and team lead T. The 4 were happy that someone like T was in their team. This T had all the best knowledge about stuff and life was going to be awesome for the 4. Or was it?

Story starts: So I talk to one of these 4 on daily basis. Lets call this friend F. F is a real gentle person. Intelligent and dedicated to work. F is awesome to work with. And always enjoyed working. F is a team player and very very soft person. F is fking workoholic. So few days after project starts, F tells me work was not going well. F is getting real frustrated at work and not able to deal with it or find solution.

What happened:
This person T, who was supposed to help these 4, is real piece of shit. He is impatient, arrogant and MFing dick head. Aaaarggggg.
All the good qualities of a leader like supporting the team, boosting confidence, guiding team when they make mistakes, teaching them, were all missing from this person. T was a machine with no emotion and only clock working jerk. I have no idea how T cleared interview process, because one of the interview round is also about cultural fit into company. I know this because i take interviews for other domains. We have rejected lot of such well qualified but arrogant candidates.

So whats the problem now: this team of 4 are learning new tools and taking over the clients requests from old company. Most of the stuff is new for them. So in tat case people need lot of time to understand and figure out shit. people make mistakes while learning and you know have to deal with it. Person T abuses these 4 when something goes wrong. That's one.

Second, the T definitely knows more than these 4. So if these guys dont understand certain stuff they ask T. But T does not help them learn. T will either say busy or run away by saying thats simple and ull know when time comes. REALLY MF???

Third, T does not talk nice. T is rude and does not listen to team members. For eg, If F says some task cannot be done for some reason T will say, "y cant u do it? U r capable of doing it. Tats y u r in this job". And then point number one and two happens. Never responds to emails and messages. But if someone else does the same will not tolerate that and abuses them. List goes on.

So y not escalate and deal with that T:
This person F and other 3 are still under probation and they think complaint or escalation will back fire. These people do not want to lose job in between all this pandemic shit. They are scared.

So this was happening for a while. And i was giving lot of tips on how to handle certain situations. And how one should communicate these.

But being a gentle, soft and workoholic person, F focussed on work and assumed things will get in place as time goes by.

Today, F could not meet a requirement. So T told some shit which got F all sad. and F called up me late night and started crying explaining what happened. I felt real bad. I asked F to file harrassment case. F refused saying it was F's mistake on not completing requirement. WHO THE FK CARES. PEOPLE CANNOT TALK SHIT. I told ill file harrassment case against T. (We have a policy where others can also file if person is not courageous enough). But F did not allow me.

Then after calming down, I told F that telling the problems to me wont solve them. You have to talk to T directly and tell him on face not to talk like this. Or tell the manager about whats happening. Or tell the the HR about this. F said tat cant be done. I was like Y THE FK NOT.

Because the other 3 are not ready to talk about this to anyone as they fear they'll lose job. So if F talks and people question other 3 they might bail out. WAT THE HOLY SPIRIT.

so after lot of convincing F is still not going to
Talk to anyone about this.

So i have decided ill write an anonymous email to HR, the manager and other senior people in the organisation about whats happening.

I really dont know how itll go. Ill keep updating you guys. Feel free to share ur thoughts.

Today I had a casual chat with my friend and we were discussing how human mind limits the things one can achieve. Like giving up after constant failures, or lack of determination, blaming destiny for failures. I told him I am never easy about the fact that your destiny is pre-written and you can't do anything about it. If you are willing, you can change it. You just need to have the right mindset.
He said I am going to do MBA after engineering. You can't be rich with just engineering. I told him if you work smart and hard enough, and just follow your passion, there is no need for an MBA. And he went on to tell me how top richest persons mostly comprise of businessmen.

I fear for the future. People like this with no goals when take up engineering, they blame everyone but themselves and the stream gets the bad name. People want money, but they don't want to work from the beginning. Even after that they give up too easy.

People like Bill and Mark were not pre-destined. They made themselves. They were just like us, but they never got satisfied with themselves. We all have the capabilities to be them or even better. We just need to keep driving ourselves until we reach there, we don't have to get satisfied. We have to keep improving and learn from our mistakes, then try again.

Remember my friends

Fuck 2019. I still have one photo of 1/1/2019 on my instagram profile as my first photo with hopes to achieve what i was planning to achieve. But life happened. Things went wrong. Murphy's fucking law took over. Fuck you

Start fresh 2020. Learn from the mistakes. Expect more mistakes because they are inevitable. But do your best to NOT repeat the old ones.

We are going into the new decade. No more 201X year.

-Delete all negative energy
-Cleanse all BULLSHIT
-Remove everything weighting you down
-DETACH FROM THE PARASITE PEOPLE
-Stay with the real people
-Stay with family

2 more weeks until 2020

🙏🙏🙏

Don't be afraid to make mistakes. Making mistakes is the only way to learn from them and grow. F*ck sh*t up and build it back up again but better. Fall seven times stand up 8!

Interviewer at Google: How did you come across this open position?

Candidate: I saw a student's post on LinkedIn where he got rejected in the first interview. I am active on LinkedIn so that I can learn from others' mistakes.

Interviewer: I will give you a chance to learn from your mistake. Please apply to Microsoft.

I'm working on a codebase that is terminally ill. It's split so badly into microservices that no matter what you do, every one of them talks to every one of them over and over. If there's any way they can avoid just invoking a method on a class and send themselves a message or make an HTTP request, they'll do it. One of the services just sends messages to itself for no apparent reason. Except it doesn't even send messages to itself. It sends an HTTP request to a controller in another app, and that controller sends a message which is received by the same class that made the request.

The point is that this application is screwed. The defects pile up and there is literally no one who can understand what it's supposed to do in any scenario. I'm good at this. I can follow confusing code and document it. But not this one. It's overwhelming. It's insanity.

When these defects come in we're told to just run the app from the UI, see what HTTP requests it makes, and start tracing the code manually. Running and debugging it locally would be a nightmare but it's impossible anyway.

They decided that we all need to understand the application better so we can work on it, so we were each given six poorly-define five-hour tasks to "understand" various things. Those things don't make any sense. It's like if someone gave you the source code to Excel and told you to spent five hours understanding columns, five more understanding rows, and five more understanding cells.

Here's the thing: I'm okay with learning and understanding some code. It's part of the job. But I'm not going to abandon my career as a software developer so I can become an expert on debugging their awful code. I didn't make this mess. I'm not going to live with it. I'm moving on as quickly as I possibly can.

I've tried to explain to them that if they want the situation to improve they need to improve the code. They need to learn how to write tests. If your plan is that people will study your code, know it inside and out, and then spend all their time debugging it, that's a plan for failure. Everyone who can will leave and take what they know with them.

These companies just don't get it. They need their software to work, but the types of developers who can help them don't need that software to work. No one capable of doing good work is going to spend several years debugging their awful code unless you pay them a crazy ton of money.

Just don't make a mess in the first place. Hire developers who can do a good job. If you hire the cheapest people you can find you won't be able to get someone else to fix it later. It's not personal but I wish failure on those projects or even those companies. I want them to fail because failure is so expensive. I want them to fail so that others learn from it and don't repeat the same mistakes.

As an industry we're a bunch of genuine idiots. We just keep doing the same things over and over again no matter how much it hurts.

Intel 8085 micro-processor, anyone?

In my graduation, one of the semesters had Intel 8085 programming in the curriculum. It's because of that dev-kit I understood what assembly-level language means.

A simple scenario of adding two numbers would result in half a page long sequence of commands that literally didn't excuse any mistakes.

It made me understand the semantics or basically what we get taught as "middle level" languages.
We had to memorize the exact pins of the thing and had to draw it from memory. And we had to learn the instruction set it had.

Later we had to learn Intel 8086 but its instruction set was way too complicated and I gave up on it.

I know it sounds geeky but I randomly remembered it today.

My parents didn't mind. Since childhood, they used to tell me that I can choose my profession freely. I tried with medicine. Burned lots of €s and lots of time. And then switched to IT. Parents did not get in my way - on the contrary, helped me wherever they could. And allowed me to shoot my own foot whenever I was so stupidly determined to.

I believe it's the best kind of parenting -- allowing your children to make their choices, their own mistakes and learn from them while suggesting a piece of advice along the way.

I'm so sick of "senior/lead" developers pretending they know how to write tests and ending up with these unmaintainable test suites, full of repetitions and incomprehensible assertions.

You should take some time to learn from your mistakes instead of just continuing to write the same shitty tests as usual!!!

Every time I arrive at a new team I spend weeks just trying to understand the test suites for what should be fairly SIMPLE applications!

UNIT TESTS SHOULD TEST UNITS OF CODE!
If your unit test tests seem to be repetitive, they are not unit tests. Repetition is expected in integration tests, but that is why those are usually DATA DRIVEN tests!!!

After hiring a guy to work on a project for the clients and after 3 months when the project was done i asked him how was his experience working on this project and to just tell me honestly cause i would like to learn from my mistakes if there are any and improve. In summary he replied that he enjoyed the project and is satisfied with the overall experience. I was happy to read that. Then i read that again and something clicked in my head. I realized that response was kind of "way too generic". So i copy pasted it into google and found a link "Answer project manager interview questions like a pro" and on that site was written an exact sentence he wrote

😐

I've spent so many years not coding, I could never get over the initial hump, which was definitely a mistake. Mistakes are fine, we all make them. The best thing is to learn from them. On the plus side I've learnt firewalls, Web hosting. Windows domains, Azure cloud, virtual machines etc etc, skills which are hopefully very useful for Dev to have. I look forward to joining the ranks of skilled developers. If you are interested in development but are afraid to take the leap. Just go for it, start to learn and play with it. My recommendation for anyone looking for a starting point is a Udemy course called "The Complete ASP.NET MVC 5 course". I'm not affiliated in any way or advertising it. I just think it's brilliant and you get to the fun stuff really quick. You will start with the basics of getting and setting up visual studio. Also. If anyone could recommend other very good courses they know of I would appreciate it

Its time to remind ourselves the wonderful time of the year, where people look back and decide to be better and learn from your mistakes...

For example never test in prod and wake me up with notifications you dumbfucks... Someone has exams to do..

Seriously, I have seen a lot of push notifications lately, its some kind of Letstestinprod-uary?

very interesting how uni stressed me tf out but is still better than school has been.
I'm taking a class which has a theoretical and practical part, and there is a guy leading the practical lesson. and after struggling to find motivation for studying, this class somehow probably gives me my hopes back... even though I'm way less capable than the rest in what we're doing, I still can follow everything, which is very suprising to me because I'm always behind and the class has some recommended classes I should've taken before (but I failed some or didn't take them at all)... I still can follow the class somehow?

so... school taught me to not ask question because even if they say there are no dumb questions... the possibility still existed that I could ask a dumb question (shoutout to my math teacher in 3rd class). so... I stopped and when I didn't understand something I gave up.

now... this class makes me feel differently, I can ask questions and the guy I've talked about talks to me normally, talks to me as human beings should talk with each other and doesn't judge me for making a mistake, because... mistakes are human and when I allow myself to ask questions I can learn from it.

this is really a weird epiphany I had this week

and I also don't know if anything of this makes sense

Have u guys ever wonder, all those devs we rant about (mostly senior developer), how it feels like to be them? Today I realized, I am most probably becoming like one.
I joined devops 7 month back(around one and half year in industry). Right now, I am 2nd senior member in project. I have done deployment on multiple environments more than 100 times. But till today, I never knew how the deployment is being done. I knew to trigger job but I never knew how it worked. Today when a junior asked me, then I learn ansible, then I understand whole deployment process.(and remember I am 2nd senior most with 7 month in project)
Sometime I wonder, till now I always had good rating and most responsible title. But how much is that because of my technical knowledge? Sometime it feels like I have very good luck. But man, it's very depressing. Sometime it feels like my junior don't get enough limelight because I am in their way although they have good knowledge but they lack the though process for now. Most of the time my senior present me as role model to juniors, and it's very embarrassing for me(this will not continue on as I talked to my seniors) . I did work on good projects from time I joined company. And never had any issue and always deliver what needed. But I still can't write code in Java to take input or do for each on array in javascript without seeing stackoverflow once.
Now I fear that someday I will write piece shit of code and whole efficiency of project will go down cause of me. Atleast, the person who will get to fix it will get a chance to have good rant here. I tried open source projects to understand how to write good code but I always have hard time understanding new-projects which I never worked on.
Then there is reputation on Indian devs. This is my another Fear. That someday cause of me, my fellow devs will get bad reputation as well.
This coming year, my goal is to fill up all the holes but I don't know why my fingers are crossed.
Sorry, I had to bring this out somewhere. And please ignore my grammatical mistakes.

"Smart people learn from their mistakes. But the real sharp ones learn from the mistakes of others." - Brandon Mull

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state

... worst drunk coding experience?
none. or to be more precise, all of the three of them I had. I can't code drunk, i hate doing it, i hatw even thinking about doing it when drunk.

so after those initial three attempts i don't try to do it again, ever.

BUT, best coding experience while high?
ALL OF THEM.
some of the best pieces of code I wrote i did when I was high. my mind goes into overdrive at those times, and my thinking is not lines/threads of thought, but TREES of thought, branching and branching, all nodes of each layer of the tree coming to me AT ONCE, one packet == whole layer across all of the branches.

and the best was when one day, in about 14 hour marathon of coding while high, i wrote from scratch a whole vertical slice of my AI system that i've been toying around in my head for several years prior, and I had all of the high-level concepts ALMOST down, but could never specify them into concrete implementations.

and I do mean MY ai system, my own design, from the ground up, mixing principles of neural networks and neuropsychology/human brain that I still haven't seen even mentioned anywhere.

autonomous game ai which percieves and explores its environment and tools within it via code reflection, remembers and learns, uses tools, makes decisions for itself for its own well-being.

in the end, i had a testbed with person, zombie and shotgun.
all they had pre-defined in their brains were concepts of hunger and health. nothing more.

upon launching it, zombie realized it wants to feed, approached oblivious person, and started eating it.

at which point, purely out of how the system worked, person realized: "this hurts, the hurt is caused by zombie, therefore i hate zombie, therefore i want to hurt it", then looked around, saw the shotgun, inspected its class by reflection, realized "this can hurt stuff", picked the shotgun up, and shot the zombie.

remembered all of that, and upon seeing another zombie, shot it immediately.

it was a complete system, all it needed to become full-fledged thing was adding more concepts and usable objects, and it would automatically be able to create complex multi-stage, multi-element plans to achieve its goals/needs/wants and execute them. and the system was designed in such a way that by just adding a dictionary of natural language words for the concept objects on top of it, it should have been able to generate (crude but functional) english sentences to "talk" about its memories, explain what happened when, how it reacted, what it did and why, just by exploring the memory graph the same way as when it was doing its decision process... and by reversing the function, it should have been able to recieve (crude) english sentences that would make it learn what happened somewhere else in the gameworld to someone else, how to use stuff and tell it what to do, as in, actually transfer actual actionable usable knowledge to it...

it felt amazing to code for 14 hours straight, with no testruns during that, run it for the first time after those 14 hours, and see that happen.

and it did, i swear! while i was coding, i was routinely just realizing typos and mistakes i did 5-20 minutes ago, 4 files/classes ago! the kind you (and i) usually notice only when you try to run the thing and it bugs out.

it was a transcendental experience.

and then, two days later, i don't remember anymore what happened, but i lost all of that code.

and since then, i never mustered enough strength and resolve to try and write the whole thing again.

... that was like 4 years ago.
i hope that miracle will happen again one day...

From now on -and until further notice- I'll commit heinous crimes against each and any developer blaming GPT when their code is BAD.

YOU are in the workforce. Not GPT. YOU are responsible for the shit you write.
There is a reason GPT costs 200 bucks per month and you cost at least ten times as much. Own your mistakes, learn to code while you still have time, before the chatbot actually catches up and makes you obsolete.

Sincerely signed: the guy who straight up refuses to install copilot. I'm perfectly capable of introducing my own fair share of bugs, without relying on some autocomplete plugin.

When did you scrap your project and start over, and why?

I'm working on a second project at my company.

But as the project got longer and initially unplanned features started to pile up, the software has become a total mess and a pile of conversion layers for all sorts of I/O.

I'm starting to believe that it'd be better to learn from our mistakes and start over with a better plan, if it means we'll be able to achieve performance and stability improvements.

So, what was it like scrapping your project and starting over?

Some days I hate my work - other days I love it. Usually what happens is I make some poor decision that I have to live with and get super angry with myself, feel my colleagues are disappointed, go home, feel sad, sleep, go back, talk to them about it and try to learn from my mistakes - and then I'm back at loving work. Repeat. Software development is so much more than writing code.

My work doesn't stress me, what stress me are developers that doesn't learn from their mistakes

So this is something that happened in the first year at college.
I was at one of the top 50 engineering colleges in my country. To get admission here one needs to get a good score in the qualifying exams.
Now we had a cs related course in the first year which covered basic programming and coding concepts.
So in the first practical session we had to just write a hello world program in C.
The guy next to me for this session was the class topper who had secured the highest marks in the qualifying exams.
Now, as most of us know that program has a line that is:
printf("Hello World!"); or a variant of this.
This guy gets stuck while writing this line, so I ask him if I can help him.
He turns to me and said, " Man, I'm trying to get this comma to go up but it's not working"
Extremely confused I look at his terminal, only to realize that he was pressing shift+, and trying to get the " sign.
That guy went on to finish with a 4.0 gpa and is currently doing his masters.
Although hilarious, this serves as a very good lesson to all the beginners out here.
If you learn from your mistakes and improve you can definitely succeed in your life!
Just remember to actually look at the full keyboard though!

What's devrant's opinion on WordPress blogs?

I've wanted to start a blog for a while to share what I know and learn from others who read and want to correct my mistakes on the blog. But as of now my own site is barely held together and nowhere near ready to host a blog. So while I continue learning and building my skills to eventually make my site more reflective of my abilities I'm considering starting WordPress blog to just start now rather than continue the 'eventually' trend I've been following while working on my site.

Shit!!!!
Worst question I have seen around here.
I only had, at the moment, 3:
The first one was... unsignificant. Never learn anything important/relevant from him.

The second one didn't payed me for three months. I had to quit.
Still waiting for him to pay....... just being ironic his not going to pay.

The third one is bipolar and... well I already had stories shared here...so you can have a look.

I could say that I had another one. Is was my Father... best man in the world. My hereo. Learn the best things with him: Honesty, loyalty and Hardwork.

Sorry from any kind of mistakes on my writting. Long day and long night.

It's okay to slow down. Seriously it's fine. You can write 203 wpm... as long as the command you enter includes all necessary limits. Nothing is worse than having ansible rm -r the wrong directory or the wrong server because you missed a limit and put all.

I'm currently having a problems sleeping my inner philosopher just keeps thinking about various things. I wanna try to write some of them down as an simply to see what will happen.

I'll write my opinion down as honest as possible so feel free to disagree, but point out what I should rethink, if you want me to consider it.

To me respect has to be earned. I think especially on the internet many people try to skip this crucial step when they try to get respect. Most often when they want an opinion or their ideals to be respected. Most of the time it doesn't even feel like they want to be respected, but rather accepted.

There's nothing wrong with accepted in my opinion, but there are several approaches to get to this point and I despise some of them.

Earning acceptance by earning respect is one of the right ways to do it. Working hard towards your goals, showing your individual strength, standing behind your ideals. These are things I can respect.

I should also mention that these Ideals should be concrete, based on rational thought and a general good will or you will just twist my words to say that I support e.g. IS, Stalin's politics ect.

On a side node, I think it'd be wrong to disrespect everything Stalin did, since, from an economical point of view, he pushed Russia forward by quite a bit.

Then on the other side I see crybabies. People who want to be accepted, without putting effort in their ideals. Most of the time not even aiming for acceptance through respect, but through pity. Honestly, that's all they're going to get from me.

Pity, for their petty ideals.

Basically all I ever see these people doing is attention whoring and practicing multiple deadly sins at once.

Wrath, jealousy, sloth, pride, greed and optionally also gluttony.

Lust is rather a separate package. When I think about it, I link it mostly to horny teens and "send bob and vegane" type of stuff.
Gluttony being powered by sloth or vice versa, enhancing it.

The clear image I have in mind, while I write about this packages of deadly sins however, is that of a jealous person, complaining / getting angry about something they could change change themselves, but want them to be changed for them. Mostly through social networks such as Facebook, Twitter and whatever the fuck Tumblr is supposed to be.

"I wanna be rich, why is <person> richt but I'm not? This world is so unfair 😡". Have you tried working towards becoming rich?

"I don't don't feel pretty. Accept me". Accept yourself. Done.

"I don't like <person or organization>'s doing". If that's the whole message, all you probably did so far is complaining or crying. Sweet tears.

Stuff like that can happen to any person, just like any person makes mistakes.
Mistakes are made to learn from them. If you realize realize and accept your mistakes others may do so as well and forgive you.

But we are he towards this idiotic trend where people just can swallow their pride even for microscopic things. They instead push their pride to higher levels of ignorance, blaming other people, l(ying)mfao, creating black holes of density in the process. Makes me wonder whether their real motive is an inside bet on who can get the most people to kill them selves by face palming.

Most of my life I have been fairly protected against these people, besides some spikes of incompetence, but recently the have invaded 2 areas in my world that make the world somewhat less of a pain. Programming and the internet culture.

Yes, I'm talking about that master / slave BS renaming and article 11 and 13.

The remaking itself isn't really the problem, but rather the context. This was basically a show of power for the self proclaimed "social justice warriors" or SJW for short.

The fact that this madness has spread. That's what worries me. To me it feels like the first zombie has spawned.

Then we have this corrupted piece of incompetent shit, called Axel Voss, and other old farts.

They live in a galaxy far away from reality, somewhere in the European Parlament, making laws they don't know shit about, regulating things they know shit about.

All in the name of the people of the EU of course. And by people we obviously talk about the money.

I can honestly not think of another reason, after reading the replies Voss and his party gave on Twitter regarding the shit they pulled off.
Well, at least none that doesn't involve some firm of brain death.

For now I'll show them as much as possible how much I despise / reject them. Currently playing with the thought of some kind (social media?) website were posts from other sites or actions in general can be rated only with "Fuck you"s.
Given these articles, I should not have them hosted in an European country though 😅.

Almost hitting that 5k character limit 😰

So when i was playing saxophone, I realized that music and coding are just the same. When you get a new score to play you need to start over by learning how to play it. When you code and start a new project you need to start from zero. When you play the score over and over you learn from your mistakes. When you code you debug your faults when there is something wrong in your code. At the exam you need to make no faults when you play music. When you’re at the deadline. There shouldn't be no faults in your code

I'm sure like a lot of Devs of my generation, CS education didn't really exist when I was at school. All my knowledge has been self taught over time.

I think the best thing you can have is a good mentor and the opportunity to learn from your mistakes.

So I currently work at my first job and have for 2 years now. First project I had was to redesign a user info set up page. Didn't know any of the languages so kinda had to just wing it. Anyway finally committed my code and tested on dev server. Then code pushed to production and tested there. Then I saw a message from one of the top devs saying nobody could login. I replied saying that I was able to. Well, I actually ended up making it to where no one could log in except me. I learned real quick to never fuck up like that again. Surprised I wasn't fired on the spot.

First you’re telling me my work always needs to be 1000% perfect and complete, next thing you’re saying everyone makes mistakes and you need the mistakes so you can learn from them.

I’m getting mixed signals here

Need advice:

So I’m 20 years old. Got a decent job as software engineer with a really good pay and really want to break into machine learning.

Mastered NodeJS (my stack has always had node for the past 5-6 years) and I’m finding it difficult to switch to python for machine learning since things are so engraved in my head in javascript.

Aside from the syntax when I’m watching tutorials or reading books, I see data scientists and mathematicians make design mistakes in their code and it hurts my eyes and triggers my ocd.

I need tips on how to put my mindset in a moldable state so I can judge less and learn more and absorb data. Like you know that philosophy that when u get old your brain can’t learn things as fast anymore? I feel like that’s already happening to me rn at the age of 20.

HOW TO HIRE A PROFESSIONAL HACKER TO RECOVER MY STOLEN BITCOIN. CONTACT A CERTIFIED CRYPTO RECOVERY EXPERT FASTFUND RECOVERY .

FASTFUND RECOVERY TEAM was so thorough, they were so straightforward, had clear guidance, and was extremely Knowledgeable when I contracted them for a CRYPTO RECOVERY job. The root of wisdom is the awareness of what you don't know and after my investment loss, in my wildest dreams I never thought asset recovery was real or even possible, “FASTFUND RECOVERY TEAM” is indeed one of one. Missteps are an inherent part of investing, but success happens when you learn from them. Repeating the same mistakes without adjustment can lead to ongoing financial setbacks. Let us assume you invest in a product that claims to give you over 50% returns. However, there is a high management fee of 10%, and on top of it, the gains/ investment returns are also taxed. It means your net profit is in the single digits/ stagnant . You may stay invested in the product for years, assuming you are making excellent returns, but the reality is different, you may not even have been investing at all to begin with if all stones were turned. get all the transparency and certainty you need when you contact FASTFUND RECOVERY TEAM. Therefore, you should always pay attention to the various fees, transaction charges, and taxes before investing in a product or asset class. And it’s clear that’s what got us into this at the first place, that is chasing performance and it is a mistake most of us have made. After all, it’s really tempting to see a fund give high double-digit returns and invest in it, hoping that its dream run will continue and one will earn those returns. Unfortunately, in most cases, it doesn’t happen. That’s because the company may flop or the promised returns were never real. Contact FASTFUND RECOVERY TEAM today you’ll want to thank me later;
* E/mail: Fastfundrecovery8 at gmail dot com
* Whats//App : 1..807..500-.75.54