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 - "lucky number"
Hey, haven't written a post in forever. Just wanted to talk about teaching kids Scratch. Something I've been lucky enough to do the past few months. It's been a great experience, despite the obvious frustrations. These kids, at a number of different schools, mind you, are great to work with. It's just truly rewarding stuff, and some of them are so intuitive, it's mind blowing. It's not particularly difficult work, but it feels truly rewarding. Just wanted to throw that out there to encourage this community of smart, great people to do the same. Especially if you're not currently working full time, like me. If you have questions feel free to ask.2
I just had such a forfilling moment.
Normally, i often (force myself) go to bed at night, after i worked on a project of mine, with these thought saying "oh man i wanted to get that feature done today" or "i want to finish this and that part of my code".I am sure everyone of you knows the feeling, when your brain communicates that you are just not done for today.
Today it was different. I got a project of mine working in it's first state, where i put much heart, love and time in.Just a few minutes before i finished for today i got my server responding the expected numbers(some kind of pin-code). It's a very easy system: Someone(at the time only me and my debug mode :3) on a android phone request a verification which is checked and processed by the server. The server creates a random six-digit number, returns it encoded to the client and sends an email to the user, which currently sends it in plain text(shame on me).
Yeah, the user enters the number and voilà
And of course, all the Pincodes can only be used once.
I got to bed with this feeling of luck and succes.
I hope tomorrow is going to be a productive day!
I am so lucky right now.
Have a good day everyone!
Lets play a little python game together and win some devRant points :
We have an array of integers named L
We need to sort this array so that the biggest number be in the beginning and lowest at the end..descending order
-You are not allowed to write more than one line of code in the comment...only one
-if you comment once...you cannot comment directly after that...you have to wait for two other comments after you so you can comment again
-you have to build your code upon the previous comments ... you cannot start from scratch
-the lucky one who puts the final comment is the winner..and we should all ++ his comment to give him the biggest amount of points
Lets start and see who will win :)15
I was so tired of work last week and weather was so good I ended up in a bar.
People were so nice there so I got there second day in a row.
I met new nice people and cute female bartender who laughed from my jokes.
Was to drunk and tried so much to make her laugh that l forgot to get her number.
Got there next day asked bartender for her shifts, turned out it was last day of her work, she moved out from city for at least a year. So I got drunk again, and so on 5 days in a row.
Well that’s my life. Lucky me... again.
Karma is so funny I can’t laugh for some time anymore.
Many of you commented on my previous rant regarding my first ever freelance gig that I would definitely be back with even more to rant... here I am.
What was supposedly a 1 to 1.5 month long project became one that is stretching beyond 3, if lucky, else 4 months long. Requirements and scope evolving more complex and with variations more intense than pokemon evolutions.
I fucked up. I signed a contract that nobody would have. I didn't plan or protect my ass enough to prevent such shit from happening. I severely underestimated and hence under quoted. This is one of the nightmare situations a freelancer could be in (in my opinion). I mean it could only get better... Right? I'm preparing myself for one hell of a payment at the end of the project. Brace yourself, payment is hopefully coming as fast as the number of seasons it took for winter to come in GoT.
On the bright side, I'm currently working on a new project with a client that is indeed much much better than this first. I mean he is a nice person and communications thus far has been nothing short of great.
I guess it's good to start with your expectations rock bottom, that way nothing else can be worse, I hope.
I usually don't do these types of posts, but it's a nice number, and i feel lucky to have caught it. Usually I just miss it by a few and then my next rant gets too many ++ and I just miss it.2
I worked at my previous job about 8 years (hired out of school) and wasn't actively looking for a new one; I had a lot of freedom and liked my boss and colleagues, but the pay was mediocre and I was under a lot of pressure because I was the sole architect, engineer, and programmer for a good number of important applications.
Anyway, my brother-in-law told me that his employer was looking for a developer and that previous candidates fell through, and that the pay was a lot more and they're good about raises (which was like pulling teeth at my then-current job) so I applied and went for an interview.
They basically gave me an offer on the spot and wanted me to start in 2 weeks. I told them that it would be hard since I'd basically be cutting my boss's Achilles by leaving so soon and suddenly (just hiring someone would take at least a month, not counting getting applicants), but they were adamant, as the position had been vacant for a few months at that point. I got them to agree to 3 weeks and pulled the trigger, but offered to help out in my old position for a few months cause we had a big project in progress I was leading.
So the new job is great: it's a much younger office and I'm having more fun and there's a lot less pressure. Meanwhile, at the old job, the project I was leading got scrapped and the asked me to do other odds and ends until, after screwing something up I basically told them I'm done. They got a new guy quickly due to a lucky turn of events, but he couldn't pick up where I left off on a lot of projects: they're going to rewrite one because of it. My one colleague still likes to point out that I left without them having knowledge of my code (besides that I always said I'd answer questions, plus it's been 6 months now and my code is all on a TFS instance they all have access to).
I still feel a bit guilty even though I have no reason to.
Setting up a new docker environment for developing, its my first experience with it...
Guess who drew the lucky number to do the experiment...
Anyhow... Progress is slow, cause the sys admin refuses to cooperate, feeling threatened by the thought of us devs being able to do more ourselves...
Not to mention, our servers currently are a mess, there's no common ground, it's a mix of whatever was needed at the time, no documentation at all...
This is making the whole dockerizing process so damn painfull1
You work in a team, for a team to move forward successfully the team should work in sync. A team always has a goal and a plan to get to it. There are times when the team needs to take a different direction therefore the set path should always be available for change because our environments dictate it.
We all have different styles of working and different opinions on how things should work. Sometimes one is wrong and the other is right, and sometimes both are wrong, or actually sometimes both are right. However, at the end of it all, the next step is a decision for the team, not an individual, and moving forward means doing it together. #KickAssTeam
The end result can not come in at the beginning but only at the end of an implementation and sometimes if you’re lucky, during implementation you can smell the shit before it hits the fan. So as humans, we will make mistakes at times by using the wrong decisions and when this happens, a strong team will pull things in the right direction quickly and together. #KickAssTeam
Having a team of different opinions does not mean not being able to work together. It actually means a strong team! #kickAssTeam However the challenging part means it can be a challenge. This calls for having processes in place that will allow the team members to be heard and for new knowledge to take lead. This space requires discipline in listening and interrogating opinions without attachment to ideas and always knowing that YOUR opinion is a suggestion, not a solution. Until it is taken on by the team. #KickAssTeam We all love our own thinking. However, learning to re-learn or change opinions when faced with new information should become as easy to take in and use.
Now, I am no expert at this however through my years of development I find this strategy to work in a team of developers. It’s a few questions you ask yourself before every commit, When faced with working in a new team and possibly as a suggestion when trying to align other team members with the team.
The point of this article, the questions to self!
Am I following the formatting standard set?
Is what I have written in line with official documentation?
Is what I am committing a technical conversion of the business requirement?
Have I duplicated functionality the framework already offers?
I have introduced a methodology, library, heavily reusable component to the system, have you had a discussion with the team before implementing?
Are your methods and functions truly responsible for 1 thing?
Will someone you will never get to talk to or your future self have documentation of your work?
Either via point number 2, domain-specific, or business requirements documentation.
Are you future thinking too much in your solution?
Will future proof have a great chance of complicating the current use case?
Remember, you can never write perfect code that cures every future problem, but what you can do perfectly is serve the current business problem you are facing and after doing that for decades, you would have had a perfect line of development success.1