wk87 is a dangerous topic for me, i've been through a lot. I apologise for what I am about to inflict on this network over the coming week.

Most incompetent co-worker, candidate 1, "T".

T was an embedded C developer who talked openly about how he's been writing code since he was 14, knew all the C system libraries and functions like the back of his hand. For the most part, he did ... but not how to actually use them, as (based on his shocking ... well everything) he was inflicted by some sort of brain disorder not yet fully understood by medical science. Some highlights:

- Myself and the CTO spent 4 days teaching him what a circle buffer was and how to build one.
- His final circle buffer implementation had about 3 times as much code as he actually needed.
- When the code was running too slowly on the device, we didn't try find any performance improvements, or debug anything to see if there was anything taking too long. No not with T, T immediately blamed TCP for being inefficient.
- After he left we found a file called "TCP-Light" in his projects folder.
- He accused the CTO of having "violent tendencies" because he was playing with a marker tossing it up in the air and catching it.
- He once managed to leave his bank statements, jumper and TROUSERS in the bathroom and didn't realise until a building wide email went out.
- He once .... no hang on, seriously his fucking trousers, how?
- He accused us all of being fascists because we gave out to him for not driving with his glasses, despite the fact his license says he needs to (blind as a bat).

... why were his trousers off in the first place? and how do you forget ... or miss the pile of clothes and letters in a small bathroom.

Moving on, eventually he was fired, but the most depressing thing of all about T, is that he might not even be top of my list.

Tune in later for more practiceSafeHex's most incompetent co-worker!!!

What issue did you FUCKING fix!!?

Starting to use the Devrant face in my log messages

This facts are killing me

"During his own Google interview, Jeff Dean was asked the implications if P=NP were true. He said, "P = 0 or N = 1." Then, before the interviewer had even finished laughing, Jeff examined Google’s public certificate and wrote the private key on the whiteboard."

"Compilers don't warn Jeff Dean. Jeff Dean warns compilers."

"gcc -O4 emails your code to Jeff Dean for a rewrite."

"When Jeff Dean sends an ethernet frame there are no collisions because the competing frames retreat back up into the buffer memory on their source nic."

"When Jeff Dean has an ergonomic evaluation, it is for the protection of his keyboard."

"When Jeff Dean designs software, he first codes the binary and then writes the source as documentation."

"When Jeff has trouble sleeping, he Mapreduces sheep."

"When Jeff Dean listens to mp3s, he just cats them to /dev/dsp and does the decoding in his head."

"Google search went down for a few hours in 2002, and Jeff Dean started handling queries by hand. Search Quality doubled."

"One day Jeff Dean grabbed his Etch-a-Sketch instead of his laptop on his way out the door. On his way back home to get his real laptop, he programmed the Etch-a-Sketch to play Tetris."

"Jeff Dean once shifted a bit so hard, it ended up on another computer. "

This is just my token of appreciation for the Skype devs. Can't begin to say how much I hate it. Your android app is a joke even after a host of updates, your desktop client is an even bigger joke (atleast Linux Beta version, I know betas aren't supposed to be stable but this is ridiculous).

You have reinvented chat clients to be extremely bulky, cumbersome and very hard to sync across devices. And you have managed to make it "buffer" more than a YouTube video does on a 2G network. I for one, am blown over by how you did that. And to top it all, you can't close the client on Linux atleast! All you did is just override the close button so that it only minimises it. Brilliant piece of work right there!

Why the hell can't you just close the client and run it in the background the proper way like everyone else does? Why does it have to take 20 *** seconds to open a message? The only reason I am stuck with this is some wierdos in the office still only use this. Get your shit together 😡

Ahh.. I feel much better now.

A guide to estimations.

1) don’t give an immediate answer. The first “timeframe” you give will be held against you and will result in overtime and working weekends.

2) think of a relevant piece of work and the time that took.

2.1) if it’s something you haven’t done before, add some adequate research time.

3) allow half a day of testing for every day of development.

4) add a day as buffer - this is good for on the fly bug fixes

5) calculate time

6) now give an educated estimate.

7) this should take you 5 seconds to get through mentally.

8) if scope creep occurs: goto:1

Okay WhatsApp, as if I didn't have enough reasons to uninstall you anyway.

someone tell a programmer at Steam to up the vertex buffer size 😹

FUCK YOU PHP!!!! FUCKING HELL JUST FUCK THE HELL OFF YOU PIECE OF SHIT.
8 GOD FORSAKEN HOURS SPENT TRYING TO ZIP SOME SHITTY FUCKING FILES IN A FOLDER ON MY WEB SERVER TO HAVE THEM DOWNLOADED TO MY CLIENT COMPUTER.... 8 HOURS UNABLE TO OPEN THE DAMN FILE AND THE ISSUE WAS "echo" & "print_r()" STATEMENTS GETTING TRAPPED IN MY ZIPARCHIVE BUFFER MAKING THE ZIP FILE A GIANT PILE OF UNREADABLE SHIT.
HOW IN GODS NAME WERE THOSE FUCKERS EVEN BEING ADDED TO THE ZIP FILE.

Fucking hell. Time to sleep.

Hey guys, first rant,

At the moment I'm developing a very big and complex app. We are almost done and decided to deliver a test version to our customer. After he received our test he called us and said there is a problem with a function, he just said it's not working and wasn't very specific.

So I decided to check his problem, because an colleague couldn't figure it out.
I started the app via android studio and had a similar problem, there was a huge delay at the automatic recording function of Bluetooth messages, I thought yeah this is his problem.
I showed it my colleague and he said that he doesn't have this problem, we have different Bluetooth simulators so we thought that there must be a problem with the Bluetooth communication or the simulators are broken.
I checked if there is some kind of timing or buffer problem and logged the shit out of the simulator and found nothing, 3 hours were lost🏁.

My colleague checked his last changes because he had changed a lot at the App Api do to new conditions and those customer wishes💀 he couldn't found anything. So we thought maybe it's my device and the device of the customer. We switched the devices and tada no problem with my devices if the app is builded at the pc of my colleague.

I thought ok maybe it's because I turned some ndk features off. Turned it back on, nothing happened. So we exchanged our Android Studio Settings but no difference. So I said yeah whatever my mashine is just fucked. I restarted my mashine for the third time and started android fucking studio. Some little popup showed up "new updates"... the solution came to my mind ... Do to an update of android studio I excidently turned on Instant Run.....🌋 . I checked it, it was activated, these fucking instant run, great idea but not working... Turned it off, everything worked.
I called the customer because he can't have a problem and he said, this time not angry, oh yeah it was just a notification if I want to turn on my Bluetooth and I decided no and the Bluetooth recording is not recording, this is a problem... -😠NO FUCKING COMMENT😤-

Someone on a C++ learning and help discord wanted to know why the following was causing issues.

char * get_some_data() {
char buffer[1000];
init_buffer(&buffer[0]);
return &buffer[0];
}

I told them they were returning a pointer to a stack allocated memory region. They were confused, didn't know what I was talking about.

I pointed them to two pretty decently written and succinct articles, the first about stack vs. heap, and the second describing the theory of ownership and lifetimes. I instructed to give them a read, and to try to understand them as best as possible, and to ping me with any questions. Then I promised to explain their exact issue.

Silence for maybe five minutes. They disregard the articles, post other code saying "maybe it's because of this...". I quickly pointed them back at their original code (the above) and said this is 100% an issue you're facing. "Have you read the articles?"

"Nope" they said, "I just skimmed through them, can you tell me what's wrong with my code?"

Someone else chimed in and said "you need to just use malloc()." In a C++ room, no less.

I said "@OtherGuy please don't blindly instruct people to allocate memory on the heap if they do not understand what the heap is. They need to understand the concepts and the problems before learning how C++ approaches the solution."

I was quickly PM'd by one of the server's mods and told that I was being unhelpful and that I needed to reconsider my tone.

Fuck this industry. I'm getting so sick of it.

Best of luck to all Ukrainian ranters. Buffer states are awful places to be.

Got a new 4k smart TV. But internet to slow to buffer YouTube videos at 4k.

At a party.
Everyone dancing like crazy.
And I'm here devRanting.

Updating from Swift 2 to 3 using Xcode's "migration assistant"

Did 2 important tasks today:
- Registered on devRant
- Uninstalled Whatsapp

Just double buffered the Windows console. What you are seeing here is two buffers: one which is empty, and one which has the text "Hello world!", and a pause of 1 second between buffer swapping.

This enables accelerated rendering in the Windows command line (By rendering to an off-screen buffer then simply swapping the active buffer), making things like advanced terminal applications in the Windows console possible.

And the best part- this is the first compilation of the project. Not a single run-time error. What a fucking satisfying accomplishment, honestly.

The solution for this one isn't nearly as amusing as the journey.

I was working for one of the largest retailers in NA as an architect. Said retailer had over a thousand big box stores, IT maintenance budget of $200M/year. The kind of place that just reeks of waste and mismanagement at every level.

They had installed a system to distribute training and instructional videos to every store, as well as recorded daily broadcasts to all store employees as a way of reducing management time spend with employees in the morning. This system had cost a cool 400M USD, not including labor and upgrades for round 1. Round 2 was another 100M to add a storage buffer to each store because they'd failed to account for the fact that their internet connections at the store and the outbound pipe from the DC wasn't capable of running the public facing e-commerce and streaming all the video data to every store in realtime. Typical massive enterprise clusterfuck.

Then security gets involved. Each device at stores had a different address on a private megawan. The stores didn't generally phone home, home phoned them as an access control measure; stores calling the DC was verboten. This presented an obvious problem for the video system because it needed to pull updates.

The brilliant Infosys resources had a bright idea to solve this problem:

- Treat each device IP as an access key for that device (avg 15 per store per store).
- Verify the request ip, then issue a redirect with ANOTHER ip unique to that device that the firewall would ingress only to the video subnet
- Do it all with the F5

A few months later, the networking team comes back and announces that after months of work and 10s of people years they can't implement the solution because iRules have a size limit and they would need more than 60,000 lines or 15,000 rules to implement it. Sad trombones all around.

Then, a wild DBA appears, steps up to the plate and says he can solve the problem with the power of ORACLE! Few months later he comes back with some absolutely batshit solution that stored the individual octets of an IPV4, multiple nested queries to the same table to emulate subnet masking through some temp table spanning voodoo. Time to complete: 2-4 minutes per request. He too eventually gives up the fight, sort of, in that backhanded way DBAs tend to do everything. I wish I would have paid more attention to that abortion because the rationale and its mechanics were just staggeringly rube goldberg and should have been documented for posterity.

So I catch wind of this sitting in a CAB meeting. I hear them talking about how there's "no way to solve this problem, it's too complex, we're going to need a lot more databases to handle this." I tune in and gather all it really needs to do, since the ingress firewall is handling the origin IP checks, is convert the request IP to video ingress IP, 302 and call it a day.

While they're all grandstanding and pontificating, I fire up visual studio and:

- write a method that encodes the incoming request IP into a single uint32
- write an http module that keeps an in-memory dictionary of uint32,string for the request, response, converts the request ip and 302s the call with blackhole support
- convert all the mappings in the spreadsheet attached to the meetings into a csv, dump to disk
- write a wpf application to allow for easily managing the IP database in the short term
- deploy the solution one of our stage boxes
- add a TODO to eventually move this to a database

All this took about 5 minutes. I interrupt their conversation to ask them to retarget their test to the port I exposed on the stage box. Then watch them stare in stunned silence as the crow grows cold.

According to a friend who still works there, that code is still running in production on a single node to this day. And still running on the same static file database.

#TheValueOfEngineers

Damn, credit cards are so fucking secure these days that you hardly can BUY shit with them!
I need some special electronics that I only can get from a vendor in the US, which is overseas. Click click, buy, done. Well no, credit card refused. WTF? Click retry link. No, still refused. FUCK.
Called up the 24/7 hotline of my CC company. Oh yeah, that got blocked by the security system, somehow. We disable that for 20 minutes, just retry. Clicked retry link at the vendor. No failure mail. Hmmm, too good to be true?! Called up the electronics vendor. Yeah should work, stuff is in the warehouse stage. 40 minutes later: credit card declined. FUCK.
Called up the CC company again. Ok, disable blocker for one hour. Nice advice from them, tell the vendor it's only 45 minutes so that there's some buffer. Clicked retry link at the vendor and called them up to make sure that they retry before the time runs out.
LO AND BEHOLD, I could finally pay the shit!!

Starting a new project in a new company. After 4 hours of training and receiving all kinds of new information another collegue passes by and says:

"Hey! So where are you from?"

"I... Don't know..."

Running nano inside a terminal emulator buffer inside vim 8)

Yesssssssssssssssssssssssssssss, finally!

After months of searching for a damn bug I've finally found it in a 5h session. People increasingly started to worry whether this bug has been introduced because of a recent update of the programming language, but I finally found the bug in a dependency. Nobody thought it would be the dependency, because it wasn't updated in 9 months, but it seems like the update improved the networking a tiny bit, whiche caused a buffer to load a second mesage sooner than expected.

I can finally work on my side project again!
Fucking finally!

The GashlyCode Tinies

A is for Amy whose malloc was one byte short
B is for Basil who used a quadratic sort
C is for Chuck who checked floats for equality
D is for Desmond who double-freed memory
E is for Ed whose exceptions weren’t handled
F is for Franny whose stack pointers dangled
G is for Glenda whose reads and writes raced
H is for Hans who forgot the base case
I is for Ivan who did not initialize
J is for Jenny who did not know Least Surprise
K is for Kate whose inheritance depth might shock
L is for Larry who never released a lock
M is for Meg who used negatives as unsigned
N is for Ned with behavior left undefined
O is for Olive whose index was off by one
P is for Pat who ignored buffer overrun
Q is for Quentin whose numbers had overflows
R is for Rhoda whose code made the rep exposed
S is for Sam who skipped retesting after wait()
T is for Tom who lacked TCP_NODELAY
U is for Una whose functions were most verbose
V is for Vic who subtracted when floats were close
W is for Winnie who aliased arguments
X is for Xerxes who thought type casts made good sense
Y is for Yorick whose interface was too wide
Z is for Zack in whose code nulls were often spied

- Andrew Myers

buffer overflow

Uh-oh shit went wrong with umpteen thousand jobs in a pointer heavy, multi-threaded application in raw C. Fuck, some pointer gone wild?!

30 minutes later, after trying to find out how many jobs it takes to start failing. Noticed that it's about the default settings. Wait what? That's where the realloc'ing should kick in, check that.

Aahhhh. Maybe I shouldn't zero the whole buffer after realloc, just the new part. D'uh!

!Rant

Designer decide to have a meeting with stakeholders about UX/UI workflow for control panel of our new embedded system (no framework, no library, gui is bit per bit rendered on frame buffer).
A week later, still nothing on my table, not a mail, not a call. Meanwhile I wrote a framework, the control system, renderer, and messaging queues between tasks.
Wrote some widgets, a layout system and a view swtching mechanism, and a separate stack control to use a "back" button.

Now I am stuck for I do not know what should happen when clicking on various (non obvious) items on the touchscreen.
Fine, I'll ask the designer.

"Oh, I will write the workflow next week" (ETA time, 2 weeks. Seriously? You take a week to draw on Adobe Illustrator 20 screenshot with text and I have another week to write it from scratch in C?)
Ok, while you write it, just tell me what should happen when I click an active item.
"Well, we didn't talk about that. We just decided the colour of the icons on the screen..."
For fuck sake...

I FIXED THE FINAL BUG WITH MY OWN SOLUTION AND NOW IT WORKS, I EVEN SENT MY 5GB FUCKING TXT FILE.

ALTHOUGH IT TOOK FOREVER BECAUSE I FORGOT TO INCREASE THE BUFFER SIZE FROM 1KB SO IT TOOK A BIT.

BUT NOW ALL I NEED TO DO IS POLISH, MAKE SOME QUALITY OF LIFE CHANGES AND I CAN PUT THAT SHIT ON GITHUB!

THIS IS MY SECOND FINISHED PROJECT! But I do gotta thank an online friend that has been teaching me the concepts of network programming without him I couldn’t have done it. Also I’ve learned so much about how shit works thanks to him/and the project.

Agh, holy shit. devRant, I need some love.

I have successfully double-buffered the Windows console (cmd.exe) but all hell breaks loose when you resize the fucking window. The currently active buffer will receive the change in dimensions while the inactive buffer will not, resulting in the window quickly oscillating between the two sizes as the buffers change size.

That got me stuck for about a day. Today, I got it sort of working but it wasn't satisfying at all. I can get it to resize LARGER, but if you resize the window SMALLER, the actual buffer inside the window doesn't change size, so scrollbars appear and I have NO IDEA HOW TO FIX THAT. I somehow need to calculate, or use the API to find, the perfect dimensions (In rows and columns) for the console buffer INSIDE the window buffer for them to not have scrollbars.

And I just - -

I cannot gather the energy to do so right now.

I spent hours finding the solution to this bullshit and ONLY SOLVED HALF MY PROBLEM.

And stack overflow isn't exactly helpful. My problem is so specific that nobody even writes comments on the question.

I guess I need to calculate the amount of characters the screen can hold given the font size and the window size, but fuck, that's a lot of work to do just for something that probably won't even work anyways.

Well, off to the code editor again. Time to inevitably waste my time doing something that won't work.

Yay, programming.

My software is safe from buffalo overflow. What about yours? Is it safe from hip overflow too?

Fuck this, fuck that, fuck the buffer, fuck AES, fuck crypto, fuck node-forge, fuck IV and browsers, once I am done with this fucking cryptographic wrapper on both client and server, the first person to say decrypt and Javascript in the same sentence in front of me will get their own dick in their ass. The guy that said mixing computer and crypto was a bad idea was fucking right

C++ application running on Linux. If customer makes a mistake, I log CustomerIsDumb to kernel message buffer.

You may remember a super long time ago I double-buffered the Windows cmd.exe using c++

tl;dr, here it is in c!

Anyways, I was still learning c++ back then. It wasn't my first project in c++ but it was close and I ran into a lot of issues. The thing worked... but only if you didn't touch it.

Here's the same project (With a lot less bells'n'whistles) written in c. I used a different approach this time, and other than my function naming convention (Which, I honestly don't even know if it's bad or not!), I think this is some pretty solid code!

In the image you see the header file (I used as a summary of the code) and then three x's in a terminal. To do this, the code:

-Creates a ConsoleScreenBuffer handle
-Creates two CHAR_INFO buffers for drawing & displaying
-Draws three x's to the draw buffer
-Copies the draw buffer to the display buffer
-Copies the display buffer to the ConsoleScreenBuffer handle

I'm thinking about cutting out the middle man and removing the display buffer (which holds what is currently displayed) but I think it may actually be useful, and I don't know.

Anyways, I have no friends that understand this stuff so that's why it's here. Cheers.

HTML without CSS be like

nearly cried.

I had been working on this file for the last 4 or so hours.

And accidentally deleted it with NerdTree (mdy).

300 loc. poof.

scoured internet for recovery procedure.

and.......
... to no avail. just about to give up.

here comes the climax: .....

It was stillllll...... in the NEOVIM. BUFFER.
vim got my back.

praise you vim lord.

#vim_pope

Java dev here. I rewrote an app and replaced a system call to ssh with a modern jaxrs post for uploading a file and (new) some additional data.
I even used a stream.

1 hour in production, first client doesn't get his file. Log says OutOfMemoryError: heap.

Me: wtf? I already use streams.
Looking at the Jersey library. Docs say nothing. An issue from 2013 says: oh if you silly don't use the Apache httpclient addon, we disable chunking and buffer the whole body, because our tests fail with the jdk included http client otherwise.

Me: meh.

No warning in the logs. Thank you soooooo much! Who could have known?

Yeaaahhh that moment when the program flawlessly crunches through ten thousands of files, only limited by the slowish HDD! :-)

In full multi-threading, tons of dynamic buffer resizing, pointer shit left and right, also two star programming, and everything written in raw C!

I think my ISP has been a little sneaky cum gargler. Nothing wanted to stream properly for awhile now. When even youtube struggles shit is wrong.

Installed protonvpn now and by the power of some magical internet ball bag the internet came forth and is streaming at 720p no buffer even required and from a not so glorious server.

did they try to keep me blind? Not no more I have wiped that jizz off my face.

Buffer usage for simple file operation in python.

What the code "should" do, was using I think open or write a stream with a specific buffer size.

Buffer size should be specific, as it was a stream of a multiple gigabyte file over a direct interlink network connection.

Which should have speed things up tremendously, due to fewer syscalls and the machine having beefy resources for a large buffer.

So far the theory.

In practical, the devs made one very very very very very very very very stupid error.

They used dicts for configurations... With extremely bad naming.

configuration = {}
buffer_size = configuration.get("buffering", int(DEFAULT_BUFFERING))

You might immediately guess what has happened here.

DEFAULT_BUFFERING was set to true, evaluating to 1.

Yeah. Writing in 1 byte size chunks results in enormous speed deficiency, as the system is basically bombing itself with syscalls per nanoseconds.

Kinda obvious when you look at it in the raw pure form.

But I guess you can imagine how configuration actually looked....

Wild. Pretty wild. It was the main dict, hard coded, I think 200 entries plus and of course it looked like my toilet after having an spicy food evening and eating too much....

What's even worse is that none made the connection to the buffer size.

This simple and trivial thing entertained us for 2-3 weeks because *drumrolls please* none of the devs tested with large files.

So as usual there was the deployment and then "the sudden miraculous it works totally slow, must be admin / it fault" game.

At some time it landed then on my desk as pretty much everyone who had to deal with it was confused and angry, for understandable reasons (blame game).

It took me and the admin / devs then a few days to track it down, as we really started at the entirely wrong end of the problem, the network...

So much joy for such a stupid thing.

May the people responsible for the decision to let Windows 10 wake up people's PCs from sleep mode in the middle of the night to install patches and then force-restart be tortured for eternity in hell. All of the hells. Of every religion. At the same time. While having to stare at a Windows ME bluescreen of death without the ability to blink or look away. For 65535 eternities. Followed by a buffer overflow.

Just got an amazing lecture by text from a university mentor of mine on some of the coolest shit to do with cat in linux, and why you can do things like open a shell with cat /bin/sh (or in my case, use it to stall a program and keep open a shell in a simple buffer overflow task).

God bless all you mentors out there who take the time to explain exactly how all this stuff works. It feels so good to have an idea on the mechanisms on "WHY" something works, not just that it does and that you should use it. As someone new, it makes all the difference.

Rust, because if we can eliminate all security issues because of buffer overflows or other memory-related problems without a GC and still be as fast as with C, that would be pretty dope for everyone.

Everyone and their dog is making a game, so why can't I?
1. open world (check)

2. taking inspiration from metro and fallout (check)

3. on a map roughly the size of the u.s. (check)

So I thought what I'd do is pretend to be one of those deaf mutes. While also pretending to be a programmer. Sometimes you make believe
so hard that it comes true apparently.

For the main map I thought I'd automate laying down the base map before hand tweaking it. It's been a bit of a slog. Roughly 1 pixel per mile. (okay, 1973 by 1067). The u.s. is 3.1 million miles, this would work out to 2.1 million miles instead. Eh.

Wrote the script to filter out all the ocean pixels, based on the elevation map, and output the difference. Still had to edit around the shoreline but it sped things up a lot. Just attached the elevation map, because the actual one is an ugly cluster of death magenta to represent the ocean.

Consequence of filtering is, the shoreline is messy and not entirely representative of the u.s.

The preprocessing step also added a lot of in-land 'lakes' that don't exist in some areas, like death valley. Already expected that.

But the plus side is I now have map layers for both elevation and ecology biomes. Aligning them close enough so that the heightmap wasn't displaced, and didn't cut off the shoreline in the ecology layer (at export), was a royal pain, and as super finicky. But thankfully thats done.

Next step is to go through the ecology map, copy each key color, and write down the biome id, courtesy of the 2017 ecoregions project.

From there, I write down the primary landscape features (water, plants, trees, terrain roughness, etc), anything easy to convey.
Main thing I'm interested in is tree types, because those, as tiles, convey a lot more information about the hex terrain than anything else.

Once the biomes are marked, and the tree types are written, the next step is to assign a tile to each tree type, and each density level of mountains (flat, hills, mountains, snowcapped peaks, etc).
The reference ids, colors, and numbers on the map will simplify the process.

After that, I'll write an exporter with python, and dump to csv or another format.

Next steps are laying out the instances in the level editor, that'll act as the tiles in question.
Theres a few naive approaches:

Spawn all the relevant instances at startup, and load the corresponding tiles.

Or setup chunks of instances, enough to cover the camera, and a buffer surrounding the camera. As the camera moves, reconfigure the instances to match the streamed in tile data.

Instances here make sense, because if theres any simulation going on (and I'd like there to be), they can detect in event code, when they are in the invisible buffer around the camera but not yet visible, and be activated by the camera, or deactive themselves after leaving the camera and buffer's area.

The alternative is to let a global controller stream the data in, as a series of tile IDs, corresponding to the various tile sprites, and code global interaction like tile picking into a single event, which seems unwieldy and not at all manageable. I can see it turning into a giant switch case already.

So instances it is.

Actually, if I do 16^2 pixel chunks, it only works out to 124x68 chunks in all. A few thousand, mostly inactive chunks is pretty trivial, and simplifies spawning and serializing/deserializing.

All of this doesn't account for
* putting lakes back in that aren't present

* lots of islands and parts of shores that would typically have bays and parts that jut out, need reworked.

* great lakes need refinement and corrections

* elevation key map too blocky. Need a higher resolution one while reducing color count
This can be solved by introducing some noise into the elevations, varying say, within one standard div.

* mountains will still require refinement to individual state geography. Thats for later on

* shoreline is too smooth, and needs to be less straight-line and less blocky. less corners.

* rivers need added, not just large ones but smaller ones too

* available tree assets need to be matched, as best and fully as possible, to types of trees represented in biome data, so that even if I don't have an exact match, I can still place *something* thats native or looks close enough to what you would expect in a given biome.
Ponderosa pines vs white pines for example.

This also doesn't account for 1. major and minor roads, 2. artificial and natural attractions, 3. other major features people in any given state are familiar with. 4. named places, 5. infrastructure, 6. cities and buildings and towns.

Also I'm pretty sure I cut off part of florida.
Woops, sorry everglades.

Guess I'll just make it a death-zone from nuclear fallout.

Take that gators!

HTTPS requests in most languages:

Import a couple of libraries, you may need to install a few as well. It's possible that you will need to initialize and set up the socket. Be sure to specify SSL settings. Create the connection, provide it a URL, and attempt the connection. Read the response, usually in chunks. You may need to manually create a buffer of fixed size, depending on if the language has buffer helper classes or not. You will probably need to convert the input stream response to a string to do anything with it. Close the connection and clean up any buffers used.

HTTPS requests in Python:

import urllib
urllib.YEET()

Writing a truly crossplatform terminal library is the biggest pain in the ass.

And you thought windows was bad. They have a proper API with droves of features, freely allocatable screenbuffers, scrolling on both axes, etc.
Fucking xterm vtxxx compatible piles of shit are the problem.
Controlling kinda works eventhough the feature set is pretty bad. The really fucked up thing is reading values back. They literally get put into the input buffer. So you have to read all the actual user input before that and then somehow parse out the returned control sequence. Of course the user input has to be consumed so I have to buffer it myself. Even better is when you get a response with non printable characters which the fucking terminal will interpret as another control sequence. So when you set a window title to a ansi control sequence it would get executed when queried. Fuck this shit but I'm not giving up. I will tame this ugly, bodged together dragon

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.

Windows decides to finish faulty programs whenever it likes. İt's so annoying, I did just one small mistake in c++. I wrote "new char(length);" instead of "new char[length];" and I have been dealing with this shit for three days. Then I run the program on Linux and boom it failed in the same spot, which I fixed. But in Windows it sometimes runs, sometimes fails or sometimes even fails on unrelated places. Wtf windows? How about security and shit. There was literally a buffer overflow and you still keep running the program. And why GCC didn't even popped a warning. I hate developing c :(

When the Internet starts to slow down near lunch and your music starts to buffer.
Cut my salary in half, but give me music.

Our project at work goes live in 3 weeks.

The code base has no automated tests, breaks very often, has never had any level of manual testing

will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.

We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.

Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.

We have no testing team, or qa team of any sort.

Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.

We don't use any file streams so everything is just shoved in the buffer on the server.

Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.

No one looks at the pull requests, they just click approve so they may as well push directly to master.

Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.

I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.

Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.

No one there understands css properly. Or javascript.

Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.

Our customer facing fe app is not dry because no tests so it was decided it was better this way.

Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.

Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.

Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.

I love Unix systems because everything goes smoothly most of the time but today... Fuck me... I just wanted to see how many lines my script was with "wc - l" but I couldn't remember "m" or "w". 180 degrees separated despair and monotony, although I didn't know it yet. I did "mc - l" first and midnight logged empty ftp buffer to my file. Goodbye Thursday and Fridays work :) I should commit more often.

for your next edition of "TI's constantly been smoking crack since the 80s and has no intention of ever stopping":

the TI-8x calculators have a hardware buffer and an OS-provided buffer for screen data, effectively being an "immediate" buffer in hardware, to be displayed next VBlank, and a "slower" buffer, being what's copied to the "immediate" buffer when the OS decides it's time to update the screen. All well and good, maybe a little weirdly done but all in all makes sense. (You can even define a third buffer in RAM if you need to triple-buffer your shit.)

The problem arises when you use TI-BASIC and try to draw to the screen:
If you do something like, say, draw a circle, you'll notice that it's visibly drawn to the screen one pixel at a time. However, looking through what bits of the SDK I can find, the OS' "draw circle" assembly routine *doesn't update the immediate buffer!*

This means that, in TI-BASIC, the "draw circle" routine doesn't use the ACTUAL circle-drawing routine the OS provides, but instead individually calculates and plots a pixel, then updates the hardware buffer (an ENTIRE 768 bytes are copied EVERY TIME) and waits for VBlank to pass before repeating for the next one. In other words, it's deliberately slow as fuck.

Why? All the drawing commands, outside of like 2 or 3, do this. Why would you deliberately slow down the process of drawing to the screen on a system that you KNEW would be popular for people to code on???

My first task in my current company, a few years ago.

I had to add features to a 10 year old microcontroller-based device written in C.

There was a struct named "global", which held hundreds of other structs that held variables or even more structs.
If one would have printed the structure of this mess it would haven needed several pages.

This "global"-struct was used in every single sourcefile to store and pass data around. Obviously there was no documentation and often useless comments.

Additionally there were a few protocol stacks involved, mainly similar, only differing in one or two protocol layers.
The implementation of the protocol stack was by setting flags in the "global"-struct in every protocol layer and having the application data in a buffer.
The complete telegram with all layer specific data (header, checksums, etc.) was then build at one single point right before sending it, based on the flags and the data buffer.

As there was no chance to reuse protocol layers with this implemenation. Three protocol implementations with special telegram builder existed in parallel, although they were nearly identical.

I needed a fourth variant of the protocol stack, so I had no chance but to make another copy with some minor changes.

But there was a benefit from this task.
As I had to do the software for the successor of this device from scratch I learned for many things how not to do them :-)

I fucking hate this low level programming shit. The fucking buffer overflow attacks and the whole understanding of the system architecture just goes over my mind. Can anyone who has found relatively useful resources be kind enough to refer them to me so my stupid mind can understand that better?

Woo! My first Vulkan window that does buffer swapping (swapchain image presenting in vulkan lingo). It doesn't draw anything yet and still took me 3 days lol

Note that if you try to resize it or minimize it or do basically anything with it the whole application crashes but still

A few years ago I would whine, complain and rant about shitty software, which I knew could be so much better than it was. But I didn't yet write software of my own.

Now I complain about shitty libraries, API's and users. Not much has changed really. And every time I write code, I curse myself, and whoever made this trashpile I have to work with. I curse the user to the moon and beyond for using the program wrong. Funny thing is, exactly the thing I was complaining about (input validation, see earlier rant) is also exactly what no more than 5 minutes after release, a user fucked up with. The bot just does not respond at this point. But fuck these braindead retards for users.

In a few years I expect myself to be complaining about shitty compilers and buffer overflows, segmentation violations, bad coding style (don't make your program a fucking colander kthx), and so on.

Next decade I expect myself to be complaining about physics itself, and why the universe is governed by the laws it's governed by. Whoever this God is, he's a fucking retard. Funny thing is, the signs for it are already there. Electron theory! If only those electrons were positrons, then the math would check out properly. Instead of negative electrons traveling from negative to positive, we'd have positive positrons traveling from positive to negative. At least from what I understand so far, this is still a decade away after all.

The point I'm trying to make is that nothing changes, only my understanding of the world around me does, as I tumble further and further down the rabbit hole. Sometimes I wish I had taken the blue pill... Either complain about others' software or perhaps not give a shit at all. Become one of those filthy users I now despise.

WTF IS WRONG WITH ASSEMBLY LANGUAGE?!
I was just modifying an existing program for adding a sequence of numbers from the data section and through console input. I studied the code and started modifying it one step at a time. I needed to modify it into a multiplication program. So I started by changing the ADD functions, replaced the result and buffer registers with bigger size and thought I completed it. WELL GUESS WHAT? SHIT JUST GIVES ME SEGMENTATION FAULT! NOW I HAVE TO REDO THE WHOLE THING! WHY DOESN'T IT TELL ME WHICH LINE OF THE CODE I FUCKED UP AT?! STUPID NASM COMPILER.

*during sprint planning*
Me: so here are the tickets I'm taking in this sprint. I'll do this first and that second. I'm also keeping some buffer for emergency stuff
Manager: ok, this looks good. I trust you and will let you work in peace unless something important comes up. I won't micro manage you
Also my manager for every fucking day of the sprint: hey man what's up? Ready for sync up call?

THAT'S MICRO MANAGING RIGHT THERE YOU PIECE OF SHIT. YOU COULD CHECK JIRA OR GITHUB OR ASK ME IN STANDUP BUT YOU INSIST ON CALLING AND ASK ABOUT THE TINIEST DETAILS. GO FUCK YOURSELF SERIOUSLY

tfw I get called smart for just helping a lad having a welcome splash from node-canvas buffer.

Well, you sometimes love people giving you gratitude, doesn't it?

So I just fixed about a year or so old bug by removing my solution entirely.

As very few of you will know, I work on/ off on a project called TG which accelerates cmd.exe

One of my oldest bugs in this project is that the buffer resizes real weird. If you adjust both the height and width at the same time, it goes into this weird infinite loop business.

As it turns out, cmd.exe handles that by itself just fine. I just removed my resize listeners and now everything is running smooth.

feelsgood(?)man.jpg

It's only noon on Monday and I am already have a bullshit buffer overflow.

Everytime you use OpenGL in a brand new project you have to go through the ceremonial blindfolded obstacle course that is getting the first damn triangle to show up. Is the shader code right? Did I forget to check an error on this buffer upload? Is my texture incomplete? Am I bad at matrix math? (Spoiler alert: usually yes) Did I not GL enable something? Is my context setup wrong? Did Nvidia release drivers that grep for my window title and refuse to display any geometry in it?

Oh. Needed to glViewport. OK.

I do some robotics stuff on the side. We built our robot around a Raspberry Pi last year. We had 2 Python scripts talking over TCP, one for the bot, one for the controller. Overflowed the buffer on the bot and it went berserk once the script crashed.

- have a look at the project
- brake it down into smaller stories
- estimate the time
- multipy it with 1.5
- add 1-3 days of testing
- add 15% project management
- add a 2 days buffer

= be happy with being done in 2 weeks, present it in 4

Custom image format update:

Currently converts a 12KB PNG image into 172KB BIN file, now to compress the fuck out of it!

Update: Fuck should I use a buffer or simple binary data for file structure manipulation....

Anybody know a terminal emulator for Linux that supports searching/selecting/copying text in the scrollback buffer without the mouse? This is a killer feature of iterm that I have yet to see on a Linux TE.

This way of converting "string" to "s" (for example)

0) program reads the whole buffer, stores it as an array of instructions
1) program reverses the order of the instructions
2) parser makes standard token from an instruction ("asd" -> ASD)
3) parser2 assigns operands to instruction
4) parser 3 makes string from instruction token ?????
5) parser fucking 4 makeS A MUTABLE STRING INSTRUCTION
6) PARSER FIVE SUBSTITUES OPERANDS
7) AND THEN CUTS IT TO A REVERSED ARRAY OF COMMANDS
8) AND PUSHES IT UNTO THE STACK

WHAT

Failed asserting that false is true.

No shit sherlock ;/

Worked 6 hours straight without a break today. Completely exhausted😌, but the level of satisfaction out of the world!😊

Why is it so difficult to copy paste in an editor which is considered as one of the most sophisticated editor ? I use VIM for almost everything except for copy pasting . All those internal buffer ..external buffer things are complicating things..

And the sad part is ..once i was editing a bash script using sublime ..I pressed escape :wq .. and tried executing that for a long time .. I was clueless for sometime after which i realised i didnt save the document..

If at all VIM had easy ways to copy paste..😥

How many managers does it take to fix a bug in production?

ERROR: Buffer overlflow at line 1

Got an assignment last year to use a buffer overflow to "hack" a series of problems within some kind of assembly code. There were 2 required problems, but 6 in total. I completed all 7 (one hidden bonus problem).

The teacher that gave that assignment ended up writing me a letter of recommendation for my masters program

Talking about adrenaline sports in a class and our favorites.

Me ? Writing C code without checking for null pointers!

What about you ?

When someone (and this is typically someone non-dev and not a very structured person) says "Can I ask you a question" and, upon an affirmative answer to that, fires away a whole bunch of questions without waiting for an answer to the first of the questions.

Pleeeease! If you expect an answer, ask me one. question. at. a. time. Or write a freaking e-mail.

ECMAScript is everywhere, so I thought: Let's do even more inappropriate and insane things with it ;)

...Like using Duktape (small ECMAScript engine) and exposing LoadLibrary/GetProcAddress along with some helper routines to describe the routine's argument types and return type, and finally providing a routine to invoke those routines.

It's a very rough prototype that can handle up to 4 arguments in a 64-bit Windows environment.

Next "todo" is structure handling which will initially be a case of stuffing data into a Buffer() object.

I'm not sure what exactly I'm trying to do with it or why...

Just what the fuck is up with the senior devs in my team? Just because it's my first job as a developer doesn't mean I can't be right at times. Why can't they fucking digest that they could be wrong at times and me trying to tell them what could be improved is just for the product and has nothing to do with their egoistic selves.

Lately nothing compares to the excitement and happiness of executing my first successful buffer overflow.

Aha, more c++ knowledge. An implementation of a List (already provided by vector).

Lots of learning here, including use of the placement new operator, which is required for containers like this because if you just use the normal new operator, the buffer will construct a million items.

Also, the buffer is of type char*, not of type T, which really confused me in the beginning.

Lastly, with placement new, you need to call destructors yourself.

Interesting stuff.

CVE-2019-3568
Description: A buffer overflow vulnerability in WhatsApp VOIP stack allowed remote code execution via specially crafted series of SRTCP packets sent to a target phone number.

NSO group even sell a spyware application based on that vulnerability to governments.

Listen!!!!! I'm going to the toilet with my phone!!! Listen!!!

Turns out the only thing that was keeping me from using alacritty was the lack of keyboard-based text selection. About a month ago they released version 0.5.0, which added the ability to toggle "vi mode," which allows built-in, simple navigation of the current buffer using common vi keys. Consider me hooked and converted from urxvt, which works well, but lacks a lot of modern features, and is a bit clunky to configure.

Monday morning server dmesg error before coffee be like : Buffer I/O error on dev sdb ...
Before my coffee...
Oh I am surely being tested here ...

So I'm not sure on how much Youtube can fuck up so much in a short time, but I'm actually suprised.
And I'm not just tslking of all the shady/bullshit bahavior and reasoning on content creators, but also on how this shitty new app is just one clusterfuck of not working shit.

One if the easiest features there is - the damn shuffle feature for a damn playlist - doesn't properly work since the first day it went live. Are you shitting me? Even after a felt decade they are still not able to fix it. Yet alone showing more than 200 in the playlist items (when a video is already playing)

But a simple feature which is useful to nearly everyone and which worked before is surely no problem when the damn service itself would work.
Aside that the app sometimes randomly crashes when leaving fullscreen mode (desktop) and making it for some magical way impossible to interact with the browser (WTF?!) until you resize it or wait for an eternity to relase you from that suffer.

On top of that pile of garbage, the videos don't load properly anymore. Whats the fucking point of showing how much of a video is supposidly loaded when you skip forward for 5sec and it has to buffer for 10 to continue?

Well, if that were to at least only happen when the video is skipped forwards/backwards. On some strange occasion (Probably when the stars arrange properly) than your connection to the servers is back in the stoneage. Because otherwise I can't explain how the fuck it has to lower the resolution down to 360p and STILL buffer. I have a fucking 10MByte/s+ DL rate, ARE YOU SHITTING ME?!

Now after over 1.5k chars I notice I maybe a bit over the top ... BUT FUCK IT. I mean, it's fucking youtube ffs. If the biggest videoplatform can't even create a properly working webapp, then what the fuck are you doing google?

The day I read The Simulation Argument, by Nick Bostrom, a thought popped into my mind: "if we are made of code, maybe there are ways to hack life as you would hack some random program", I started thinking privilege escalation over the simulation, buffer overflow, picking signals as if I was eavesdropping... it was an epiphany and also fun

I was programming in java, C# and similar languages for years now and I never knew how the buffer overflow exploits would work, then I started C and saw the fixed size char arrays. After puking on my keyboard I realized that most of the vulerable programs were indeed written in C or similar languages.

Neovim,
I can code, git, ssh, reddit, mailbox, Spotify all at the same window.
With coc-explorer you can switch between your buffer just like VSCode

Oh god, structure alignement, why you do this... You might be interested if you do C/C++ but haven't tried passing structures as binary to other programs.

Just started working recently with a lib that's only a DLL and a header file that doesn't compile. So using python I was able to use the DLL and redefined all of the structures using ctypes, and the nice thing is: it works.

But I spent the whole afternoon debugging why the data in my structures was incoherent. After much cussing, I figured out that the DLL was compiled with 2 bytes packing...

Packing refers to how structures don't just have all the data placed next to each other in a buffer. Instead, the standard way a compiler will allocate memory for a structure is to ensure that for each field of the structure, the offset between the pointer to the structure and the one to the field in that structure is a multiple of either the size of the field, or the size of the processor's words. That means that typically, you'll find that in a structure containing a char and a long, allocated at pointer p, the double will be starting at p+4 instead of the p+1 you might assume.
With most compilers, on most architectures, you still have the option to force an other alignment for your structures. Well that was the case here, with a single pragma hidden in a sea of ifdefs... Man that took some time to debug...

It's 20-freakin'-17. Why aren't decent internet speeds the norm yet? (And I'm not taking about rural areas, I mean near the town center). If my and a friend are both streaming a movie, I SHOULDN'T HAVE TO FUCKING GIVE UP HALFWAY THROUGH JUST BECAUSE HE HAS TO KEEP PAUSING SO FREQUENTLY TO FUCKING BUFFER THE DARN FUCKING THING! WHY!? I CAN'T FUCKING FOLLOW A MOVIE IF THERE ARE CONSTANT FUCKING INTERUPTIONS EVERY TEN OR SO FUCKING MINUTES FUUUUUUUUCCK.

There is some speculation that Skynet is nothing more than a pretentious buffer overrun...

I was trying to make a circular buffer in C++. I was also trying to expose iterators for using the buffer with STL algorithms. I kept trying to think about how to add the functions needed to manipulate the existing internal iterators to not exceed the bounds of the buffer. Then I realized I was "too close" to the problem. There was no way I could properly control the internal iterators of the storage vector I was using. Not without giving too much power to the user of my library. So I abstracted the iterators up one level. Hid all the details of the internal iterator and made a new iterator.

The solution of abstracting the iterator was not the epiphany. The epiphany was if you are struggling with how to solve a particular problem. You keep running into problems with how to represent something, there is too much power available at a particular representation, or the object you are trying to make work just don't fit. This is when you should consider abstracting a level up. Take a higher look at the problem and simplify the interface.

Abstraction could be a number of things. Divide and conquer, hiding details, specializing an object, etc. Whatever tool is needed to make the problem more consumable to your brain.

That moment you take a crap after eating lunch and equate your digestive system as a circular buffer...

I was sure my buffer size was average...

Best experience: Sitting gleefully sipping coffee and typing away in VIM.

Worst experience: The constant stream of interruptions that refuse to be banished to another buffer.

I looked at an SQL server today from a customer, talked with one of their devs and he said that he's unable to understand why the server misbehaves... All (!) queries were optimized, but they have 'big data queries'... Migraine started, I had a very bad feeling. Monitoring? Nooooppeeee. Migraine kicks in. Connected to server. SHOW GLOBAL VARIABLES...
After a bit of scrolling I found a lot of misconfigured variables (e.g. extreme large join buffers, unrealistic buffer sizes), high slow query count (nearly 60 % of COM_SELECT) and a few variables that were unknown to me.

Then came the version line.
5.0.46
Yes. 5.0.46.

Big data? Well... 30 GB of usage data.

I called the company back... The dev told me sternly that this was the production server (I had hope...) and that I lie - neither the version, nor the variables could be the problem.
A coworker had to verify it and our manager had to do the communication... Worst, most traumatic working day I ever had.

In a Computer Systems class, we had a project to debug and buffer-overflow a program written in x86 Assembly. There were 2 mandatory problems we had to figure out, but the teacher told us there were 6 in total that can be solved. Not only did I complete all 6 on the next day (the project was due 2 weeks from then), I also noticed something looked weird in the code, so I investigated and found a hidden 7th problem and solved that too. Only one in the class to do so, and the teacher said I was the best student in any of her classes this year.

First, realize that trying to accurately estimate how much time something is going to take is akin to accurately predicting the future and that people who ask you to do it are stupid. Then realize that sales-oriented deadlines are the source of all that is evil. Then shift away from sales oriented software. Instead focus on selling existing features and new features on the roadmap have no deadlines, they're done when they're done. Then realize almost no workplace will let you truly do that because chasing the sale is all that matters despite the latest buzz word rhetoric. Then estimate enough buffer to give you a reasonable time to complete it without calling your abilities into question. Then finish it faster so you score points with management, but not every time because then they'll begin to expect it. Now you have leveled up in mind games, an unfortunate but necessary tool in the tool belt. Then hate on sales oriented software some more, rinse and repeat.

I called the hack "blow up bunny", was in my first company.

We had 4 industrial printers which usually got fed by PHP / IPP to generate invoices / picking lists / ...

The dilemma started with inventory - we didn't have time to prepar due to a severe influenza going round (my team of 5 was down to 2 persons, where on was stuck with trying to maintain order. Overall I guess more than 40 % ill, of roughly 70 persons...)

Inventory was the kind of ultimate death process. Since the company sold mobile accessoires and other - small - stuff.

Small is the important word here....

Over 10 000 items were usually in stock.

Everything needed to be counted if open or (if closed) at least registered.

The dev task was to generate PDFs with SKUs and prefilled information to prevent disaster.

The problem wasn't printing.

The problem was time and size.

To generate lists for > 10 000 articles, matching SKUs, segmented by number of teams isn't fun.

To print it even less. Especially since printers can and will fail - if you send nonstop, there is a high chance that the printer get's stuck since the printers command buffer get's cranky and so on.

It was my longest working day: 18 hours.

In the end "Blow up bunny" did something incredibly stupid: It was a not so trivial bash pipeline which "blew up" the large PDF in a max of 5 pages, sent it to one of the 4 printers in round robin fashion.

After a max of 4 iterations, bunny was called.

"bunny" was the fun part.

Via IPP you can of course watch the printer queue.

So...

Check if queue was empty, start next round with determined empty printer queues.

Not so easy already. But due to the amount of pages this could fail too.

This was the moment where my brain suddenly got stuck aft 4 o clock in the morning in a very dark and spookey empty company - what if the printer get's stuck? I could send an reset queue or stuff like that, but all in all - dead is dead. Paper Jam is paper jam.

So... I just added all cups servers to the curl list of bunny.

Yes. I printed on all > 50 printers on 4 beefy CUPS servers in the whole company.

It worked.

People were pretty pissed since collecting them was a pita... But it worked.

And in less than 2 hours, which I would have never believed (cannot remember the previous time or number of pages...)

You might think that getting your work done super fast is a good idea but it's really not. It takes QA awhile to test your tickets and give feedback. If you clear your sprint board, PMs will add more assignments... Then on top of that extra work, QA will give you feedback from your previous work. You now will be super stressed to get all of this done by the end of the sprint.

It is best to take your time and get it right the first time... I've also learned to make a buffer... which is tickets in my queue I've already completed but did not say I've competed yet. This way I can take extra time on tickets that need TLC and the PM team won't surprise you with backlog tickets.

Note to self, selecting text to copy it into the paste buffer only works in the terminal. It doesn't work in chrome...

Estimates.. First, part of the team makes "high-level" estimates which are based on informal, incomplete, still-evolving specs and an unstable back-end. The project people report the estimates to the client and elevate the status of these inaccurate estimates to that of commitments.

Then, before the "sprint", we review our initial estimates *ahum commitments* in greater (technical) detail. Because there are still a lot of unknowns, we tend to estimate more buffer here (back-end is often not ready, always ping-pong between project people and dev-team about unclear specs, more work than originally expected, and often late modifications to the original spec).

When an estimate becomes more than 50% extra time at the "refinement", we are told: "sorry, we gotta do it in less" and when it doesn't work out, we're kindly asked to spend part of our weekend catching up at 100% pay rate (legally it's 150-200%).

FUCK THIS SHIT

*quotes used abundantly because these terms belong to "agile/scrum" terminology but we're only pretending

Stack overflow is full of useless assholes, like I asked a specific question about a problem I am having that is similar to another problem that exists but it is not the same at all in terms of how to fix and instead of helping I’ve got 2 downvotes on it and a comment linking me to a completely unrelated stylistic based question based on something I SAID I HAD ALREADY TRIED CHANGING IN MY QUESTION!!! Here’s my question btw in case anyone can help here before I smash up my laptop 😑:
I have a piece of code in which I am trying to read in words which have been categorised using a number and then placed in a text file in the following format "word-number-" with a new line for each word. However, despite not mixing cin>> and getline and having tried a number of methods I still cannot get it working.
So far I have attempted using a cin.ignore() call to clear any '\n' char's from the buffer, as well as checking if the file is opening in the first place (it is), and using the >> operator instead throughout my code however I could not get that working either. When I place the get line call inside the condition of the while loop, the while loop doesn't run, however when I make the while loop condition a .eof() call it will run once however when I try to print the text that has been read from the getline call it just prints a blank line.
if(file.is_open()){
while(!file.eof()){
getline(file, text, '-');
count++;
cout<<count<<endl;
cout<<text<<endl;
if(count%2 == 1){
wordBuff = text;
}else if(count%2 == 0){
if(stoi(text) == wordClass){
wordList.push_back(wordBuff);
}
}
}
file.close();
}
While I recognise there are a lot of other questions on this out there I cannot seem to get any of their solutions to work and the vast number being related to people mixing the >> operator and getline doesn't help, so any tips or solutions will be of great help

Holy fuck, I just found out about 'set -o vi' which allows editing the readline buffer (the command line buffer) using vi bindings. All that wasted time holy fuck me.

Do any of you use Buffer? I'm thinking about creating an open source alternative to it, as ot would help me learn. Do you think building something like it makes sense?

Save enough from my current job to give me the buffer to go solo;

and it’s a cliche, but hopefully be making games

I don't want to spend a whole day tracking a crash back through multiple systems just to find a buffer that was initialised with garbage, wasn't written into completely, and as a result just *happened* to contain an exact value that causes a crash later on. If you're doing weird low-level things in C/C++, ZERO-INITIALISE YOUR DAMN BUFFERS.

Finally finished an algo to check an image for grouping of pixels that will form a rectangular area. I got the grouping to work on one image, but found it was utterly failing on another. I went through every step of the algo and still could not find the solution. The 128x128 image was working, but the 128x16 image was not. I knew it had something to do with the dimensions. Started thinking it was overflowing a buffer somewhere. So I started putting asserts in the functions that abstracted the buffer access. None of the numbers exceeded the proper bounds. It was close to bedtime so I finally gave up. I was tired. Then I realized it wouldn't be until the next evening when I could look at this again. So I got up again and started looking at the code again. I had a loop to check the output of my algo that I did the memory access of the buffer. It too was not fully filling my temp image to show how the algo was working. WTF!

Then I finally realized the flaw:
buffer[x+y*height]

And my test loop to test the algo:
buffer[x+y*ymax]

I kept overlooking the error because I was sure it was right. Also my asserts for the functions to access the buffers? They only checked the inputs x and y. So it didn't help that the math was wrong for reading and writing the buffers. It also worked fine on 128x128 images because the width and height were the same.

It is funny that I struggled with this part. The algo was actually surprisingly easy to formulate. I just looked through every point and checked a buffer to see if that point was used. If not then I would attempt to grow in the x and y direction the shaped of that point based upon pixel color. This was saved in a structure while growing that point. Then when that rectangle could not be grown further the inner loop would continue checking used points again.

I still have work to do to use the data this algo produces. I need to now figure out how to parent the rectangular areas to each other. I will probably use my check buffer to keep track of these rects by an index. Then do adjacent checks to determine parenting. Eventually I will have to extend this algo to 3 dimensions, but that should not be difficult.

And there is a new crash message for IOS tested and worked

Man my gf is awesome and actually takes interest in my tech adventures, but she gets so angry when I stay up late coding. So I wrote in a extra line of code in her software to make her more happy. Unfortunately it caused a buffer overflow.

In the basement, between the hot water buffer tank and the boiler.

Cozy temperature.

Not.

Q: You know it's Monday when...
A: (typing)... (buffer overflow)

Because you had a bad.. *Segfault*.

Well fyck, spilled me coffee now tho..

Is there an ios app that records my gps logs for last n day(cyclic buffer)? Privacy is also important: data shouldn’t leave my phone: no internet access.

WTF Windows?

If you call the API function to lookup the name of a service it expects a buffer and the size of the buffer.
If the supplied size is smaller than the service name it returns the number of characters (excluding the null-terminator) of the service name.
You can allocate a buffer for the service name and call the function again to receive the service name.

Except now Windows wants to know the size of the buffer including null terminators.

That took me a moment to figure out.

Difference between security threat and programming bug ?

Found a cool paper about format string attacks which mentioned buffer Overflow is a security threat while format string is a programming bug.
Had no idea what that really meant.

Tnx

In my previous agile sprint I somehow completed my task before the halfway, that's why I got less buffer time and point in this sprint.

Ability to code without having to type anything. Whatever I think appears in the editor real time.

If you develop something with bulk-internet-traffic (caching, backup and so on) buffer that long that OpenVPN can connect without interruption of a download, stream or so...

Microsoft announced a new security feature for the Windows operating system.

According to a report of ZDNet: Named "Hardware-Enforced Stack Protection", which allows applications to use the local CPU hardware to protect their code while running inside the CPU's memory. As the name says, it's primary role is to protect the memory-stack (where an app's code is stored during execution).

"Hardware-Enforced Stack Protection" works by enforcing strict management of the memory stack through the use of a combination between modern CPU hardware and Shadow Stacks (refers to a copies of a program's intended execution).

The new "Hardware-Enforced Stack Protection" feature plans to use the hardware-based security features in modern CPUs to keep a copy of the app's shadow stack (intended code execution flow) in a hardware-secured environment.

Microsoft says that this will prevent malware from hijacking an app's code by exploiting common memory bugs such as stack buffer overflows, dangling pointers, or uninitialized variables which could allow attackers to hijack an app's normal code execution flow. Any modifications that don't match the shadow stacks are ignored, effectively shutting down any exploit attempts.

I am building a synth program for producing waveforms such as binaural. The programs I have used in the past have been mediocre.

In that project I am working on a realtime scope to visualize the waveforms. It is fun to learn how to streamline moving data between parts of the application. Right now it has a lot of unnecessary data copying going on, and resizing of vectors. So I am reading some books on high performance C++ to learn how to do this better. As part of this I am thinking about building a circular buffer so the vector is never resized and is always in contiguous memory.

Just plain fun!

I had a pretty good day.

I had my first pay raise as a dev;) not huge but i wasnt expecting one for another 4months ;)

And i was working on a security scrip for after effect plugins. The thing is called Extendscript and is built on top of ecma3. Yeah javascript version from 1999. Hashing stuff gave me different results. Took me about a week to realise that the string buffer were different and i had to parse in latin something to have the same matching buffers. What a hassle man. Let alone trying to make it work with Windows terminal which after starting with Linux then mac， windows seems sooo sucky.

But yeah its my first security scripts so 2 main achievements for me today! Ive waited 4 years to reach a level where i now feel like a real professional dev. ;) sry not a rant ;)

Tried out the node.js code demo in this book.
🤦‍♂️
Terrible format, use tab for indentation, very very long function, redundant code (eg: new Buffer vulnerability)...
The major issue is none of the total.js nosql code works. Eg:
db.clear()
db.insert({...data})
Without any asynchronous call, how do you expect this to work?!
Just fixed the code and updated npm modules for demos in Chapter 3 btw... Took way longer than expected.

I usually work backwards trying to estimate time. Instead of asking "how long would it take me to do this?" I ask "could I get this done in X amount of time?" If the answer is yes, X-- and try again. This is how I get the absolute minimum amount of time I would need to get *something* done. Then I add a bit to that as a buffer.

i chose to work late today so I can have the office all to myself. however, I'm surrounded by art directors that keeps on playing cat and/or queer videos.

sorry pm, i guess i'll be taking that buffer and some.

k. bye.

I've got a basic understanding of c ++ and recently been asked something that's left me stumped. Am I able to take audio data (A sign wave as an example), output some of that data to a buffer that then directly outputs it to an audio device or speaker, without saving the data to an audio file and playing that? Been looking around Google (,Still am) and I'm not finding anything exactly the same that's answering my question or one that gives me an idea on how to do this. Any help or advice would be appreciated, even if it's only pointing me in the right direction

Thought I was a full stack developer for my company with only android and sails js until I was also told to design the website.

I don't always forget to turn off caps lock,
but when I do, it's in VIM AND WIPE OUT HALF THE FILE

you know I love you VIM

So doing some OpenGL crap and glSelectBuffer is occasionally returning all 0s. Not a problem except that right before the select buffer I push the names on to the name stack. So they should be on there. But they aren't ideas?

It's buffer overflow, but it's biology!