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
-
Tips for people new to programming
1. Start counting from zero
2. Trees are upside down, root's probably at the top
3. Warnings are usual, go rogue!
What more? 😂34 -
At Job interview.
Interviewer: Where do you see yourself in 10 years?
Me: I see myself as the leader of a raider group, robbing and scavenging together pieces of what is left of the civilization in hopes to build a weapon powerful enough to take the world back from a rogue AI, which I built myself few years earlier.
Interviewer: What!?
Me: What?15 -
Most of the time devCat is crucial in the coding/debugging process. However, sometimes he gets a little ADHD and goes rogue.
8 -
TL;DR :
"when i die i want my group project members to lower me into my grave so they can let me down one last time"
STORY TIME
Last year in College, I had two simultaneous projects. Both were semester long projects. One was for a database class an another was for a software engineering class.
As you can guess, the focus of the projects was very different. Databases we made some desktop networked chat application with a user login system and what not in Java. SE we made an app store with an approval system and admin panels and ratings and reviews and all that jazz in Meteor.js.
The DB project we had 4 total people and one of them was someone we'll call Frank. Frank was also in my SE project group. Frank disappeared for several weeks. Not in class, didn't contact us, and at one point the professors didn't know much either. As soon as we noticed it would be an issue, we talked to the professors. Just keeping them in the loop will save you a lot of trouble down the road. I'm assuming there was some medical or family emergency because the professors were very understanding with him once he started coming back to class and they had a chance to talk.
Lesson 1: If you have that guy that doesn't show up or communicate, don't be a jerk to them and communicate with your professor. Also, don't stop trying to contact the rogue partner. Maybe they'll come around sometime.
It sucked to lose 25% of our team for a project, but Frank appreciated that we didn't totally ignore him and throw him under the bus to the point that the last day of class he came up to me and said, "hey, open your book bag and bring it next to mine." He then threw a LARGE bottle of booze in there as a thank you.
Lesson 2: Treat humans as humans. Things go wrong and understanding that will get you a lot farther with people than trying to make them feel terrible about something that may have been out of their control.
Our DB project went really well. We got an A, we demoed, it worked, it was cool. The biggest problem is I was the only person that had taken a networking class so I ended up doing a large portion of the work. I wish I had taken other people's skills into account when we were deciding on a project. Especially because the only requirement was that it needed to have a minimum of 5 tables and we had to use some SQL language (aka, we couldn't use no-SQL).
The SE project had Frank and a music major who wanted to minor in CS (and then 3 other regular CS students aside from me). This assignment was make an app store using any technology you want. But, you had to use agile sprints. So we had weekly meetings with the "customer" (the TA), who would change requirements on us to keep us on our toes and tell us what they wanted done as a priority for the next meeting. Seriously, just like real life. It was so much fun trying to stay ahead of that.
So we met up and tried to decided what to use. One kid said Java because we all had it for school. The big issue is trying to make a Java web app is a pain in the ass. Seriously, there are so many better things to use. Other teams decided to use Django because they all wanted to learn Python. I suggested why not use something with a nice package system to minimize duplicating work that had already been done and tested by someone. Kid 1 didn't like that because he said in the real world you have to make your own software and not use packages. Little did he know that I had worked in SE for a few years already and knew damn well that every good project has code from somewhere else that has already solved a problem you're facing. We went with Java the first week. It failed miserably. Nobody could get the server set up on their computers. Using VCS with it required you to keep the repo outside of the where you wrote code and copy and paste changes in there. It was just a huge flop so everyone else voted to change.
Lesson 3: Be flexible. Be open to learning new things. Don't be afraid to try something new. It'll make you a better developer in the long run.
So we ended up using Meteor. Why? We all figured we could pick up javascript super easy.Two of us already knew it. And the real time thing would make for some cool effects when an app got a approved or a comment was made. We got to work and the one kid was still pissed. I just checked the repo and the only thing he committed was fixing the spelling of on word in the readme.
We sat down one day and worked for 4 straight hours. We finished the whole project in that time. While other teams were figuring out how to layout their homepage, we had a working user system and admin page and everything. Our TA was trying to throw us for loops by asking for crazy things and we still came through. We had tests that ran along side the application as you used it. It was friggin cool.
Lesson 4: If possible, pick the right tool for the job. Not the tool you know. Everything in CS has a purpose. If you use it for its purpose, you will save days off of a project.1 -
That feeling when your client connection is more stable than the connection of a fucking game server... Incompetent pieces of shit!!! BEING ABLE TO PUT A COUPLE OF SPRITES DOESN'T MAKE YOU A FUCKING SYSADMIN!!!
Oh and I sent those very incompetent fucks a mail earlier, because my mailers are blocking their servers as per my mailers' security policy. A rant from the old box - their mail servers self-identify a fucking .local!!! Those incompetent shitheads didn't even properly change the values from test into those from prod!! So I sent them an email telling them exactly how they should fix it, as I am running the same MTA on my mailers (Postfix), at some point had to fix my mailers against the exact same issue as well, and clearly noticed in-game that they have deliverability problems (they explicitly mention to unblock their domain). Guess why?! Because their server's shitty configuration triggers fucking security mechanisms that are built against rogue mailers that attempt to spoof themselves as an internal mailer, with that fucking .local! And they STILL DIDN'T CHANGE IT!!!! Your fucking domain has no issues whatsoever, it's your goddamn fucking mail servers that YOU ASOBIMO FUCKERS SHOULD JUST FIX ALREADY!!! MOTHERFUCKERS!!!!!2 -
Coolest project : I revamped classic old school "Rogue" game ☺️
(while I was learning C programming)
6 -
My mentor from my very first dev job. He was also a junior dev as well and used to say crazy things in conversations ar our desks like ‘The pope is the devil’ and ‘We are all going to get mouth herpes’.
I called him “Rogue { lastName }” because he used to dev in production like an animal.
He taught me a lot about coding though.
Miss that guy1 -
I hate buying new laptops. HATE IT. The manufacturers are always trying to do something that makes it more complicated to buy a laptop confidently.
Why not name all of the laptops with numbers? Make them really hard to differentiate. Then offer the same model number across multiple years so it is difficult to determine which year the laptop is from.
Oh. And let’s make sure every laptop has a major flaw in the form factor.
Let’a add a numpad that squishes the keyboard to the left in a weird way. Lets do something to the trackpad to make it awkward to use. Maybe the keyboard should have a weird configuration. Maybe we can put 4 spare characters of various colours on the symbol key caps. How about a battery only lasts a few hours. May we add specialized hardware so you are stuck with windows. Maybe we can make it super thick and heavy. Lets have a screen with terrible viewing angles. Since this laptop has no major flaws we should overprice it. No repairs or upgrades on this one because we filled the computer with glue. Lets double the amount of useless media keys.
It is like manufacturers are trying to design laptops like RPG game character classes. The fighter has no magic or stealth. The magician is weak and gets fatigued. The rogue is very stealthy but has poor defence and attack. The cleric can use magic but only to heal so it is useless in battle. The ranger is good at distance but has poor defence and no magic.
The only notebooks sold that are trying to make balanced character classes are MacBooks. Those cost a premium and aren’t reparable.17 -
When I found the power of poke on c64, and how to output sprites rather than use print statements. Finally, my text adventures changed into full blown rogue-likes!
https://c64-wiki.com/wiki/Sprite/1 -
So today, again, I discovered the importance of unitests.
I was solving this performance issue, in which we had a few update actions for multiple entities in mongo, but it took FOREVER to complete, even when I unified it into one bulkWrite command.
Since the unified write did improve performance slightly, and we wanted to move on, we decided to let this bug go.
So there I was committing my changes when I got a rejection from the pre-commit hook since I didn't have enough unitests coverage.
Ok, let's start writing some unitests.
Some unitests also needed to test the bulk write. So there I was comparing expected with actual result, and suddenly I got a huge facepalm.
Apparently some rogue for loop iterated all entities again for each entity that needed update. So instead of getting one update per entity, I got N identical update commands per each of the N entities 🤦♂️
Needless to say, fixing this fixed the performance bug entirely.
Thank you unitests and pre-commit hooks!2 -
Dude let his sister play a game for an hour, and his performance went to shit afterwards. Turns out she had somehow installed a new rogue AV going around and it did this shit to scare him into buying.
Edit: forgot to add that it's called "Segurazo"
16 -
Chrome blocks sites on my company intranet because the HTTPS is unsecured...
But let's a rogue JS script run that completely freezes my computer and prolly it's damaging my HD and RAM....
I had to do a forced shutdown.... I've never done that in YEARS
8 -
Found this on Twitter.
how people think AI will destroy the world:
going rogue and killing all humans
how AI will actually destroy the world:
strangling us with convenience, replacing our ability to function without it until our lives are entirely controlled by a wealthy few7 -
Since we are using the same password on all our servers (both QA and Production environment) my team somehow decided that it would be easier to copy the private SSH key for to ALL servers and add the public key to the authorized.keys file.
This way we SSH without password and easily add it to new servers, it also means that anyone who gets into one server can get to all of them.
I wasn't a fan of the same password on all servers, but this private key copying is just going against basic security principles.
Do they want rogue connections? Because that's how you get them.1 -
My phone fell down for the thousandth time and i thought it was okay as it usually has been in previous attempts at suicide.
Pressed power button ...
Screen turned on showing lock screen...
Touched back key .... phone vibrated....
Hmmm... It's okay. Didn't try unlocking screen...
Received a call later on....
Swiped to pick up call.... Nothing moved...
Turned the screen off. Turned it on again. Tried opening screen lock. Again nothing moved...
Got an OTG and plugged a mouse into phone.
Cursor moves.
Alas... My Phone's Touch Unit is DEAD :/7 -
Well, I always say that if you going to make things a mess, do it a spectacular way. Today I kicked off a data import job that went bad, and in the process of canceling said job, I canceled myself, and the job went rogue, and became a zombie and ate ALL the system memory, bringing the server to a deathly crawl and throwing a dozen developers temporarily out of work for about an hour, before I was finally able to kill the zombie, and balance was restored to the Universe.
-
I hate those persons...
*sigh*
Don't do this.
Person does it.
Don't do it. We are currently overworked and this _must_ be a project every team agrees on. Otherwise it will end exactly like it is currently - a big mess that every team implemented differently.
2 hours later....
Person books time for said project.
Other team lead: Stop working on it. This makes no sense.
Person: yeah... But I needed to clean it up anyways, so I just started cause why not.
--
Me and the other team lead had a 5 min discussion about it shortly after...
Wasn't the first time said person has gone solo rogue *sigh*
Despite that this is driving me (and the other team lead) nuts...
WHY THE FRIGGING FUCK DOES HE ALWAYS DO IT WHEN WE ARE SO FUCKING OVERWORKED....
Really. Every fucking time this mother tugging bullshit kindergarten play.
I think it's the first time that I said: I don't care - I'll just trash his work when we start on the project as a team in 2 months (Yeah... That's realistic. 2 months minimum...).
The universe really has it's way to make me angry.
I hope he stops tomorrow, we really cannot deal with emotional bullshit at the moment.
*gooozfraba*
How can such fuckwads exist....12 -
Localhost cloud in port 404 (C4)
Rogue like puzzle game (CF)
Piano tiles like runner game (CD)
Emotional Simulator (C7)
Pastebin client (PFW)
Updates in comments as i remember.6 -
Been thinking about game design for a while now. I have been thinking about how the game can affect the player emotionally. I pay attention to off comments people make in game forums. I didn't fully realize the impact of some NPCs until someone pointed it out.
For instance, in Skryim a character would say something like "Your parents should be very proud of you. I am too." People have expressed how profoundly this impacted them. So I put this in my notes of "things to include" in any given game. I also saw a meme where there are people where their only positive interaction with the world could be a video game. I don't know what kind of dark existence that would be so it makes it hard for me to relate. Which is probably why I didn't understand the impact of such a statement. I realized that regardless of the medium, you will have an impact on someone.
I have also been thinking about how people get older they become more of a casual player. But as a casual myself I want to a more detailed system of interaction with the game. Despite the shitty graphics (all text map), the "Mines of Moria" is one of my all time favorite games. It is based upon the Rogue I think. I remember being able to do almost anything that made logical sense with anything. For instance, you could dip arrows in any potion. The affect was not always significant, but you could to that. I want to recreate that in my games. I am going to start with shitty graphics and build a system of interaction that is more detailed than any RPG I have played. Maybe a lot of players will gloss over this, but for those that want that it will be there. I think the biggest issue is often the types of exploits this would allow. So I guess I will have to get good at simulating the player interactions to test things out. I am always a bit frustrated with games that have mages, but all their spells are wrote. I feel like skill trees for all types of play should be expansive and exclusionary. That way a new play through doesn't end up with the same god character every time.
I have been watching One Piece. I now want piracy and ships in my game. Including ship battles with a working crew. It seems like this could make an RPG a lot of fun. Who doesn't want mages casting fireballs at opposing ships?9 -
So I just started my first personal project. Decided to make a text-based rogue-lite.
Feels super good to finally make something that's "mine" 😀 -
We've got two conflicting linters for ruby.
The rubocops serve the IDE and say to outdent access modifiers, giving the indented line a little yellow under-squiggle. Monkey see, monkey do, I indent it.
The company's one in the build pipeline wants to indent access modifiers and literally fails the bloody build, screaming about a rogue access modifier two spaces from where it should be.
Waste of 5 minutes.1 -
How accurate is this guys ? I came across this reading comments on youtube. The moral of Star Wars rogue one ^^ and project management at its finest...
3 -
data layer for new node project established, check!! rogue 1, check!! pretty productive Christmas if I do say so myself. merry Christmas everybody
-
R.I.P John Doe
He made the mistake of writing unmaintainable code then leaving the team.
I just heard of his passing.
He was brutally beaten to death by the new maintainer. Now the maintainer is behind bars.
And now I've been asked to maintain it.
R.I.P Me as well I guess
Joke of course.6 -
South Africa Release notes version v3.0.2
In 1994 SA underwent one of the biggest system upgrades since 1948. In this new rolling release since the system update called apartheid the system has been annexing resources, locking it down, making it closed source, closing it off community updates and from global updates and minimizing services across the board. On 27 April 1994, the new democratic system update was released with a new system monitor, release resources and balancing efficiency in the system. Though there were remnants of the old code in the system, it was being rewritten by a new generation of users, open source resources were established, giving users the right to choose among themselves how to grow the system , and how to better the experience for all.
In 1999 a new system monitor was created by the users, it wasnt as popular as the ground breaking Madiba release but it was a choice by the community to move forward and grow. The system was stable for a few years, new users were able to develop more on the system, making it more lucrative monetary wise. There were still remnants of the apartheid code but the new generation of developers worked with it making it there own, though they had not yet had admin rights to help change the system, they created a developer culture of their own. A new system resources balancer was introduced called BBEE, that allowed previous disadvantage users more admin rights to other system resources, helping the user base to grow. Though the balancer was biased, and flawed it has helped the system overall to grow and move forward. It has major holes in security and may flood some aspects of the system with more outdated software patches, users have kept it in its system releases until the resource balancer moved the system into a more stable position.
The next interim system monitor release was unexpected, a quiet release that most users did not contribute towards. The system monitor after that nearly brought the system down to a halt, as it was stealing resources from users, using resources for its own gain, and hasn't released any of it back to the system.
The latest user release has been stable. It has brought more interest from users from other countries, it had more monetary advantages than all other releases before. Though it still has flaws, it has tried to balance the system thus far.
Bug report as of 16 Feb 2018
*User experience has been unbalanced since the 1994 release, still leaving some users at a disadvantage.
*The three tier user base that the 1948 release established, creating three main user groups, created a hierarchy of users that are still in effect today, thought the 1994 release tried to balance it out, the user based reversed in its hierarchy, leaving the middle group of users where they were.
*System instability has been at an all time low, allowing users to disable each others accounts, effectively
killing" them off
*Though the infrastructure of the system has been upgraded to global standards ( in some aspects ) expansions are still at an all time low
*Rogue groups of users have been taking most of the infrastructure from established users
*Security services have been heightened among user groups though admins were still able to do as they pleased without being reprimanded
*Female users have been kicked off the system at an alarming rate, the security services have only kicked in recently, but the system admins and system monitor has not done anything about it yet
Bug fixes for a future release:
*Recreating the overall sysadmin team. Removing some admins and bringing others in
*Opening the system more globally to stabilize it more
*Removing and revamping the BBEE system, replacing it with more user documentation, equalizing the user base
*Giving more resources to users that were at a disadvantage during the first release
*Giving the middle group of users more support, documentation and advantages in the system, after removing the security protocols from the user base
*Giving new users who grew up with the post 1994 release more opportunities to help grow the system on a level playing field.
*Establishing the Madiba release principles more efficiently in the current system1 -
tech D&D
dev = fighter
ops = cleris
network = wizard
design = bard
dba = warlock
infosec = rogue
it is not mine but i think its great analogy. and because i always choose the warlock1 -
When your routine security testing causes your work laptop to be seized and held for evidence indefinitely because security operations think it's a rogue laptop.
-
So our software clubs discord bot went rogue and deleted a metric ass ton of messages
This is what I get for testing in production. Fml1 -
The current finish of the whole network stuff is... exhausting.
We are in the finishing phase...
Like in the Simpsons:
Knife goes in, guts come out.
I've debugged today 4 h DNS...
One of the nodes - and the only node of 5 - didn't resolve one zone of many correctly.
It always tried to resolve via INet / Dot ...
So a _very_ special snowflake.
After going crazy... I decided to isolate the setup and increase verbosity for debugging.
It tourned out that the DNS server answered correctly - but was asked then again for a response by the defective node.
So I ripped out DNSSEC out from the DNS server, hoping the defective node would be fine with it.
Nope. It resolved then by itself via internet...
Well...
A lot of domain-insecure sprinkles later the defective node behaved correctly.
But why the fuck does _ONE_ single fucking stupid cunt machine decide to go rogue? Every node is equal....
It's just... Insane.
And reading the logs was insane too. -
Argument in the office today when the designers went rogue, ignoring the PM's agreed plan with the client and started mock-ups for what they thought would look better. Boiled down to "No. Just stop that and do what I asked, you're wasting your time." vs "No, we're doing this. I'm a designer, I know this will look better."
Anyone else had issues with designers trying to take charge?3 -
I wanna cool robot sidekick,
The more irritable the better, like bender from futurama or K2 from rogue one. (Even murderous maniac of a an ai like hal9000 and skynet is fine)
The machine learning technologies aren't just there yet though, they can be irritable but not because of their smart ass answers just the opposite really.
I will need a team with 100+ people that are experts in neurology AND machine learning. Also 10 years.. we will get there !1 -
My progress in this month.
First week : One Harddisk Electrocuted
2nd week :
3rd week : One SSD went rogue and One more HDD starts ticking after being dropped accidently.
4th week : Another HDD dies taking all my dev data with it.
Me right now : FML2 -
This *is* a question you silly wrong tagging mother fucker, how dare you doubt me?
Alright, no more disclaimer: I like dungeons and dragons, but it's too fucking much in terms of rules and systems and shit, as in just *making* a character can take a long ass while.
And if that's the highest level of all your ANAL preferences then OK, but I'm not you and things only come OUT of my ass, not inwards, I swear.
Anyhoo, I got fed up with it and wrote my own ruleset and setting as a last fuck you to everyone. It's very simple: if you want to be some kinky magical alien hermaphrodite royal prostitute half sewer dragon princess and three quarters bearded female incest child of demons and fairies then FINE, but you get no bonuses for that shit.
Get it? No complex racial level scaling bullshit, FUCK YOU, race and background is just for vibes, end of story.
You get no attribute or skills or shit to distribute on level one. All you get is a prompt: pick three actions, that's it. You wanna be sexy? Pick "seduce". You wanna set turds on fire? Pick "ignite". Are you an edge lord? Pick "summon". Would you be my wife? Pick "heal", "buff" and "smite".
The game is turn based, and each action you can take is effectively a spell. Everyone can cast a basic spell like walk, attack, talk, crouch, etcetera -- that costs no mana. Special crap like flying and firing fucking electricity costs mana, and you can only do those if you either picked the spell on level one or learnt it later from a book/tutor/demonic bargain/whatever.
Which spells are valid for taking at level one is up to the game master; I just tell people to pick three verbs or short sentences, and if they choose something that's too broken like "split the Red Sea" I'm like nah you're not Moses, try again.
Still with me? Good. You get eight points of health, four points of mana, and one point of stamina. They're all energy, and you can use it to power your magery, but spending all your health means you fucking die.
Stamina recharges fully every turn, and is used for the aforementioned basic actions. All of these cost one point of stamina each. If you run out of stamina, you can use mana. Or your BLOOD.
Level one spells cost one mana, level two cost two and so on. You get back one point of mana each turn, and you can fire all the spells you want during it, long as you have mana. Or BLOOD.
That's good and all, but if you spend anywhere over eleven combined points of energy in one go, you spontaneously combust and die, erasing all signs of life in a twenty-meter radius. This is called incineration, and it *will* leave behind a blackened crater from which the dark servants of the Horror Immemorial may or may not crawl out of.
In case you didn't guess by now, your blood doesn't fucking come back unless you eat, sleep or see a healer.
But anyway, the more points you spend into casting a spell -- and remember, basic attack counts as a spell -- the more powerful it is, so the bigger your diceroll can get. My rule is I add one dice for every fourth point of energy spent, so (1d4), (1d4 + 1d6), (1d4 + 1d6 + 1d8), incineration.
Additionally, for every three points of energy spent, your spell can hit one more target. That's right, you like AoE? Then spend more mana, bitch. Oh, and if you're using shit like poison it lasts one more turn for every two points of energy spent.
How do we calculate damage? Diceroll over two and fuck your mother. Armor class? Resistances? Out of my face with that shit. Damage reduction is called "tyranny" and is for dungeon bosses only.
If you live long enough to get to level two, you *do* get attributes. Pick:
- Grit: +2 health, +1 to fighter shit type rolls.
- Cunning: +2 mana, +1 to rogue shit type rolls.
- Allure: +1 stamina, +2 to wizard shit type rolls.
- Spirit: +1 to elemental shit type spells.
- Faith: +1 to benefactor paragon asshole shit type spells.
- Hatred: +1 to demonic murder hobo destructive shit type spells.
On second level, you can pick one of the spells you know to get +1 to it, specifically. Eh, "+1" just means you get a bonus to some diceroll, no time to explain I'm running out of characters what the fuck.
On level three, the cycle repeats. Pick attr, pick spell. DONE.
Oh right, and weapons. Mostly just vibes, pick your fancy and fuck off. Normally, you can hit things one tile away; if you have a BIG melee weapon you can hit from *two* tiles away, and if you have a ranged weapon you can shoot anyone in sight, but you need to spend one point of energy to reload.
And there, all bases covered in less that 5000 characters with some flair to spare, now suck my fucking cock Hasbro.
What was the question? Oh yeah right, I'm gonna GPL this shit and put it in browsers. I think I'm going to write it in Kotlin but I'm open to suggestions. Would you guys like to play it/contribute to it's development for shits and giggles?8 -
Little help needed to understand this:
Rogue detector: An AP dedicates itself to detecting rogue devices by correlating
MAC addresses heard on the wired network with those heard over the air. Rogue
devices are those that appear on both networks.
1.How can the same MAC appear in both networks? 2.If it does, why does it mean its a rogue device?4
Top Tags
Weekly Rant
View