Just who the fuck from apple thought its a good idea to make the FUCKING SCROLL BAR overlap, the FUCKING PROPERTY ARROWS, everytime i accidentaly hover over it? I cant change shit! I have to wait few seconds every time i accidentaly hover over the scrollbar so i can be able to FUCKING CHANGE the value!

Dear Apple Inc,

Fix your shit! We're paying 100$ a year for what? More bugs and toruture? I didnt sign up for this bullshit! Give us back some real quality products, or just buy the company Jetbrains and let them build the IDE for you instead.

Disabled fucking arrows keys in vim. Life is hell now.

I will be posting a lot more rants from now on as I am learning vim so bear with me.

Her: What are you doing over there?
Me: I'm working on cryptographic hash functions
Her: is that really homework?
Me: yes, come look with your two eyes.
Her: ...
Me: crazy stuff, no?
Her: I imagine computer science is really just a lot of boxes and arrows.
Me: *flashback to UML, ERD diagrams, and logic diagrams*
Me: you are not wrong.

Who needs screenshots?

At my first job in a web agency, we had this client who wanted to make some changes to his website and sent them to us by email. So far nothing unusual ... until I opened the email. To show us the changes he wanted to make the guy has done these steps:

1) He took the picture of his PC screen with the smartpone
2) Printed the photo of the screen
3) He made some pencil scribbles on the paper with comments like "Here we change the font, here we change the color" and the arrows that indicated where to move some blocks of the layout
4) Then he scanned the sheet with scribbles and sent it to us as a pdf by email

Of course, all our attempts to explain how a screenshot works have been useless and he went on like this for weeks

Worst experience with cs profs? Oh boy....

Databases lab: "You'll need to work of this snippet, if your IDE tells you it's deprecated you don't need to care about it"
If you want to imagine the quality of the code base we were expected to work upon just think about that attached xkcd comic, basically an undecipherable black box.

The instructions where at the same time micro managing everything (he gave us frickin variable names to use, and no good ones, no the database connection had to be called datbc, yeah very descriptive) and yet so obfuscated that I'm not completely sure he didn't resurrect Kant himself to ghostwrite for him.

He also didn't like us to use any Java feature that was to 'modern', for example for each loops since "they offer no benefit over normal for loops".

Further, everything we wrote had to be documented with a relationship diagram and a uml. So far no problem if he hadn't invented his own flavor of both (which can be read about in his book).
Oh, and he almost failed me because I used a lambda expression in his 'code on paper' exam and this "arrows are a C command" I "must have been confused"... which is glorious coming from the guy who can't get operators and commands straight.

We have a Miro collaborative whiteboard where product managers map functionality and user flows.

It currently has 89442 post-its & arrows.

know what pisses me the fuck off? when the manager of another department jumps over me and goes straight to the head of my department for a request that they want from MY department.

Currently, there are 2 stupid bitches that insist on doing this fuckery. One of them keeps getting owned by our DBA since for whatever reason she sends her requests to me, just for the DBA to remind her that I ain't giving her access to shit and bla bla

The other is the head of the human resources department. It goes like this: sends wrong data, task gets delayed cuz we have to sort her shit, gets impatient, bitches at head of department and his boss about us taking long(bitch 3 hours ain't long and your shit ain't critical) just for me to reply back with images and LOOK FUCKTARD YOU MESS THIS UP red arrows showing how what she did was wrong and I had to fix it for her.

Sends a reply back only to me saying thanks, ah no pendeja, I will forward aaaaaaall of that shit to everyone else, tried throwing me under the bus? well now ima do it to you.

And fuck those 3 applications you requested, have fun adding shit manually through spreadsheets and then go eat shit and die.

Vim is super easy, guys! You don't use arrows to navigate around the text, that's too obvious! Instead you use HJKL keys, because it goes Hup, Jleft, Kright and Ldown. You can also use B to go Beginning and E to go to End of the word, oh and W to go to the WstartOfNextWord.

TL;DR Developers don't like it when marketing attempts to do their job. They like it even less when they have to clean up the mess when they fuck things up.

Our marketing team was specifically told not to put JS into the CMS. They were told that if you need JS for something, we will do it and then work it into a release. That wasn't good enough so they hired a design firm to "hack" the JS inline. They found a back door to get the JS in place but couldn't get it to work right. They called me to come look at it. After 5 minutes of explaining why they shouldn't have done what they did, I grudgingly decided to look at the JS. 30 seconds later I fixed what they had been screwing with for about 8 hours. They were using --> arrows in their comments! Seriously?!? designer != developer

I'm making an educational game for a school project.

What I thought I had to do:
Write complex code
Learn to animate
Make all resources by myself

What i do:
Drag and drop stuff into unity.
Moving arrows around.
Watch tutorials.

Im 3 weeks ahead of my planing... After 6 days.

No wonder there are so many 3rd class unity games

how i started training myself with Up/Down/Left/Right arrows in mid 90's.

Love it when testers loose there shit and take loads of screenshots, arrows everywhere, the lot...
But no explanation of what they are actually trying to show.
😂

I found this on a wiki with Haskell Humor... it's interesting...

How to Shoot Your Self in the Foot With Haskell: Putting the unsafe in unsafePerformIO!

You shoot the gun, but the bullet gets trapped in the IO monad.
Couldn't match expected type 'Deer' against inferred type 'Foot'.
While compiling your program the compiler produces a type error long enough to overflow a kernel buffer, overwrite the trigger control register and shoot you in the foot.
After trying to decipher the type errors from the compiler, your head explodes.
After you've finally found a way to circumvent the type system and shoot yourself in the foot, Oleg appears out of nothing and shoots you in the foot for coming up with it before him.
You shoot the gun but nothing happens (Haskell is pure, after all).
Your foot is fine, until you try to walk on it, at which point it becomes mangled.
You have a shootFoot function which you've proven correct. QuickCheck validates it for arbitrary you-like values. It will be evaluated only when you end up at the hospital. You hope this doesn't come to pass, as it actually returns a bullet-ridden copy of yourself and you don't want to be garbage-collected.
foreign import ccall "shootparts.h shootfoot" shoot_foot :: Gun -> Programmer -> IO ()
shootSelfInFoot = unsafePerformIO . shoot . foot $ self -- Shoot self in foot 0 or more times depending on evaluation order
No instance for (Target Foot)
arising from use of `shoot' at SelfInflictedInjury.hs:1:0
Possible fix: add an instance declaration for (Target Foot)
In the expression: shoot foot
You go to shoot yourself in the foot but the bullet is in the ST monad and the gun is in the IO monad, so you can't.
You ask Haskell to shoot you in the foot but by the rules of lazy evaluation you don't need the result yet so it doesn't happen.
You decide to shoot yourself in the foot but get distracted devising a ballistics algebra and wondering if you can do the calculations in the type system.
You want to shoot yourself in the foot but realize there is no Gun datatype so use Arrows instead.
You shoot in the direction of your foot, but since you are inside the STM monad you can just retry until you figure out what to do.
You shoot yourself in the foot, but you are perfectly fine as long you just don't evaluate the foot.
You shoot yourself in the foot, but nothing happens unless you start walking.
Don't forget about memory consumption! If you don't look, the bullet causes heap overflow. If you look, the bullet causes stack overflow.
You *appear* to have deliberately shot yourself in the foot, and yet your program actually runs perfectly OK due to lazy evaluation. (So long as you remember to not look at your foot...)
You aim the gun at your foot, pull the trigger and remove the clip. When you look at your undamaged foot, the hammer clicks on an empty barrel.

Noticed how contrast between the active and inactive arrows in the new chrome update is so low that you can hardly make out if it's clickable or not?

Oliver queen ------Arrows

I often read articles describing developer epiphanies, where they realized, that it was not Eclipse at fault for a bad coding experience, but rather their lack of knowledge and lack of IDE optimization.

No. Just NO.

Eclipse is just horrendous garbage, nothing else. Here are some examples, where you can optimize Eclipse and your workflow all you like and still Eclipse demonstrates how bad of an IDE it is:

- There is a compilation error in the codebase. Eclipse knows this, as it marks the error. Yet in the Problems tab there is absolutely nothing. Not even after clean. Sometimes it logs errors in the problems tab, sometimes t doesn't. Why? Only the lord knows.

- Apart from the fact that navigating multiple Eclipse windows is plain laughable - why is it that to this day eclipse cannot properly manage windows on multi-desktop setups, e.g. via workspace settings? Example: Use 3 monitors, maximize Eclipse windows of one Eclipse instance on all three. Minimize. Then maximize. The windows are no longer maximized, but spread somehow over the monitors. After reboot it is even more laughable. Windows will be just randomly scrabled and stacked on top of each other. But the fact alone that you cannot navigate individual windows of one instance.. is this 2003?

- When you use a window with e.g. class code on a second monitor and your primary Eclipse window is on the first monitor, then some shortcuts won't trigger. E.g. attempting to select, then run a specific configuration via ALT+R, N, select via arrows, ALT+R won't work. Eclipse cannot deal with ALT+R, as it won't be able to focus the window, where the context menus are. One may think, this has to do with Eclipse requiring specific perspectives for specific shortcuts, as shortcuts are associated with perspectives - but no. Because the perspective for both windows is the same, namely Java. It is just that even though Shortcuts in Eclipse are perspective-bound, but they are also context-sensitive, meaning they require specific IDE inputs to work, regarldless of their perspective settings. Is that not provided, then the shortcut will do absolutely nothing and Eclipse won't tell you why.

- The fact alone that shortcut-workarounds are required to terminate launches, even though there is a button mapping this very functionality. Yes this is the only aspect in this list, where optimizing and adjusting the IDE solves the problem, because I can bind a shortcut for launch selection and then can reliably select ant trigger CTRL+F2. Despite that, how I need to first customize shortcuts and bind one that was not specified prior, just to achieve this most basic functionality - teminating a launch - is beyond me.

Eclipse is just overengineered and horrendous garbage. One could think it is being developed by people using Windows XP and a single 1024x768 desktop, as there is NO WAY these issues don't become apparent when regularily working with the IDE.

to space, or to tab,
that is the question,
whether tis nobler to suffer
the slings and arrows
of outrageous space bar use
pressing four or eight times,
or to take arms against a sea of
manual spaces by using
the tab key, and by apposing
space bar's end them.

How do you draw arrows for cli apps?

-->
->
~~>
~>
insertarrowhere>

today is the day i will write a bunch of passive agressive redmine tasks with fucking steps to reproduce the fucking bugs and fucking info on the fucking environment of the fucking bug! i mean you have the time and skills to attach bunch nonsence screenshots with color coded arrows and circles, carefully cropping out info i could actually use, like the fucking url and browser, but you cannot consolidate your thoughts well enough to write down the steps that led to a bug??? fuck these people

Lua users, have you used moonscript?

It's a little language that has it's own interpreter or can be compiled down to Lua and it's absolutely lovely (currently using it with Love2d).

Of course, as with most things, what I love about it also royally pisses me off sometimes.

For starters local has to be declared for variables, unlike lua.
Otherwise the variable goes to _
Also note, that some tutorials literally tell you the opposite.

all variables are local by default
unless you don't declare them
then they go to _ (throwaway)
Some tutorials get this wrong too.

all variables have to be declared local
except tables. failure to declare a table WITHOUT a local will cause things like
table.insert to fail with "nil" values for no god damn reason.
No tutorial I could find mentioned this.

Did you know we call methods with '\'?
By the way, we call methods with '\'.
Why? Who the fuck knows.
Does make writing web routes more natural though.

Variables in the parameters of new are declared and bound for you. Would have loved to know this before hand instead of trying
to bind to them like a fucking idiot.

Fat arrows are used to pass in self for methods.
Unless you're calling a method. Then you use backwards slash. This fact is unhelpful when you're a beginner and dealing with the differences between the *other* arrow, the backslash, the fat arrow, and the fact that functions can be called with or WITHOUT parenthesis.
And on that note..

While learning all this other shit, don't forget parenthesis are optional!
Except when they're not!
..Like when you have a function call among your arguments and have to disambiguate which args belong to the outer call and to the inner call! Why not just be fucking consistent?

But on the plus size, ":" is now used for what it should have been used for in the fucking beginning: binding values to keys.
And on the downside, it's in a language thats built on top of another language that uses it for fucking *method calls*, a completely
different fucking usage.

And better still, to add to that brainfuckery thats lost in the mental translational noise like static on a fucking dialup modem, you define methods with the fat arrow. Wait, was that the single arrow or fat one? Yeah the fat one. Fuck. But not before you do THIS shit..

someShit: =>

yeah, you STILL include the god damn colon just so when you're coming from lua you can do a mental double take. "Why am I passing self twice? Oh right, because fuck me, I decided to use moonscript." It's consistent on that front but it also pisses me off.

A lot of these are actually quality of life improvements disguised as gotchas, but when you're two beers in to a 30 minute headscratcher it sure doesn't fucking feel like it.

Nevertheless, once I moved beyond the gotchas, it was like night and day. Sure moonscripts takes a giant steaming dump all over the lua output, like a schizophrenic alcoholic athena from the head of zeus, but god damn, when it works it just WORKS.

Locals that act like locals? Check.
Sane OOP? Check.
Classes, constructors, easy access to class methods, iterators? Check, check, check, check, check.

I fucking hate ceremony. Configuration over convention is for cunts. And moonscript goes a long ways toward making lua less cunty.
If you've ever felt this way while using lua, please, give moonscript a try.

You'll regret it, but in a good way!

20 years ago, in China, they sold a so-called learning-machine which is a modified version of super Nintendo with a full sized keyboard, you could use it to learn how to type, and play Nintendo games. somehow it supports basic, and the manual book have printed a full code to create a stupid game with you could move a super Mario character with arrows, me and my step brother spend a whole day typed the 40+pages of code and enjoyed the game for 5 mins. BTW you can not save your program. after that I think it is so cool to create vedio games by programming.

Somehow managed to create my own theme for my IDE. Unfortunately didn't implement the highlight feature for semicolons, arrows, comma etc. (totally forgot about it)
Applied it super excitedly and started writing code.
Some lines later a simple loc generated error. Spent nearly 5 hours on fixing the issue. Later realized what was actually missing.
Fuck my life.

"Instead of shooting arrows at somebody else’s target… I make my own target around wherever my arrow has happened to have landed." - Brian Eno

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?

So I'm learning Vim at the moment... and one thing that bugs me is that the navigation arrows are h,j,k,l.
On the german keyboard layout, when I use the 10-finger-system, my right hand is in this constellation: forefinger on j, middle finger on k, ring finger on l, and little finger on ö.
So wouldn't it be better if the navigation would be j,k,l,ö instead of h,j,k,l?
Or is this different in english keyboard layout?
I'm confused 🤔

By far the most stupid email I ever got was a feedback to a documentation paper that I wrote.

The email's author went on a rant for long paragraphs, suggesting how the content should be structured, written, pictures suggestions ("something like a box with arrows" kind of description) only to realize, I guess in the middle of writing the email, that my approach was much more user friendly, easier to understand and to follow.

So, after this looong rant the email basically ends with "I see what you did there; forget what I wrote before. Cheers."

My brain stopped for that day. It couldn't handle it.

I bought BMW recently and the engineers who designed it did a phenomenal job. The one oddity though, there are up and down arrows on the steering wheel representing next and previous, except that down is next and up is previous. It's so counter intuitive and I wish they would standardize button interfaces or produce guidelines everyone would stick to.

I use a DasKey Ultimate with blank keycaps at work and people always ask how the hell I can work with that board. I recently bought a Happy Hacking Pro for my tablet/laptop and I must ask the same question to those who daily drive these..

How the fuck do you deal with this retarded layout??

I used the dip switches to at least change the Del to BS but the physical key is stupid small, the control key position is just idiotic and no dedicated arrows? I use VIM and my work desktop is Linux and I come from a UNIX background. Still makes no sense.

</rant>

[Long rant about one of the worst school project I got]
I just saw that post about Lego coding, and it reminds me a project we had to do for high school.

The project was about a robot that will do volleyball services. My group decided with me that I should go on programming the robot since it was my idea to pick that subject to work on. So I started to investigate the robot and the programming software.

This was one of the worst thing si could get. For some reason I didn't find any tutorial about how to program the robot, so I had to test it out. When you don't want to break the robot, that's clearly not the best thing to do.

So what about the teachers? We had 3. Two told me they don't know stuff about this, and one MIGHT know stuff but not how to use the software. Great...
Plus I add that we were asking a teacher some help, being desperate, and literally, he came, made a joke about "how long he didn't play with Lego toys", laughed at his own joke and left. Thank you, that was really helpful while I was worrying about the project that will help us getting my degree, clearly helped us.

So I managed to do something really basic, where you input the direction for the aim with the arrows on the robot, and central button was for shooting. Basically basic stuff. Even not optimal because the robot hit its own screen but a weaker throw wasn't working, so we had to put some protection over the screen and the arm.

Another group of another class were working on the same subject, so we visited them one day to see their stuff.
They made a joystick that was fully operational, with analogic direction input, precise aiming and shooting stuff. The best way to make myself doubt about my stuff.

So we did the presentation and for whatever reason, the other class (not only the other group) got bad reviews of their projects, made by my famous joking teacher, and we got a good review. Didn't understand, but whatever.

So did I learn stuff?
Absolutely not. It was one of the worst pain in the ass to learn the programming syntax and stuff, and when I graduated, I forgot anything concerning programming stuff, my engineering school did all the stuff.

This is some experience you don't forget, the one that don't make yourself grow at all but the effort is real.

"Instead of shooting arrows at somebody else’s target… I make my own target around wherever my arrow has happened to have landed." - Brian Eno

So, I work as a sysadmin junior (6 months and going), and in the past few months, I learned what my boss warned me about - Devs don't understand us admins, and we don't understand the devs.

We have this huge client who is about to migrate to our company (We do mostly server managment/Housing/Renting), and I am so gald I don't have to work on the migration myself!

Just hearing what the company devs say makes me facepalm: No, it won't work. It cannot work on just 3 machines (They use like... 20 in total), no, we won't get rid of our docker swarm, that's essential (Doing the absolute minimum in their infrastructure, just a fancy buzzword to lure people on. Though they've spent like 2 years developing the app that uses it, so they my not want to give it up).

I kid you not, once, they replied to an email that contained the phrase "To be afraid of/worried about" something during the migration, that something could break, not work, be unstable. 7 times.

Might not sound as bad, but it was a rather short mail, and when they're so afraid of everything, its kinda hard to cooperate with them.

My colleague literally spent this entire week mapping out /their/ infrastructure, because they were unable to provide us with the description themselves.

And as a cherry on top, they sent us a "graph" of relationships of all the parts of their infrastructure that was this jumbled mess of rectangles and arrows. Oh, and half of all the machines were not even in the graph at all! Stating that "We also have all this, but I really don't know how to ilustracte the interactions anymore"

Why do companies like that exist? If you build an infrastructure yourself, shouldn't at least someone know exactly how it works?

!rant

PHP guys, your equivalent to the dot operator looks weird to me with no whitespace, anybody else spaces out their arrows like this?

my requirements:
1. Able to create object with an event i.e click
2. Able to drag and move the object
3. Able to label it (for circle : inside it, for arrow: mid length)
4. Able to make double circle when specified event occurs,
5. Able to draw arrows from one object to other object or to self, and can also label the arrow.

Which technology stack should I use for this kind of requirements. doesn't matter desktop or web-applications.

Title: Error Popup Occurs --> To be discussed

Description: When I open the app -> I see the app screen -> then I see some text -> sometimes there is a popup showing an error message

We of course don't want any errors at all so we should hinder these error messages

No, this isn't parody, arrows and all its how some people write our tickets, why do they write it this way!?!? Where is the value!!?!? Where is the comprehension!?!?!? God I get so sick of it sometimes.

Just searched: "sketch app arrows are ugly as shit" - but nothing came up...