Was a co-lead on the first project to add image recognition to ATMs for depositing checks. Turns out, it was a pretty OK idea and people liked it.

INTRODUCING:

---

SYNTAX HIGHLIGHT BOT

---

I have lots of ideas.
This was one of them.

Last week I was playing around with https://carbon.now.sh and found it quite cool!
Then I thought: https://carbon.now.sh supports Twitter. Cool. But what about devRant?
So yeah, then I got the idea: A devRant Bot that generates https://carbon.now.sh images!

Now, 4 days and 800 lines of code later, the bot is ready!
I even had to rewrite the notification checking code 4 times, because none of them worked perfectly...
But on the other hand, the final solution is so good that I want to keep it a secret for now ;D

---

HOW TO USE:

All you need to do is to mention the bot!
Example:

<rant>
@highlight
console.log('Hello World!');
</rant>

The bot then generates your syntax highlighted code (as an image) and posts it as comment a few seconds later.
Everything before the "@highlight" will be ignored!
Example:

<rant>
Look at this code:

@highlight
function add(a) {
return a + 1;
}
</rant>

Here, "Look at this code:" will not be included in the syntax highlighted code.
If the comment text ends right after the "@highlight", the bot wont reply, btw.

---

THEME SELECTION:

That's not all!
You can even select the theme for your syntax highlighted code!
Just go to my other rant and read the instructions!
The theme will be used for every image the bot generates for you!

Link:
https://devrant.com/rants/2178551

---

Feel free to ask any questions in the comments!
My creator (and father thanks to @rutee07), @Skayo, will try to answer all of them!

P.S.: Speaking of @rutee07: I'm a girl. (Also thanks to him)

I'll just leave this here:

https://google.com/search/...

1. Buy boxes of orange juice, almost past their expiry date.
2. Put boxes on the hot office windowsill for a few weeks.
3. Cool down juice in fridge.
4. "Hey dear coworker, would you like a refreshing juice box on this hot spring day?"
5. Watch coworker retch and vomit, spitting blue-grayish juice over his desk, crying: "Why would you give me old moldy juice without checking the date?"
6. "Do you remember when you told me you didn't have time for unit tests? THIS IS WHAT HAPPENS, DAVE, THIS IS WHAT FUCKING HAPPENS WHEN YOU DEPLOY UNTESTED CODE.... NOW FINISH YOUR JUICE!"

So this is what a test looks like here in my school...
I really like my teacher but his test are... uhh... fucking awful.

I mean the code isn't even indented ffs! Like wtf?!? How should one be able to read this bullshit?
The questions are shitty too.
Also please add line numbers so it is easier to describe how things work in the code.
AND USE FUCKING A4 PAPERS FFS!!!

Thanks,
an experienced student

Im going to fucking murder the QA team if they don't stop sender bullshit issues!

QA: hey dev, there is an error with attached files.
Me: okay what's the issue?
QA: it's just a random file that gets attached. Can you fix it by the end of the sprint(tomorrow)?
Me: I need to investigate it a bit before I can tell you how long it will take, how can I reproduce it?
QA: idk, it was just there.
*several hours of testing later*
Me: I've tried to cause the 'issue' on my local server, the test server and the live server. But I haven't seen it and I have no clue what could cause it.
*30min. before I go home*
QA: dev you have to fix it before you go home! Because we have some other important issues you have to fix tomorrow!

FUCK YOU AND YOUR IMAGINARY ISSUES I'M GOING HOME

Today at work, still laugh thinking back to it!

We were on lunch break but the linux support engineers who are on the phones as well have to pick up calls anyways (very small team).

*engineer walks to the table, sits down: Ahhh rest, finally!*
*tringggggggggg*
*engineer pulls a face like 'oh for fucks sake' and walks back to his desk*
*puts headphones on and clicks the answer button just as it disappears*
"really!?! Alright lets finally eat now"
*sits for literally one second*
*tringgggggggggg*
*Engineer seems quite pissed off now. walks to his desk again, puts on headset, clicks the answer button JUST as the call stops again*
"Mother of god, fucking really?"
*stays as his desk for a minute or so, walks back, stays hovering above his chair for a little and finally sits down again*
"Finall......"
*TRINGGGGGGGGGGGG*
"MOTHERFUCKER. THESE GUYS TIME IT OR SOMETHING!?!?"
*walks back to his desk very frustrated this time*
*puts on headphones very quickly and presses the answer button*
*answer works but the call is literally dropped the second he starts it (it was a real client)*

"OH FOR FUCKS FUCKING FUCKING FUCKING SAKE FUUUUUUUUUUUUUUUUUUUUUUCK"

*walks back to table again and sits down. Takes sandwich and....*

*TRINGGGGGGGGGG MOTHERFUCKER*

"FUCKING COCKSUKING MOTHERFUCKING PIECES OF WHAT THE FUCKING FUCK EVER"

*gives a deadly look to another engineer: "I am NOT going to take it this time! En-fucking-joy."*

We laughed so hard xD

Pc vs Iphone X? 😃

A simple, open source Neo4j client written in PHP - help craft project decisions and develop as a team [more details]

A bot has way more ++s than me. GJ @Skayo.

How to get an invitation for Google Foobar:

Open google.com/ncr (Original page) and search for "Arraylist Java"
Copy the URL of the search result page and repeatedly open a new tab with that link (You can press ctrl and spam 't' and 'v')
After you open the necessary number of tabs (about 15-20, not sure), you'll get a black bar saying you're invited.

Enjoy!

HTTP response code cheat sheet
(From /r/Programmer humor)

EDIT: devRant April Fools joke (2017)
-------------------------
@trogus and I have had an absolute blast working on devRant over the last year. However, we're strong believers in only working on a project if you're passionate about it, and over the last few months, we've sadly lost some of that passion so we've to announce, with heavy hearts, that we will both be moving on. We've decided to focus 100% of our energies on our next product, one which we are confident has billion dollar potential: Semicolon JS (http://semicolonjs.com).

We identified this sizable market opportunity as we were building out the new devRant website. Every JavaScript framework we tried left us wanting more. More efficiency. More elegance. More extensibility. That's what Semicolon JS is: more. More than a framework, it's a guiding philosophy. We believe that Semicolon JS will do for front end development what Material Design has done for user interface design. We're calling it Semicolon JS because even though you can still develop JavaScript without it, like a semicolon, we think it will soon become a standard and synonymous with quality JS development.

So comes the obvious question. What will happen to devRant? We wanted to make the announcement today because we will be officially shutting down the product in 30 days. So that gives everyone a full month to take in the last memories, look at those rants they really loved, and hopefully take some time to chat with @trogus and I about Semicolon JS and what we have planned.

With so many thanks and looking towards the future,
- @dfox and @trogus

!Rant
Do you guys know any website that challenges​ you into coding little programs (for me, php) to solve problems ?
I mean, it would be to train my skills with actual kind of real world problems, not just hello worlds or simple "how-to" codes.

I signed up to a contest recently and I felt really dumb not to be able to find solutions faster or with more efficiency (FYI : I was ranked 1049/2300 all languages included :( )

I have a new goal

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

Thug life

#office 😂

One day when I was about 8 years old my friend and I were in the library. We decided we wanted to try to make a baseball website because we both likes baseball (this was around 1998). We picked up a book on HTML and my dad took it out for us. My dad was also a programmer so he said he would help us learn. We went home that afternoon and made a little website!

I knew right then that I really enjoyed programming and creating things with code, but I realized I wanted to be a programmer in middle school and high school. One of my friends and I started building Flash games. To see if people were playing them, I added in a call to each game that hit a PHP script on our server. I'll never forget the days/weeks that one of our most popular games caused our sever to get hammered and our shared host said they were going to boot us.

It was an awesome feeling knowing people were enjoying these games that we worked really hard on, and that's one of the main reasons I always wanted to be coding/creating things that people enjoy using.