Details
-
Skillsjs, php, nodejs, react/redux, laravel, vue
-
LocationLocalhost
Joined devRant on 12/12/2018
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
-
Vsauce has made all of its Mindfield content free on youtube...
Watched the episode about moral licensing
TL;DR; If you do something very good you tend to compensate and give yourself a free pass to do not so good
It happens to me in software when I accomplish something really fast, like a bumpy process that is undefined and in most cases should take X amount of time, but due to luck + experience + right mindset I get it done like 5 times faster...
I end up wasting the other parts of the time feeling good about myself and exploring google maps and writing rants here...4 -
I might be fucked up, but I have a tendency to gravitate towards the shit that everyone else dislikes for the sake of knowing if their bias against is actually because shit is truly fucked up or if shit is legit plain WRONG.
From all technologies that I have worked with professionally I can count:
Java(currently in the form of old JSP services for an "enterprise level application")
Java for Android development - i was the lead engineer for a mobile project
Swift with IOS dev, same gig as the above.
C++ for Android development in the form of OpenCV with Java as well.
Javascript in all possible forms, basic input validation, ajax services, jquery datatables, jquery animations and builders.
Css/sass heavily
Clojure for an ldap active directory application
Python for glue scripts
Classic ASP with JScript and VBScript
VB Net forms
C# For ASP.NET MVC
Bootstrap for multiple intranet frontends
Node+Express for a logistics warehouse management tool
Ruby on Rails freelancing small gigs
Php in all ways possible from complete standalone php apps to Laravel and just php+composer apps aaaaall the way to wordpress
Django consulting
I have found that the one that I dislike the most is wordpress. And the one that I like working with the most is Node. Don't know why, i just do really fucking like messing around with Javascript, the language has changed a fuckload throughout the years and continues to increase and change. It was my first scripting language following a stint in me trying to learn cpp way when i was starting and royally FAILING
Never really got the hate for it, even when I used JScript with classic ASP i just enjoy working with Javascript a lil too much. And from all the above mentioned stacks safe from Php is the one, or one of the ones in which i don't royally suck :V3 -
Today I discovered by myself that...
...in a shell...
...when entering a password (e.g. ssh)...
...and you make a typo... 🤦♂️
...you don't need to smack that backspace key like a maniac! You can just use the clear line shortcut: control+U (^U). This clears all input to the left of your cursor and this also works for passwords.26 -
Google: You need a fast website to rank well.
Me: Ok, so why does your Google Analytics, Google Tag Manager, and Google Optimize code drag my site down to the seventh circle of Hell in performance?
Google: You need a fast website to rank well.
Me: ...3 -
The inevitable happened, the user that I've answered tons of questions about freelancing deleted his account, thankfully I took backups and will recreate it [together with a killed joke] in the comments below (should've just webarchived it, meh)
I'll keep adding questions & answers I come across to make this a useful resource for people that want to get into freelancing, want to ask me something in the comments, you name it.
Might compile it into a better searchable resource eventually (some sort of blog with TOC), but right now neither do I have the time nor will to do that.
Wish I could have taken over the link that has been now posted a lot, but every post has an ID and I doubt it's possible, will tag dfox to clarify though and also floydian and devtea, that have been so nice to always post a link to that one rant.52 -
After spending a few months on this site, what strikes me the most, is how unhappy a lot of programmers are.
It kind of makes me sad to see so many of you struggle with office politics bullshit everyday.
I have a confession to make.
I've never had a programming job, or freelanced, yet I have made a very comfortable living with programming and marketing for the past 20 years.
I make my living by finding niches where there is shit software, and creating a better alarm clock.
The first 5-10 years of doing this, I worked my ass off (throughout my twenties)
But during most of my thirties, I barely had to
work to keep it all up. I get residual income still
from stuff I did 10 years ago.
I'm curious if anyone at all would be interested in learning how to do this, quitting their job, for example, or, just having the freedom to write your own code without answering to anybody but your own customers. Many of whom you never have to talk to, they go to your site, they buy, and rarely ever send emails (if you do it right)
Everybody here has knowledge that is so bankable, yet they seem to just surrender to
asshole bosses and clients. It doesn't have to
be like that.
If you'd be interested in this, please ++ this.
I'm thinking of creating an online course about creating and marketing your own software, specifically for programmers like you guys. and girls.
I genuinely just want to see if there's interest. I hope that's ok.63 -
I wrote my resignation letter yesterday, all’s good.
Today, bossman walks in:
“I’ve got some great news, all our developers are getting a raise”
Me: *well shit*15 -
So basically there's this guy, that work with us that relocated from a small village south of Italy to the city where we have the HQ.
So after a while this guy has found a girlfriend here and after few days we discovered that he never had sex in his life. you may ask, how did you discover it? Yes, basically he disappeared for a week, his phone was off, no slack, no Facebook, nothing. We couldn't contact him in any way. After a week he gave a call to our cto saying sorry about what happened and explaining that he spent the whole week having sex with his girl, day and night. This story has also a good end because he still has his job.27 -
Someone found my curriculum online, hooked me into an interview. I go there and the dude that handles the interview asks me: "So, why do you want to work with us?"
Man, I don't even know myself.18 -
+++ Microsoft switches to the open-source Chromium engine for the Edge browser +++
On December 6th, Microsoft announced that they will dump their own Edge engine and replace it with Chromium, an open-source browser engine developed by Google.
This way they are promising the ~2% of global internet users who prefer Edge over other browsers to experience a better web experience.
The about 2% of market share is one of the reasons Microsoft decided to stop developing their own engine. It's just not worth it.
Joe Belfiore, corporate veep of Windows, said they also want to bring Edge to other platforms, like macOS, to target more audiences.
Web-Developers, like myself, will most likely have the most to gain. Less browsers to target means less incompatibility issues.
There are a lot of HTML5 features that the Edge engine doesn't support...
The new Edge won't be a UWP app, in order to make it usable outside of Windows 10. Instead, it will be build in accordance with the Win32 API, so we can even expect support for older Windows versions, like Windows 7 and 8. A preview release is planned for early 2019.
Because they are switching to Chromium and the Win32 API, Microsoft is hiring new developers! So if you always wanted to work at Microsoft, now is your chance!
That's it!
Thanks for reading!
Source: https://theregister.co.uk/2018/12/...11 -
Another fucking rant about my fucking goldfish brain.
At meetings, I usually note down things I need to fix, to do on the sticky note pad that comes with the OS, currently Mint.
I sat at my desk.
Looked at my notes.
Decided to properly put them as tasks on trello.
I copied all notes, planning to paste it on a trello card quickly.
Then I can just work on trello and separate into different tasks.
Connection issue.
Ethernet said connected but websites are not showing up.
Maybe restart will fix since I haven't opened any app and started working anyway.
Reboot.
Internet works.
Yayyy.
Trello showed up.
Yayyy.
oooh
f
u
c
k.
fuck.
fuck.14 -
It's so annoying. Whenever you are at a hackathon, every damn team tries to throw these buzzwords- Block chain, AI, ML. And I tell you, their projects just needed a duckin if else.😣
-
!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!222 -
I was an Android developer in a company, I was told to generate a release APK file to test it locally.
So, to sign the apk, I created a keystore file and the password is my name. they decided to publish the file on Play Store.
I left the company years ago, and still on every update they have to put my name as a password.5