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 - "unstoppable"
-
Sales employee Bob wants a clickable blue button.
Bob tells product owner Karen about his unstoppable desire for clickable blue buttons.
Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons)
Karen asks the button team how hard it is to build a button. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points).
These three scores are combined to give a priority score. The global buttonbacklog is sorted by priority.
Once every two weeks (a "sprint") the button team convenes, uses the ease scores to assign scrum points. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. They use the average of the last 5 sprints to calculate each developer's "velocity".
The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. Approximate due dates are assigned, Bob is a happy Bob.
What if boss Peter runs into the office screaming "OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR"?
Devs tell boss to shut the fuck up and talk to Karen. Karen has a carefully curated list of button building tasks sorted by priority, can sedate boss with valium so he calms the fuck down until he can make a case for the impact and potential of his pink button.
Karen might agree that Peter's pink button gets a higher priority than Bob's blue button.
But devs are nocturnal creatures, easily disturbed when approached by humans, their natural rhythms thrown out of balance.
So the sprint is "locked", and Peter's pink button appears at the top of the global backlog, from where it flows into the next sprint.
On rare occasions a sprint is broken open, for example when Karen realizes that all of the end users will commit suicide if they don't have a pink heart-spawning button.
In such an event, Peter must make Bob happy (because Bob is crying that his blue button is delayed). And Peter must make the button team of devs happy.
This usually leads to a ritual involving chocolate or even hardware gift certificates to restore balance to the dev ecosystem.23 -
Computer Science is a mysterious world of three kinds of devs, irrespective of what background/profile/language they had/worked in.
The ones at the top, who keep doing crazy shit in big companies or open-source and keep adding material to the unstoppable code flowing. These constitute 5% of the dev community.
The ones at the bottom are the newbies who try to become masters/ninjas of programming by following the shit on the internet but don't understand logic or how things work. This is like 75% of dev community on the web. If you don't agree to that percentage, you don't know the number of students and non-CS people trying to code. I can see hundreds of classmates/colleagues with no understanding of basic Javascript concepts but introducing themselves as a software developer and ruler of the Web.
The remaining 15% in the middle are the "experienced" fellows who keep building shit to get to the top 5%. They work on enterprise/commercial software until the next upgrade and while the wallets keep getting fatter, they don't actually contribute to the community.
This is the part where I want people to understand the power of a dev.
What sets apart programmers/devs from other engineers:
while everyone else is busy solving the current issues/requirements of the world, we devs are the ones who 'build'.
With a right motive, a developer can solve in-numerous problems of the society, be it education, poverty or unemployment.
An experiment by Lee to put data on the web created a world of unforeseeable opportunities.
Hope to see more of Musks and less of Zuckerbergs in the future.9 -
Sometimes when i code i feel unstoppable ,those are the days that i am very productive,then there are days that i feel like an idiot and i cant code a single line6
-
Today i implemented something of such a complexity that the part of my brain i am in could not follow it.
(Really guys. I did not know what i was doing. I only knew i had to do it exact this way)
This feeling when you are in a tunnel and unstoppable. I even documented what i did.
Sadly i do not even understand my thoughts there xD
I wrote about three hours straight and then run a test. And the only mistake was a variable not filled as described. Used another one and it run smoothly as hell.
Today i will drink a beer on whatever part of me did this. Cheers6 -
Me: okay brain! We had our morning coffee. We're ready to work. Lots of things to do today.
Brain: yay! I feel unstoppable! Can't wait for logic problems and amazing things we're going to build! What's the plan?
Me: great! Today we're going to work on the ios implementation of our app. Where should we start?
Brain: ...
Me: brain?1 -
A minute before an important Skype call my Bluetooth headset just won't connect, windows asks for a restart to set it up and then of course runs unstoppable updates before allowing me to login... fuck it, going for a swim, the interview looked lame anyway2
-
It’s time for me to thank people who, through their work, defined me as a person.
Thank you Terry A. Davis. You completely obliterated my whole narrative of “being incapable because of mental state”. Your example is the reason I’m privileged enough to type this right now, you’re the reason I survived depression. You showed me how to overcome FOMO once and for all by just doing what I’m supposed to as good as I can. Fame will come. And indeed, it came.
You’re not the smartest programmer who ever lived. Only humans can be programmers. You’re a superhuman. You’re not the smartest programmer. You’re just the smartest.
May you rest in peace.
——
Thank you Richard Matthew Stallman. You showed me that the good which also can fight is a thing. You taught me to be afraid of nothing. You taught me how to be an immovable object, no matter the unstoppable force opposing. Because of you I can freely interact with people and my illness has no influence on who I am.
——
Thank you Håkon Wium Lie. You showed me that the ways of overcoming and suffering aren’t the only ones. You’re charming yet uncompromising, empowering yet never reckless. Since we met, in any troubling social interaction my brain automatically thinks “What would Håkon do?”, and somehow it’s always able to find a solution that doesn’t involve the cruelty that always dictated what I said and what I did.
You can already stop doing good things because you’re surely going to heaven with other golden retrievers but I know you’ll never stop. -
I UNDERSTAND POINTERS (kind of) HAHAHAHA NOW I JUST NEED TO KNOW HOW TO USE THEM AND I WILL BE UNSTOPPABLE15
-
Last Scrum Meeting, set up our new Container Server and installed Sentry (Bug Reporting Tool) on it. I was pretty proud, since it was one of my first DevOps thingies I had to work on. (I may end up as a DevOps Engineer after my Internship) In the scrum meeting, the colleagues just start saying everything with a French accent and just laugh about their french jokes while I'm in the middle of showing them sentry.. they were literally unstoppable... 😡 And weren't paying any attention to my presentation.
-
I can be manipulated. Yes, I’m now more resilient to manipulation than ever because I’m autistically good at recognising patterns, yet I’m not perfect.
For a manipulator, there is just one problem — now and then, my disorder obliterates my entire worldview, together with the foreign manipulative framework, so I can start with a blank slate. It protects me. Yes, this protection is akin to our body’s “we’ll boil all the germs in our own blood” tactic that instead of defining winners and losers only leave survivors, yet the force is unstoppable. You cannot secure the land that is hit by a tornado every three months.
That inner Nemesis is so strong that it even defeated a complex, almost fractal-like manipulation of my own mother that I lived in since birth, leaving her with a wound that will never heal. Wannabe manipulator exes didn’t even stand a chance. I don’t care if that force destroys me or not, as during that time, there is no “me”.
About my mom, long story short, she told me “I want to stop treating my cancer to die as soon as possible just to not see you anymore” after my coming-out. Full story is here:
- part 1: https://devrant.com/rants/4923052/...
- part 2: https://devrant.com/rants/4924040/...7 -
Headsup: if you're making a game, or want to, a good starting point is to ask a single question.
How do I want this game to feel?
A lot of people who make games get into it because they play and they say I wish this or that feature were different. Or they imagine new mechanics, or new story, or new aesthetics. These are all interesting approaches to explore.
If you're familiar with a lot of games, and why and how their designs work, starting with game
feel is great. It gives you a palette of ideas to riff on, without knowing exactly why it works, using your gut as you go. In fact a lot of designers who made great games used this approach, creating the basic form, and basically flew-blind, using the testing process to 'find the fun'.
But what if, instead of focusing on what emotions a game or mechanic evokes, we ask:
How does this system or mechanic alter the
*players behaviors*? What behaviors
*invoke* a given emotion?
And from there you can start to see the thread that connects emotion, and behavior.
In *Alien: Isolation*, the alien 'hunts' for the player, and is invulnerable. Besides its menacing look, and the dense atmosphere, its invincibility
has a powerful effect on the player. The player is prone to fear and running.
By looking at behavior first, w/ just this one game, and listing the emotions and behaviors
in pairs "Fear: Running", for example, you can start to work backwards to the systems and *conditions* that created that emotion.
In fact, by breaking designs down in this manner, it becomes easy to find parallels, and create
these emotions in games that are typically outside the given genre.
For example, if you wanted to make a game about vietnam (hold the overuse of 'fortunate son') how might we approach this?
One description might be: Play as a soldier or an insurgent during the harsh jungle warfare of vietnam. Set ambushes, scout through dense and snake infested underbrush. Identify enemy armaments to outfit your raids, and take the fight to them.
Mechanics might include
1. crawl through underbrush paths, with events to stab poisonous snacks, brush away spiders or centipedes, like the spiders in metro, hold your breathe as armed enemy units march by, etc.
2. learn to use enfilade and time your attacks.
3. run and gun chases. An ambush happens catching you off guard, you are immediately tossed behind cover, and an NPC says "we can stay and fight but we're out numbered, we should run." and the system plots out how the NPCs hem you in to direct you toward a series of
retreats and nearest cover (because its not supposed to be a battle, but a chase, so we want the player to run). Maybe it uses these NPC ambushes to occasionally push the player to interesting map objectives/locations, who knows.
4. The scouting system from State of Decay. you get a certain amount of time before you risk being 'spotted', and have to climb to the top of say, a building, or a tower, and prioritize which objects in the enemy camp to identity: trucks, anti-air, heavy guns, rockets, troop formations, carriers, comms stations, etc. And that determines what is available to 'call in' as support on the mission.
And all of this, b/c you're focusing on the player behaviors that you want, leads to the *emotions* or feelings you want the player to experience.
Point is, when you focus on the activities you want the player to *do* its a more reliable way of determining what the player will *feel*, the 'role' they'll take on, which is exactly what any good designer should want.
If we return back to Alien: Isolation, even though its a survival horror game, can we find parallels outside that genre? Well The Last of Us for one.
How so? Well TLOU is a survival third-person shooter, not a horror game, and it shows. Theres
not the omnipresent feeling of being overpowered. The player does use stealth, but mostly it's because it serves the player's main role: a hardened survivor whos a capable killer, struggling through a crapsack world. The similarity though comes in with the boss battles against the infected.
The enemy in these fights is almost unstoppable, they're a tank, and the devs have the player running from them just to survive. Many players cant help but feel a little panic as they run for their lives, especially with the superbly designed custom death scenes for joel. The point is, mechanics are more of a means to an end, and if games are paintings, and mechanics are the brushes, player behavior is the individual strokes and player emotion is the color. And by examining TLOU in this way, it becomes obvious that while its a third person survival shooter, the boss fights are *overtones* of Alien: Isolation.
And we can draw that comparison because like bach, who was deaf, and focused on the keys and not the sound, we're focused on player behavior and not strictly emotions.1 -
My power supply project is almost completely done (it's in a working state but still needs some finishing touches) but I procrastinated with it for nearly 2 weeks. The reason being that the next step (making a side panel and soldering some 3600W AC lines to the ones inside of the unit) fucking sucks. I've done that soldering of 4 wires (3 inside lines, 1 coming in from the outside) before, and I honestly can't think of many things that I've cursed and sworn on as frantically as I did on this. This time of course being no different, plus some unstoppable coughing and stuffed nose, just because my body felt like acting up. Can't say that I had a good time.
But that's not really the point of this.. it's more about the procrastination part. It isn't really procrastination as in just being too lazy to get around doing something, is it? It's more like the reluctance to do something that you know is going to suck really bad. And even now I've only quarter-assed it (well probably half-assed, quarter-assed would've been the crocodile wires between the inner and outer AC lines.. just dangling on the floor, waiting for someone to step on.. beautifully dangerous, deadly almost.. just the way I like it :3)... Anyway, how do you get the "umpf" to do something that you really dislike and don't want to do, without waiting for 2 weeks to finally get around doing it?4 -
Speaking about porn blocking on linux, how can I make a service unstoppable without losing my root privilege? :/4
-
How you fix a noisy ultrabook?
My ears are bleeding now because of this fucker's unstoppable fan.13 -
So how you like opera accepting ipfs crypto domains ?
I just started being interested in it as it might move people to encrypted internet.
You think things like unstoppable domains and metamask are the future of internet ?
I can find anything useful that is on crypto domains right now.2 -
Hitting every. single. fucking. dead end on my unstoppable march to introduce a nice feature.
I'm trying to embed interactive svg maps in a Wordpress page in such a way that the areas can be edited intuitively using Inkscape and all the page does is inline the xml markup, but also there's a JPG background embedded in the picture which Wordpress finds too big for markup (unsurprisingly) but which is a pain in the ass to reference externally.