Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "exam season"
-
To those that think they can't make it.
To those that are put down by those that don't understand you.
And to those that have never had a dream come true.
Not a rant, but the story of how I got into programming
I've always been into tech/electronics. I remember being told once that when I was 3, I used to take plug sockets to pieces. When I was 7, I built a computer with my dad.
There isn't a thing in my room that hasn't been dismantled and put back together again. Except for the things that weren't put back together again ;)
When I was 15, I got a phone for Christmas. It was a pretty crappy phone, the LG P350 (optimus ME). But I loved it all the same.
However I knew it could do a lot more. It ran a bloated, slow version of Android 2.2.
So I went searching, how can I make it faster, how to make it do more. And I found a huge community around Android ROMs. Obviously the first thing I did was flashed this ROM. Sure, there were bugs, but I was instantly in love with it. My phone was freed.
From there I went on to exploring what else can be done.
I wanted to learn how to script, so over the weekend I wrote a 1000 line batch (Windows cmd) script that would root the phone and flash a recovery environment onto it. Pretty basic. Lots of switch statements, but I was proud of it. I'd achieved something. It wasn't new to the world, but it was my first experience at programming.
But it wasn't enough, I needed more.
So I set out to actually building the roms. I installed Linux. I wanted to learn how to utilise Linux better, so I rewrote my script in bash.
By this time, I'd joined a team for developing on similar spec'd phones. Without the funds to by new devices, we began working on more radical projects.
Between us, we ported newer kernels to our devices. We rebased much of the chipset drivers onto newer equivalents to add new features.
And then..
Well, it was exam season. I was suffering from personal issues (which I will not detail), and that, with the work on Android, I ended up failing the exams.
I still passed, but not to the level I expected.
So I gave up on school, and went head first into a new kind of development. "continue doing what you love. You'll make it" is what I told myself.
I found python by contributing to an IRC bot. I learnt it by reading the codebase. Anything I didn't understand, I researched. Anything I wanted to do, google was there to help me through it.
Then it was exam season again. Even though I'd given up on school, I was still going. It was easier to stay in than do anything about it.
A few weeks before the exams, I had a panic attack. I was behind on coursework, and I knew I would do poorly on exams.
So I dropped out.
I was disappointed, my family was disappointed.
So I did the only thing I felt I could do. I set out to get a job as a developer.
At this stage, I'd not done anything special. So I started aiming bigger. Contributing to projects maintained by Sony and Google, learning from them. Building my own projects to assist with my old Android friends.
I managed to land a contract, however due to the stresses at home, I had to drop it after a month.
Everything was going well, I felt ready to get a full time job as a developer, after 2 years of experience in the community.
Then I had to wake up.
Unfortunately, my advisors (I was a job seeker at the time) didn't understand the potential of learning to be a developer. With them, it's "university for a skilled job".
They see the word "computer" on a CV, they instantly say "tech support".
I played ball, I did what I could for them. But they'd always put me down, saying I wasn't good enough, that I'd never get a job.
I hated them. I'd row with them every other day.
By God, I would prove them wrong.
And then I found them. Or, to be more precise, they found me. A startup in London got in contact with me. They seemed like decent people. I spoke with their developers, and they knew their stuff, these were people that I can learn from.
I travelled 4 hours to go for an interview, then 4 hours back.
When I got the email saying they'd move me to London, I was over the moon.
I did exactly what everyone was telling me I couldn't do.
1.5 years later, I'm still working with them. We all respect each other, and we all learn from each other.
I'm ever grateful to them for taking a shot with me. I had no professional experience, and I was by no means the most skilled individual they interviewed.
Many people have a dream. I won't lie, I once dreamed of working at Google. But after the journey I've been through, I wouldn't have where I am now any other way. Though, in time, I wish to share this dream with another.
I hope that all of you reach your dreams too.
Sorry for the long post. The details are brief, but there are only 5k characters ;)23 -
I really like my little group for this one huge exam project we have. Everyone's nice, ambitious, takes the project seriously, responsible and communicates well. Additional bonus is we're all on the same skill level so everyone's learning and nobody is dragging a huge load alone. We've had no issues so far and despite being fairly early in the project we're making good progress all around. Is this what a stress-free experience feels like? Pretty happy with the project in general and I think our app idea is pretty cool too.22
-
Started watching silicon Valley. HELL, THE BEST TECH SERIES EVER.don't know why i always end up watching long multi-season series in my exam days xD
Anyways what would you guys choose for your million dollar idea: sell it at $10 million, or build a company out of it? I will definitely sell.14 -
I haven't written a single line of code in three weeks and it's starting to hurt. I need a summer project of some kind but my brain isn't doing any idea-generating moves. Woe is me, this semester hasn't even ended yet and I already wish the next one would start right now 😂😭
Never thought I'd reach a point where I'd miss code (not my passion, simply a means to an end) but here we are.13 -
After 5 frustrating days, I have my laptop running again. Just in time for a data structures and algorithms exam.
TL;DR: driver issues aren't fun.
It all started on Friday, after the creators update. I was doing notes on lectures, and Windows crashed. I thought not much of it, it was just a "random" crash. I'd gotten a similar crash before, but I didn't think anything of it. This time was different, again it was my touchpad drivers that caused the issue, but this time a restart didn't work. I couldn't boot into Windows. I had to roll back to the last recovery point, effectively undoing the update.
This was fine, and fixed the issue, until Windows automatically updated my touchpad again, after me previously changing the driver. Another restart later and I couldn't boot. Time to roll back to recovery, right? Wrong. My drive had somehow, corrupt most of the Windows files.
And so, starts the journey of dismantling my laptop, changing the hard drive and putting it back together, a process that took 3 days due to not having the correct tools originally, and a late delivery.
(I could have rolled back to my backup system image, but that was before the creators update, and would have essentially postponed the issues I was having)
Finally, I managed to get Windows loaded from boot media (thankfully, they seem to tie your Windows licence to your account now) and am currently in the process of regaining all my lost files (which I have to pull from a system image, so it's a lot of digging through compressed files).
On a positive note, things are running well, and the faster hard drive (7200rpm vs 5400rpm) is a nice upgrade. And the touchpad drivers (the same one that kept crashing) haven't caused any problems since.
Now at least, I can get back to programming :D1 -
Me and a couple of friends have this group on WhatsApp where we can share stuff that we do and maybe come up with new stuff to work on as well.
For giggles (honestly irritating to me) I'm gonna summarize some conversations on the group.
26/11
Me: Finally completed my first FPGA program, these devices are amazjng!
NO REPLY
28/11
Me: gonna make the Jacobs ladder thing today! Hope I don't get zapped
Anyone interested ?
NO REPLY
29/11
Me: hey here's a nice electronic circuit, try to analyze how this circuit oscillates (we're all ec 'engineers' well... soon at least)
NO REPLY
2/12
Friend: Guys creed 2 was amazing I don't mind watching it twice
F2 : Really? Why don't we go soon?
F3 : I'm in!!! What's the plan
F4 : how about tomorrow ?
....
3/12
F1 : Guys anyone have notes for X exam
F2 : here. {Link}
F3 : here. {Link}
F4 : how many of you are done ?
F5 : what are the important questions
(just a stupid aptitude test)
{Me} changes group title from X to Notes group
Let's give this another shot
6/12
Me: There's a conference on X technology by Y industry leader ..
Should we check it out ?
There's even a workshop on X
NO REPLY
Alright time to acknowledge my stupidity and my lack of brains for even belonging to this kind of social circle/COUNTRY
7/12
ME: New fortnite season is out
F1: woah it's crazy let's play
F2: already on it, client is updating
F3: are you shitting me? gonna get BROS laptop (i'm going to suck my brothers cock and take his computer)
F4: Hang on bro wait for me also call me on discord.
I hope you guys could stick through that. Well there's no crazy moral to this but if you're one of these guys just appreciate your friend for his efforts once in a while even at the cost of acknowledging your stupidity.
Also, words like BRO are instant triggers and I'll make sure I find you can kill you if you use it more than once every couple of sentences ( I have relatively high tolerance )1 -
What I hate the lost about exam season, is the lack of coding... Spend two months cramming all the theoretical parts of computer science, and it just gives no time to code