The GET /users endpoint will return a page of the first 13 users by default.

To request other pages, add |-separated querystring with the limit and offset, as roman numerals enclosed in double quotation marks. Response status is always equal to 200, plus the total count of the resource, or zero when there's an error.

You can include an array of friends of the user in the result by setting the request header "friends" to the base64-encoded value of the single white pixel png.

Other metadata is not included by default in responses, but can be requested by appending ?meta.json to any endpoint, which will return an xml response.

If you want to update the user's profile picture, you can request an OAuth token per fax machine, followed by a pigeon POST capsule containing a filename and a rolled up Polaroid picture. The status code attached to the return postal dove will be the decimal ASCII code for a happy smiley on success, and a sad smiley if any field fails form validation.

-- Every single external REST API I've ever worked with.

Customer :Can you build a system that rates our product by XYZ standard?
Us: Sure!

*time passes*

Us: Ta-da!
Customer: Okay, here are some good and some bad products!

*products get rated shit to supershit*

Customer: No, that's wrong. Some of these are as good as we can, they should be rated best!
Us: okay, we offset the results.

*products get rated good to barely okay*

Customer: Great! Can you sign that the system rates by XYZ Standard?
Us: No.
Customer : But we paid you to rate by XYZ standard!
Us: By XYZ standard your products are bad, you can either have your products rated by standard or pass the test.
Customer: Unacceptable!
Us: Improve production?
Customer : Not possible, the job is done when you rate the products good by XYZ standard.

Just remember, if someone ever makes a colony on Mars, you may have to support their timezone in your applications. And their day is longer, so a simple offset from UTC won’t do....

I noticed people using hashtags in rants. # really? We should use //

//theneworder

Many years ago I had the glorious idea to name myself 'offset' on github.
Now guess who always gets a notification when someone mentions '@offset' in a commit?

I'd rather code then study for my exams 🙁

TL;DR, employers are often penny wise and pound foolish.

One morning, my vehicle had a potentially life-threatening condition that I needed fixed before I could drive to work. I was 3 hours late but made a productive day of it. Plus I had stayed late after work, for no pay, a couple of nights because I have the kind of work ethic that compels me to do weird stuff like that occasionally.

When the time clock report came out it showed I was 3 hours short for the pay period. I brought up that I had "paid it forward" a few weeks prior and asked for an exception based on that. I was told that a) all "extra" work had to have been approved prior to doing it and b) that pay period had already passed, so no, I'd need to make up the hours. Being pretty miffed at being so nickled-and-dimed, and for being expected to drive to work in spite of the possibility of losing my life, I just had them take it out of my time off.

Fast forward to my latest monthly review: After another potentially life-threatening vehicle breakdown and fix, I decided to ask whether I could have a couple of telecommute days per week to offset fuel and mileage to recover the repair cost for the wear and tear on my vehicle. The answer was "No, because then everyone will want to work from home and then we'd have no way to know if they're really working."

On that same day I got an offer for doing the same job at another company for 100% telecommute and at nearly twice the salary. I turned in my resignation two days later. Now they're scrambling to try to replace me.

Deadline tomorrow, OTY, no offset but I love my company, boss and teammates 💪🔥

Thanks to @dfox @trogus for asking users for a pittance to offset server costs rather than inundating the app with ads that make it unusable.

This has been a longtime suggestion of mine for other apps and social media sites. People will pay a premium (even if it’s only $2) for quality; just ask Apple.

I'm fairly certain my boss'.....boss (didn't want to count them.. it's high up the chain, and slightly lateral) thinks I'm incredibly weird. I have too many sports injuries to be fully functional and they all flare up while I'm sitting at my desk. To offset this, I stand up or walk around while on the phone, and occasionally stretch.

These stretches are for hip and it band, usually, which are a bit more involved, so of course he ONLY fucking walks into the damn office while I'm stretching. (Image search for hip stretch).

To top it off, I have an unfortunate colored ointment for the pain in my elbow that i was applying today while stretching, and im scared to know what he was thinking before he realized what was actually going on. Imagine hip stretching (this one with leg on desk) while rubbing milky sort of clear ointment into skin...

Sir, if you're reading this, I promise I'm not actually that weird at work, you just have shitty timing.

Fuck Firefox's CSS engine! Why is it so fucking buggy?

I needed to position some elements in a circle, so I used Math.cos(Math.PI / 2) to calculate their x positions. So, mathematically speaking, that should return 0, right? Turns out in JS it doesn't (because fuck precision). It actually returns 6.123233995736766e-17 and I was using that in the style, like top: offset + that.

In chrome it was working perfectly, but in Firefox all hell broke loose. All animations stopped working, scripts stopped working, demons were eating people alive.

And I lost hours hunting that down. My fault because I should have tested it immediately on other browsers, but fuck!

I did a job interview recently for a company and the test was something like this.

In ruby, write a web server that will serve a specific line number from a text file.

I thought up a simple solution and a more advanced solution, but I opted to go with the simple solution and submit my work quickly. I made a nice web server with tests and everything and it used the sed command to get the line number from the file.

Now, they had various instructions, like it had to perform. They asked how it'd perform with 10G, 100G files. I thought "Eh... it'll be alright."

The solution they were looking for was the "advanced" solution that I thought up, which involved storing a binary file of 32/64 bit integers that reference the byte-offset of the line they're looking for. Basically a binary index file.

This violates all of my sensibilities, because I would never build a database indexer like this using ruby, of all things.

I thought it was a stupid test, and how do these companies honestly expect me to spend hours coding and then tell me I didn't go far enough? It's unethical.

I actually followed-up with the "advanced" solution a couple hours after hearing I was out, just to show them that their process is flawed.

Hoozay! I'm now starting to become an adult! (or atleast, that's what they expect of me)

myAge:
.long 19
main:
push rbp
mov rbp, rsp
mov eax, DWORD PTR myAge[rip]
add eax, 1
mov DWORD PTR myAge[rip], eax
mov eax, DWORD PTR myAge[rip]
mov esi, eax
mov edi, OFFSET FLAT:_ZSt4cout
call std::basic_ostream<char, std::char_traits<char> >::operator<<(int)
mov eax, 0
pop rbp
ret
__static_initialization_and_destruction_0(int, int):
push rbp
mov rbp, rsp
sub rsp, 16
mov DWORD PTR [rbp-4], edi
mov DWORD PTR [rbp-8], esi
cmp DWORD PTR [rbp-4], 1
jne .L5
cmp DWORD PTR [rbp-8], 65535
jne .L5
mov edi, OFFSET FLAT:_ZStL8__ioinit
call std::ios_base::Init::Init() [complete object constructor]
mov edx, OFFSET FLAT:__dso_handle
mov esi, OFFSET FLAT:_ZStL8__ioinit
mov edi, OFFSET FLAT:_ZNSt8ios_base4InitD1Ev
call __cxa_atexit
.L5:
nop
leave
ret
_GLOBAL__sub_I_myAge:
push rbp
mov rbp, rsp
mov esi, 65535
mov edi, 1
call __static_initialization_and_destruction_0(int, int)
pop rbp
ret

Interesting bug hunt!

Got called in because a co-team had a strange bug and couldn't make sense of it. After a compiler update, things had stopped working.

They had already hunted down the bug to something equivalent to the screenshot and put a breakpoint on the if-statement. The memory window showed the memory content, and it was indeed 42. However, the debugger would still jump over do_stuff(), both in single step and when setting a breakpoint on the function call. Very unusual, but the rest worked.

Looking closer, I noticed that the pointer's content was an odd number, but was supposed to be of type uint32_t *. So I dug out the controller's manual and looked up the instruction set what it would do with a 32 bit load from an unaligned address: the most braindead thing possible, it would just ignore the lowest two address bits. So the actual load happened from a different address, that's why the comparison failed.

I think the debugger fetched the memory content bytewise because that would work for any kind of data structure with only one code path, that's how it bypassed the alignment issue. Nice pitfall!

Investigating further why the pointer was off, it turned out that it pointed into an underlying array of type char. The offset into the array was correctly divisible by 4, but the beginning had no alignment, and a char array doesn't need one. I checked the mapfiles and indeed, the old compiler had put the array to a 4 byte boundary and the new one didn't.

Sure enough, after giving the array a 4 byte alignment directive, the code worked as intended.

Well, if your tests fails because it expects 1557525600000 instead of 1557532800000 for a date it tells you exactly: NOTHING.

Unix timestamp have their point, yet in some cases human readability is a feature. So why the fuck don't you display them not in a human readable format?

Now if you'd see:

2019-05-10T22:00:00+00:00

vs the expected

2019-05-11T00:00:00+00:00

you'd know right away that the first date is wrong by an offset of 2 hours because somebody fucked up timezones and wasn't using a UTC calculation.

So even if want your code to rely on timestamps, at least visualize your failures in a human readable way. (In most cases I argue that keeping dates as an iso string would be JUST FUCKING FINE performance-wise.)

Why do have me parse numbers? Show me the meaningful data.

Timestamps are for computers, dates are for humans.

Countries in UTC region have a relative advantage in debugging, as they don't have to add offset to datetime in logs,database etc to convert to localtime😂

Mother fucking SQL, fuck mathematicians, fuck every thing!

So let's supose we'd only need the first char of a string. Every, and I mean fucking every (php, java, javascript, ruby, python, haskell) fucking language, uses something like `substring(input, 0, 1)` as it knows the input is nothing more than a fucking array of chars, otherwise known as motherfucking String. Logically the offset for the first char is 0.

Enter SQL, there you need to put `SUBSTRING(input, 1, 1)` because fuck every one! Fucking math guys who developed relational algebra on which (most) databases are based on (I love you for it, but come on you fuckers!), Decided that the first character should be at position 1...

Fuckers

We have an API available for our customers to integrate our software with their Webshop.

A client and their developer complained because not all of the products came through. I checked the products, the validation, the parameters, the database .. everything looked fine and I was scratching my head why these articles wouldn't come through (but it did work at my end).

After some time, I checked the request logs..
Apparently it wasn't quite clear for them that a loop is required with the 'skip' and 'take' parameters to create an offset for pagination.They only synchronised the first 500 products.. everytime..

We have a limit of 500 products per batch (take) for performance reasons.

They asked if we could increase this limit, because they have "a large range of products" (not really, only 800 or so and we have clients with more than 2mil. products..) Oh pls.. I've sent them a link to the PHP manual for a basic 'while' loop..

An asshole ex-client who owes me in excess of $1000, and doesn't intend to pay, has left me on their Twilio administration (unknowingly clearly) panel. I have the option of requesting around 30+ Cayman Islands numbers to auto charge his card enough to offset the debt.

Hmmmm.

This was a while back. I was hosting a site at a hosting company's 'vps'. I had 1gig for the mysql databases. Problem is, for some reason the server didnt let me have more than 300mbs including everything (there were some videos on the site). I contacted them and they only replied that its ok on their end. Okay, makes sense. So i opened ssh and started looking for the problem. After a bit, i figured out that my site is hosted on a 1tb drive and i could see all the other partitions. Meaning they just slapped a bunch of users data on the same drive. So i wrote an assembly program to offset the mysql files by ~500 mbs. Turns out that put me in an unoccupied 100gb partition and the site was still working properly. So i offset everything to there and i had a 100gb vps for like $5.

I didn't leave, I just got busy working 60 hour weeks in between studying.

I found a new method called matrix decomposition (not the known method of the same name).

Premise is that you break a semiprime down into its component numbers and magnitudes, lets say 697 for example. It becomes 600, 90, and 7.

Then you break each of those down into their prime factorizations (with exponents).
So you get something like

>>> decon(697)
offset: 3, exp: [[Decimal('2'), Decimal('3')], [Decimal('3'), Decimal('1')], [Decimal('5'), Decimal('2')]]
offset: 2, exp: [[Decimal('2'), Decimal('1')], [Decimal('3'), Decimal('2')], [Decimal('5'), Decimal('1')]]
offset: 1, exp: [[Decimal('7'), Decimal('1')]]

And it turns out that in larger numbers there are distinct patterns that act as maps at each offset (or magnitude) of the product, mapping to the respective magnitudes and digits of the factors.

For example I can pretty reliably predict from a product, where the '8's are in its factors.

Apparently theres a whole host of rules like this.
So what I've done is gone an started writing an interpreter with some pseudo-assembly I defined. This has been ongoing for maybe a month, and I've had very little time to work on it in between at my job (which I'm about to be late for here if I don't start getting ready, lol).

Anyway, long and the short of it, the plan is to generate a large data set of primes and their products, and then write a rules engine to generate sets of my custom assembly language, and then fitness test and validate them, winnowing what doesn't work.

The end product should be a function that lets me map from the digits of a product to all the digits of its factors.

It technically already works, like I've printed out a ton of products and eyeballed patterns to derive custom rules, its just not the complete set yet. And instead of spending months or years doing that I'm just gonna finish the system to automatically derive them for me. The rules I found so far have tested out successfully every time, and whether or not the engine finds those will be the test case for if the broader system is viable, but everything looks legit.

I wouldn't have persued this except when I realized the production of semiprimes *must* be non-eularian (long story), it occured to me that there must be rich internal representations mapping products to factors, that we were simply missing.

I'll go into more details in a later post, maybe not today, because I'm working till close tonight (won't be back till 3 am), but after 4 1/2 years the work is bearing fruit.

Also, its good to see you all again. I fucking missed you guys.

I found weird that some developer never ask why when facing a problem. "What do you mean never ask why?" here some story.

Let's say a developer work with simple app. Laravel as Backend and Postgresql as Database. He face a problem that the app very slow when searching data.

In order to solve that problem he implement cache using redis but he found problem that it fast occasionally. In order to solve that problem he implement elasticsearch because he think elasticsearch very good for search but he found another problem that sometimes data on postgresql out of sync with data on elasticsearch. In order to solve that problem he implement cronjobs to fix out of sync data but he found another problem that cronjobs cannot fix out of sync data in real time. and so on...

Do you see the problem? He never ask why the app slow. Which part search the data? Backend or Database (Search in the Backend mostly slower than Database because Backend have to get all data on database first). Has the query been optimized? (limit offset, indexing). How about the internet connection? etc.

For me it's important to ask why when facing a problem and try to solve the problem as simple as possible.

So there is the webapp that the national post is using in Hungary. When you want to search a street in the given city you have to wait until the whole fucking list is populated and the street names are filtered afterwards. (I've got it he only wanted one request per street). But if that won't be enough the drop down menu is offset in some resolutions and the console is full of errors.

I can live with that even with the duplicate street name, but how dare you to publish an app with a search function that is unable to work with the special characters of the specific language? It's not even hard to make it work. You just a lazy ass dumbfuck who copy pasted something from stack overflow and didn't make the effort of testing it.

I mean I would probably jump off of a brifge if I would make such a huge mistake.

Im listening to 8D music (sound vibrations in 8 dimensions) and it is weird as fuck

Feels like i am in a giant and small room in the same time, at place A while being at place B in the same time because the vibrations cycle around you to create an illusion of offset spatial divergence

FUCK EVERY PERSON IN THIS SHIT BANK!! FFS THE IDIOTS CREATED A NEW DATABASE USING SQL SERVER 2008! Yes, 2008 and its a new database if it was some type of legacy I could try to understand, but this shit is a completely new database. I have to use sequelize and guess what? It can't paginate results because shit server 2008 does not accept OFFSET FETCH syntax

Spend literally two days trying to figure out why I have a 2 hour offset in my timezones for a lamp web app. This isn't even close to my first timezone rodeo.

Check logs, reset Apache/MySQL/PHP timezones in like 100 places. Use 3rd party server side and client side timezone libraries. Moment.js you say? Shit works like a charm... but is, of course, still two hours off.

MySQL is right. PHP is right. Apache is right. PHP libs are in place. Finally convert the entire damn project to use epoch time because I have a deadline, I have no more time to read backwater AWS docs and try to figure out why the hell this Ubuntu EC2 is fucked up, and I literally cannot figure out why in the hell the damn clock is off.

Several days later notice a variable in the main .config file... right in root... 2 hour timezone offset.

Fuuuuuuuuuuuuuuuuuuuuck.

When you need to work with the register of your microcontroller but you fuck up the addresses. I wasted so much time looking at my code to figure out what I'm doing wrong. I tried everything, looked up the datasheet again on how to initialize everything and in the end I fucked up the fucking register addresses. Three addresses had, at the offset, one 0 instead of two.

I never felt so dumb in my life

One of my collegues:(C#)

A(him): i need to do a helper to transform 2 fields from a class that are DateTimeOffset to another offset. I want to create a new class that do that and to instantiate where i need it.
B(me): use extensions, they are nicer and they fit better in this case. Also if you want to use a helper just make a static function.
A: it's too complicated
B: Why?
A: Nevermind..

FUCK OFF!

Asciidoc! I finally got around to play around with it and it is just so awesome! Best tool for documentation hands down! So many improvements over Markdown:

- importing real code snippets based on tags with syntax highlighting and annotations (which can be also auto numbered with "<.>" instead of "<1>"!)
- Admotions! Love them!
- automatic TOC! Finally!!
- joining a child item to a parent item in a list with "+" in a new line (this one took me a while to understand, but no more offset items in lists! Love it!)
- making tables and loading data from an actual CSV-file! The future is now!!
- embedding images with a fixed size

Just a few things from the top of my head. I don't know why I put up with vanilla Markdown all these years...

Last but not least, a big THANK YOU to everyone who recommended Asciidoc! I accidentally stumbled across multiple mentions of Asciidoc a few months ago. Sorry, but you know who you are! Much love to you and your loved ones! You changed my life for the better. Thank you!

Converting server time to any given local timezone is a pain in the ass.. at least in JS.

Here's what I've got:
convertNowToTimezone = (localOffset) => {
let d = new Date();
let millis = d.getTime() + (d.getTimezoneOffset() * 60000); //convert server local time to UTC millisec
d.setTime(millis - (localOffset * 60000)); //convert UTC millisec to required local time
return d;
}

where I pass localOffset as -330 (IST offset).
Works in chrome console but gives a diff of 4min in the server side nodejs I'm running it in..

🤬🤬😡😡😡😡😡

Time to annoy @kiki :)

the first 4 tabs are pinned. All the remaining ones are not. Chrome after its latest update

Alright, that’s IT. I am going to just auto-find that fucking mentions and URLs myself, because the offset system in devRant’s metadata is completely unpredictable. Really.

For context look at my last rant (I think).

My wish for devrant: click devrant text in navigationbar to refresh and scroll to top of the feed.

Say what you will, but nothing compares to the excessive pleasure one derives from transitioning from a top-tier development machine, the mere sight of which inspires awe from computer enthusiasts everywhere - the type of machine that seems to glisten in the light of the sunset as choirs ring out from nowhere in particular yet everywhere at once to sing it's praises as it's many full HD screens aluminate the room to offset the dying of the light.

To a mandatory, work provided claptrap with a Core 2 Duo, 2gb of RAM, 90GB of storage and an integrated GPU that can barely stomach 720p before it starts choking on its own mucous.

Truly fucking marvellous.

I was using SimpleDateFormat and everything was great but then next thing I find out, the time offset for GMT is stored as Z and not +00:00 which is the format I needed for API calls.

Every other time zone follows a similar format but yet somebody thought it was a good idea to switch it up for GMT

So I promised a post after work last night, discussing the new factorization technique.

As before, I use a method called decon() that takes any number, like 697 for example, and first breaks it down into the respective digits and magnitudes.

697 becomes -> 600, 90, and 7.

It then factors *those* to give a decomposition matrix that looks something like the following when printed out:

offset: 3, exp: [[Decimal('2'), Decimal('3')], [Decimal('3'), Decimal('1')], [Decimal('5'), Decimal('2')]]

offset: 2, exp: [[Decimal('2'), Decimal('1')], [Decimal('3'), Decimal('2')], [Decimal('5'), Decimal('1')]]

offset: 1, exp: [[Decimal('7'), Decimal('1')]]

Each entry is a pair of numbers representing a prime base and an exponent.

Now the idea was that, in theory, at each magnitude of a product, we could actually search through the *range* of the product of these exponents.

So for offset three (600) here, we're looking at

2^3 * 3 ^ 1 * 5 ^ 2.

But actually we're searching

2^3 * 3 ^ 1 * 5 ^ 2.
2^3 * 3 ^ 1 * 5 ^ 1
2^3 * 3 ^ 1 * 5 ^ 0
2^3 * 3 ^ 0 * 5 ^ 2.
2^3 * 3 ^ 1 * 5 ^ 1

etc..

On the basis that whatever it generates may be the digits of another magnitude in one of our target product's factors.

And the first optimization or filter we can apply is to notice that assuming our factors pq=n,
and where p <= q, it will always be more efficient to search for the digits of p (because its under n^0.5 or the square root), than the larger factor q.

So by implication we can filter out any product of this exponent search that is greater than the square root of n.

Writing this code was a bit of a headache because I had to deal with potentially very large lists of bases and exponents, so I couldn't just use loops within loops.

Instead I resorted to writing a three state state machine that 'counted down' across these exponents, and it just works.

And now, in practice this doesn't immediately give us anything useful. And I had hoped this would at least give us *upperbounds* to start our search from, for any particular digit of a product's factors at a given magnitude. So the 12 digit (or pick a magnitude out of a hat) of an example product might give us an upperbound on the 2's exponent for that same digit in our lowest factor q of n.

It didn't work out that way. Sometimes there would be 'inversions', where the exponent of a factor on a magnitude of n, would be *lower* than the exponent of that factor on the same digit of q.

But when I started tearing into examples and generating test data I started to see certain patterns emerge, and immediately I found a way to not just pin down these inversions, but get *tight* bounds on the 2's exponents in the corresponding digit for our product's factor itself. It was like the complications I initially saw actually became a means to *tighten* the bounds.

For example, for one particular semiprime n=pq, this was some of the data:

n - offset: 6, exp: [[Decimal('2'), Decimal('5')], [Decimal('5'), Decimal('5')]]

q - offset: 6, exp: [[Decimal('2'), Decimal('6')], [Decimal('3'), Decimal('1')], [Decimal('5'), Decimal('5')]]

It's almost like the base 3 exponent in [n:7] gives away the presence of 3^1 in [q:6], even
though theres no subsequent presence of 3^n in [n:6] itself.

And I found this rule held each time I tested it.

Other rules, not so much, and other rules still would fail in the presence of yet other rules, almost like a giant switchboard.

I immediately realized the implications: rules had precedence, acted predictable when in isolated instances, and changed in specific instances in combination with other rules.

This was ripe for a decision tree generated through random search.

Another product n=pq, with mroe data
q(4)
offset: 4, exp: [[Decimal('2'), Decimal('4')], [Decimal('5'), Decimal('3')]]

n(4)
offset: 4, exp: [[Decimal('2'), Decimal('3')], [Decimal('3'), Decimal('2')], [Decimal('5'), Decimal('3')]]

Suggesting that a nontrivial base 3 exponent (**2 rather than **1) suggests the exponent on the 2 in the relevant
digit of [n], is one less than the same base 2 digital exponent at the same digit on [q]

And so it was clear from the get go that this approach held promise.

From there I discovered a bunch more rules and made some observations.
The bulk of the patterns, regardless of how large the product grows, should be present in the smaller bases (some bound of primes, say the first dozen), because the bulk of exponents for the factorization of any magnitude of a number, overwhelming lean heavily in the lower prime bases.

It was if the entire vulnerability was hiding in plain sight for four+ years, and we'd been approaching factorization all wrong from the beginning, by trying to factor a number, and all its digits at all its magnitudes, all at once, when like addition or multiplication, factorization could be done piecemeal if we knew the patterns to look for.

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...

Bug report : date_created is wrong by one day, but only in the afternoon. Gaaah ! Why did nobody save the user's offset...
Or better yet just normalize to UTC!?!?

I know we all start from the bottom but for fuck's sake some people have no fucking clue what the are doing.

I saw this in a previous senior of mine's stylesheet.

.col-sm-offset-1 { margin-left: 0%; }

I cannot believe that a person can be this stupid.

timestamps with TZ offset

why.... WHYYYY???????

Why is tech management so f-ing distant? Very often NOT in meetings which they created and very not interested in anything the team/teams do. It is really a large offset between the work actually being done, the day-to-day operations that we do and the competence of management to acknowledge the fact that we actually do those things.

A lot of times they just stay silent in meetings and in the end they say something to try and make some conclusion and perhaps something ”funny” to try and lighten up the atmosphere. They fail on both of their tasks. They have no clue and are not interested in learning.

I feel like many of them don’t actually do anything. They are often ”away” but it is really unclear what that means.

I think it is symptom of a truly dysfunctional tech process. Bad leaders tend to hire more bad leaders and it is a toxic circle ending in good competent people leaving wanting more in the leadership.

I've been reading this new book. And the heading & the paragraph is way offset. Like 3 fingers offset.

It freaks me up every time.

Got my new Thinkpad T480s today. First i was happy then i saw that the display has an offset and isn't centred 😒

Am I the only one who noticed the different offset on the notifys tab? 😂

I've been given two months to make an AR app that gives information on buildings seen out of the window of a client's skyscraper office.

So off I go, smash together some Ar.js in a few days because it looks easy. Yet I quickly find out that the compass on mobile phones are completely trash. Every device I try has true north randomly chosen from anywhere between 10 degrees wrong or full on 180 degrees the opposite direction. It's a miracle that none of these devices have managed to stumble onto true north by luck. I'm getting suspicious that ar.js is actually just mapping coordinates based on north instead of true north or something ridiculous. This likely won't be helped by GPS interference from the skyscraper.

It isn't helped that ar.js is a steaming pile of bugs on top of bugs, many of the examples taken straight from documentation straight up don't work.

I'm trying to get ar.js with three.js now in the hope that I can figure out some kind of true north calibration controls as an offset to whatever the phone says north is.

If anyone has any suggestions for a better solution that would be grand.

<?php
// This is the demo code of a PHP gotcha which took me some hours to figure out

$hr = "\n<hr>\n";
$JSON = '{"2":"Element Foo","3":"Element Bar","Test":"Works"}';
$array = (array)json_decode($JSON);

echo "Version: " . phpversion() . $hr;
// Tested on: 5.5.35 and 7.0.15

var_dump($array);
// Prints: array(3) { '2' => string(11) "Element Foo" '3' => string(11) "Element Bar" 'Test' => string(5) "Works" }

echo $hr;

var_dump($array['Test']);
// Prints: string(5) "Works"

echo $hr;

var_dump($array[2]);
var_dump($array['2']);
var_dump($array["2"]);
var_dump($array[3]);
var_dump($array['3']);
var_dump($array["3"]);
// Prints: NULL + Notice: Undefined offset ... in ...

echo $hr;

$newArray = array();
foreach ($array as $key => $value) $newArray[$key] = $value;

var_dump($newArray[2]);
var_dump($newArray['2']);
var_dump($newArray["2"]);
// Prints three times: string(11) "Element Foo"

var_dump($newArray[3]);
var_dump($newArray['3']);
var_dump($newArray["3"]);
// Prints three times: string(11) "Element Bar"

Oh let the rant time begin…

So previous post I mentioned about this dev who has resigned and how I was going to see about a Snr. position.

Management is now scrambling to figure out what to do as this dev managed all the migration to AWS etc, I know servers but haven’t got too much familiarity with AWS.

Anyways so I finally get a 1:1 with my new line manager. I ask about the position and he says they don’t know what there going to do yet. Hire a new dev in India to offset and with the same knowledge even though the guy leaving is in the U.K. Bad idea as the servers are in the U.K. so if we get downtime or the server crashes we have no one in the U.K. to reset or access to the servers. India are very cagey who gets access which is annoying to say the least even though us (three devs) in the U.K. are the principal engineering team so there looking at all options.

Anyways we have a back and fourth, we discuss some of the plans for the app, some of which we are nowhere near ready to even conceptualise as the app in its current state sucks, (ruby 2.2.6 and rails 5 but not really). Needs major refactoring and rewrite, one thing they want to do is multi tendency which again given the state is laughable.

So, as my manager is speaking my head is screaming being like “this is just going to be a massive disaster”. Then we go onto that he’s seeing what everyone’s strengths are etc. And then we get onto the upgrade and that he wants me to work on it.

Yes.. the upgrade I’ve been trying to do for the past 4+ months but I keep getting told to stop and getting pushed backed.

I’ve been told we have devOps looking into restructuring the app, not possible as how the app is written, we have India trying to multi tenant again disaster incoming as they’ll end up rushing it. Legal are going to have a field day. Every time I say the issues are the fundamentals with the app, here’s how we can sort it. In one ear out the other basically there patching the ship even though it’s still leaking.

I have so many ideas, and things I can do to improve the app and get it back to not only working order, fix the performance issues, data issues and everything else. Brick wall.

So rants ensue where I basically say I would love to do the upgrade but management gives me no time in the roadmap (we have no say in planning). At this point I’m just speaking to a brick wall.

After the meeting I have a chat with the BAs, we all have the same issues so honestly it sucks we end up ranting to each other for an hour.

I’m being under-utilised, being told do this, do that even though I’ve had two stabs but told to stop and pushed back, I know what benefits I can bring to the app with a refactoring, ideas and how to properly lead the team because honestly we’re working on an old legacy app, and management are clueless and there priorities are all wrong, the company is getting frustrated and it’s a sinking ship. They would rather patch issues without solving them and everything I say goes in one ear and out the other.

Frustrating is not the word.

Its amazing how you have to train people so their greed doesn't override their greed.

Imagine this.

2000.00 of waste a day.
2000.00 a DAY, offset by EVERY last customer you get.

To make on average 15.00 to 20.00 a day you have to spend the equivalent of $0.19 of electricity extra for them to run a laptop, to get a certain kinda client.

And some days, for a few days at least, you have to leave them alone for 4 to 5 days without buying anything so they'll buy something every day for 2 to 4 weeks at a time.

Well you're already lighting, heating, cooling and staffing the place, and you're throwing out a fuck ton of perishable product, can you afford to turn that customer away ? nope.

but they want to because they like being assholes and because they're mimicking their asshole parents who's purpose or finer points of detail they never understood because they're just desiring to mimic their piece of shit parents in being assholes, not realizing when they can be assholes without too much self detriment.

and the place is far from the ritz hotel :P

public function index(Request $request): array
{
$parameters = json_decode($request->get('lazyEvent'), true);

if (isset($parameters['page'])) {
$page = $parameters['page'];
} else {
$page = 0;
}

$queryBuilder = DB::table('companies')
->leftJoin('company_contact', 'company_contact.company_id', '=', 'companies.id')
->groupBy('companies.id')
;

if (isset($parameters['filters']['name'])) {
$queryBuilder
->where('name', 'like', '%' . $parameters['filters']['name']['value'] . '%')
;
}

$total = $queryBuilder
->count()
;

$companies = $queryBuilder
->select('companies.id', 'name', 'email', 'phone', DB::raw("COUNT('company_contact.id') AS contact_count"))
->orderBy('name')
->offset($page * $parameters['rows'])
->limit($parameters['rows'])
->get();

return ['companies' => $companies, 'totalRecords' => $total];
}

what is this shit? I get $total 1 when in reality is $companies count is 51

I am thinking avout writing whole sql as raw because I cannto get fucking count correctly

Spent the best part of a day getting Google maps to offset the center of its bounds to account for divs displaying the marker info, which are floated on top - why does this shit take so long??

"We would really prefer it if you didn't attempt to print time zone offset with your DateTime values (because that functionality is utterly borked and prints nonsense)."

From documentation of .Net DateTime.

I have finally done what I will call a "pro javascript move", but I did this in C++...

QString str("hello");
float offset=0.0;
...
offset = somevalue;
return str + offset;

This printed out "hello[]". Where [] is some unknown character box.

No warnings at all. It just found a conversion function and did it.

Another day, another struggle with time zones.

How many fucking helper methods do I need to create for dates and time zones? How many components, pipes and services do I need to wrap just so two datetimes line up? Apparently another one today. At this point I'm ready to accept flat earth theory if it means no more time zones. I'm fucking sold on it if so.

It's not even the time zone that's the issue. It's business needing it formatted, but also offset properly, based on your browser locale, but with points that cross into DST observing time zones of a different locale simultaneously. Sometimes those times are the same, sometimes they're different, sometimes they're different but only in winter. And despite a plethora of libraries to help with these calculations, nothing ever seems to just work out of the box. So here's to another layer of abstraction, because time zones (and DST) are bullshit.

The time I save by making something work on the first try is offset by the time I spend not believing it, poking around and making sure I didn't overlook anything.

That feel when you find that one font that both looks good and renders ponysay's ponies well ... yet the powerline glyphs are vertically offset T_T

(It's Fira Mono for Powerline btw.)

Hi devs just a simple question for people who use cheat engine or any memory editor if your looking for information of a gun like fire rate don't you have to search ammo to find other things related to that object?

and say fire rate is a few values close
is that because when programming the game they put the values close to each other and that is called offset (1 value is closer to the base value)?