AboutSoftware developer living in Argentina. I love coding and running. I like to travel the world (who doesn't) and the seven seas.
SkillsMostly Java with a special enfasis in the Spring framework and web services development. I also dabble in c++, js, node js and python. I like to know all the tools of my trade.
Joined devRant on 7/11/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
So I decided that instead of let a bad meme thread misinforms our users, specially the young ones I decided is better to make a proper one with Open Source/Libre Software and Hardware in the community and bring up attention to it, of course at the same time I require if you could both ++ this to help it up so new users can see it and also for you guys to help out informing us about such projects if you came around,now to the point:
For me I can at least comment that seems RISC and POWER may make a new come back as fully open source hardware without any kind of close sourced drivers and such, right now Im only aware of this platforms:
There is only 1 motherboard Im aware is sold commercially to big companies and is quite recent, mostly after the whole New EU law about data breaches and such so yeah, Its rather wicked expensive and not for your average joe:
I usually don’t use caps so I apologize but.... HOLY FUCKING SHIT! MY PERSONAL BUSINESS THAT I BUILT WITH My HANDS HAS JUST SIGNED A ****HUGE**** contract!! More to come!13
*SSH's into VPS*
*Starts doing some general maintainance (updating, checking the logs etc)*
*runs the who command for fun*
*NOTICES THAT THERE"S ANOTHER ACTIVE SESSION*
*FURIOUSLY STARTS TO TRY AND LOOK HOW THAT USER MIGHT HAVE GOTTEN IN (root)*
*Goes one terminal to the left after a few minutes to see if I can use that one as well*
*notices an active and forgotten SSH session to that VPS*
I am stupid.19
I don't like anything political on here, but this is affecting us all, even non-US people.
Today is the day, take a stance, fight for NetNeutrality12
How everyone uses stackoverflow:
1. Work on some project
2. Spot a bug
3. Try to solve the bug and fail.
4. Write a question for SO.
5. Post question on SO.
6. Get the answer and some points.
How I use stackoverflow:
1. Work on some project
2. Find a bug
3. Try to fix the bug and fail
4. Write a question on SO
5. Get scared that I might be downvoted.
6. Spend 45 minutes optimizing the structure of the question.
7. Try additional tests to cover all possible scenarios.
8. Still scared to click post.
9. Scrap everything and restart line by line writing further details of each step in your question.
10. Find the bug myself.
11. Click cancel on the question that took me 3+ hours to write.
After reading a lot of cryptography, I realized that it would be best if Alice and Bob just talk in person13
"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"
So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.
First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.
So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.
Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?
I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.
Did you run the code I gave you to do this update?
"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"
So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.
More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!
I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.
And this, my friends, is the part I will never forget.
"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."
You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!
"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."
I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.
So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.
You just cannot make this kind of stuff up.101
Hi everyone! Sam here, @dfox's gf :) so happy to be talking to you all! Today I will be live-ranting TNW Conference where devRant will be presenting with photos in this thread. Pictured here, @dfox and @trogus setting up our booth. There will also be a stage presentation, a sticker printer on site (because how could we not :)), and energy drink/stress ball giveaway. Stop by and say hi if you're here!!
Go devRant team!39
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!209
I was dressed up as an UDP packet for the Halloween. I don’t think anyone got it, but I couldn’t tell. #humour
Have a great Halloween :)4
I agree 😂
(The preview doesn't work with that size, at least on my device, just click below the comment, where the picture it's supposed to be)
I once designed my own Arduino IDE compatible microcontroller, and even had the card manufactured.
Sadly I've yet to actually use it for anything, but hey, achievement unlocked, right?15
TL;DR: Read it.
Please don't redistribute without permission. *PUT OPEN SOURCE LICENSE HERE*
Many users in devRant use Windows but then the "Arch Linux Alliance" short ALA came together to invade devRant. After some weeks, the small group FedB ("Fedora Bureau") also joined the OS Wars. When the release of Ubuntu 16.10 was near the UBO ("UbuntuBestOS Alliance") joined and was near to victory, because dpkg was faster than ever before. But then the macOS Defenders woke up. They finally finished the upgrade to Sierra and tried to fight the other OSes. They wanted to attack with their package manager, but that attack failed. After days of war Windows crashed while updating, which made it unoperational. They called it Blue Screen. After windows gave up, the other groups realized, that they are all built with the same base. They called it Unix. They grouped up (except macOS, because they just want to make money) and discovered the remains of Windows. They found a software named "Ubuntu bash for Windows". Everyone in the group was angry, because UBO teamed up with Windows. They destroyed UBO and continued.
To be continued.
Should it continue? Comments...4