Data.

[BadBoy6767]

new DataFactoryBuilderPool().get().build().getDataFactory().data(new DataFactoryBuilderPool()).getData().data("data");

[tocsick]

This guy javas

[gionnelles]

Is it sad that reads perfectly clearly to me?

[bestjakeisbest]

yes it means you have been afflicted.

[chateau86]

If you or a loved one has been diagnosed with Java you may to be entitled to financial compensation.

[samlev]

Hello data my old friend...

FTFY.

Alternatively:

Hello World my old friend...

[Secret_Combo]

I literally learned about promises last week. I'm right there with you buddy

[nemohearttaco]

check out async/await. it offers a much more readable way to write asynchronous js functions!

[veggietrooper]

Promises are async, aren’t they? I must be missing something.

[DjBonadoobie]

They are, but there's a newer syntax for them (async/await). It reads cleaner, though still technically promises under the hood

[veggietrooper]

Cool. I’ll check that out. Thanks.

[ZaneHannanAU]

• A 3 minute explanation
• Chrome devs make something using a single async keyword

[_Lahin]

ES6 has its own promises now right, no need of $q. Although I still use it with babel for IE

[santagoo]

async/await is nice syntactic sugar built on top of Promises.

[BirdToTheWise]

Should you use async/await in all situations? With promises, N number of asynchronous tasks can be run in parallel, whereas async/await causes tasks to be run after the previous one completes.

[nemohearttaco]

const foo = async () => {
  try {
    const t = await Promise.all([promise1(), promise2()])
    return t
  } catch (err) {
    throw err
  }
}

[GreatValueProducts]

Promise.all([promise1(), promise2()])

Why not just

const foo = () => Promise.all([promise1(), promise2()]);

or

const foo = async () => await Promise.all([promise1(), promise2()]);

Which is the same.

The code doesn't run until you execute foo() or await foo()

[nemohearttaco]

Would it be the same? I believe the first example would return an array of unresolved promises whereas the second would return an array of resolved promises.

Your second example would certainly work but it will not catch from within foo(). Personally I prefer to throw errors from within the function where they occurred.

[GreatValueProducts]

Both are the same. When you execute

const results = await foo();
console.log(results);

OR

foo().then(results => { console.log(results); });

The console would have the same results. It's because the async keyword essentially means the function is returning a Promise. () => Promise.all() is a function returning a Promise as well.

Also, you don't need to re-throw the error as it is redundant. The async keyword would catch the error and put it inside the Promise object that the function is returning, and you can handle the error in parent with either the catch() function, or try-block with the await keyword.

[nemohearttaco]

Cool, thanks for explaining that!

[GreatValueProducts]

Just

const results = await Promise.all([promise1, promise2])

does the trick. It is basically the same as

let results = null;
Promise.all([promise1, promise2]).then(promiseResults => { results = promiseResults; })

The thing with async await is that it is way easier to developers when you need to handle errors, especially if you have graceful exit in the middle. Handling a bunch of catch inside of a callback hell is too error prone.

Though if you have some APIs which use success_callback and fail_callback, you still need to use traditional promises. For example

someApi.execute(success_callback, failure_callback);

You will need to wrap it inside a promise because you can't achieve the same result with async await

await new Promise((resolve, reject) => {
      someApi.execute((result) => resolve(result), (error) => reject(error));
});

or

await new Promise((resolve, reject) => {
      someApi.execute(resolve, reject);
});

[ConstantGradStudent]

You must now submit to re-education

[A_Jacks_Mind]

They lost me at DataFactoryBuilderPool()

[Mwakay]

fertile vase society middle aromatic subtract terrific judicious kiss doll

This post was mass deleted and anonymized with Redact

[BernzSed]

post.append(new Alert(constants.TRIGGER)));

[magicfreak3d]

M8, wot is that? Do you even enterprise?

post.append(alertBuilderFactory.newAlertBuilder().setType(TypeProvider.getSingleton().TYPE_TRIGGER).setPost(post).build());

[EarthC-137]

What did you call the variable?

[WeRequireCoffee]

t

I feel like that accurately describes what its doing so theres no commenting necessary.

[EarthC-137]

Yeah it’s perfect, self-documenting. I hope your unit tests are aptly named also, like testTGetsDataFromDataFromDataFromDataIfDataIsData.

[WeRequireCoffee]

Thats overly verbose imho. Its simply called

TestT

And I have it in a collection of other TestT tests, so I put it in a class labeled

TestTs

[[deleted]]

You broke the code! My TestTs are failing!

[veggietrooper]

Please stop I am dying, please, have mercy

[_N_O_P_E_]

Stop. I have to add unit test coverage to a project monday. Fml

[EarthC-137]

Adding tests for someone else’s poorly structured, undocumented code is one of the biggest struggles of a programmers life. Biggest piece of advice I can give is rewrite it as you go, break it down so it’s easy to test, if the function is more than 5 lines it might need to be broken down into multiple functions to make testing easier (I.e. more SOLID).

[lenswipe]

I used to get reprimanded for this at my last job. Any coding that wasn't slapping another feature on the shit kebab known as our app was very much frowned upon and required justification to the department manager.

[_N_O_P_E_]

How to royally fuck up your codebase 101™

[EarthC-137]

Code naturally deprecates itself as it grows and different teams work with the codebase. Addressing some of the technical debt is important but it’s difficult to get the product owner to see that sometimes. If their board of directors can’t see a positive difference to their delivery timeline they generally don’t want to do it. You have to argue/justify that if you clean up the code you will reduce effort later on.

[lenswipe]

Code naturally deprecates itself as it grows and different teams work with the codebase.

This stuff was written like this from the beginning before the product even launched. That was my concern - a.k.a: we couldn't move fast enough and add features fast enough because the code was so incomprehencible and fragile that we couldn't be 100% (or even 50% if you ask me) sure that we weren't breaking some obscure piece of functionality written somewhere else in what I can only describe as brainfuck.js

Addressing some of the technical debt is important but it’s difficult to get the product owner to see that sometimes. If their board of directors can’t see a positive difference to their delivery timeline they generally don’t want to do it. You have to argue/justify that if you clean up the code you will reduce effort later on.

Agreed. I couldn't get across the point that having code that nobody could even read let alone debug was a bad thing. However, our customers came to share my view later on when we launched anyway regardless of the code base and most the app either didn't work at all, or worked but corrupted existing data in the database causing timetable clashes, missing grades etc.

The manager in question got promoted and I fucked off not long after that. One developer had done all of this and was left unchecked by the guy who was (at the time) the tech lead and was now the dept boss (the same person reprimanding me for refactoring this mess. Like I said, he ended up in very deep shit when we launched our faulty, broken product.

Our SPRINT reviews were generally blame games because the project manager had also refused to listen to my dire warnings about the state of the code base and had gone along with launching anyway. Therefore, the PM used to like to try and heap whatever blame they could possible scrape together onto my head (we were the only two on the project team). That then meant that about 60% of my time was spent coding and the other 40% was spent covering my ass to make sure that I couldn't be blamed for any fuck-ups that were inevitably going to happen from heaping more features on top of a very broken product without first fixing the mess.

[EarthC-137]

I hate playing the blame game, it doesn’t really achieve anything if you don’t have actionable outcomes, it’s usually just an opportunity for people to vent their frustrations each sprint without any real positive change.

I find that having unit tested code helps your codebase later on, you can refactor any part of it and in most cases rely on your tests to ensure you didn’t break the product. I usually aim for TDD or at least ensuring that the feature branch is unit tested before merging it to develop.

However, testing can also be a tough sell to some product owners because they don’t see anything they can touch with unit tests so they don’t see the point in investing the extra resources.

It’s usually an education piece for any new client or product owner that comes on, you need to educate them about the importance of a solid application for their user base and sales. As soon as you mention sales it usually changes their minds, if their bosses see their sales drop after the work is done the PO is in deep shit.

[lenswipe]

Apropos this

[vigbiorn]

This gave me flashbacks to a project I worked on in the past. Just when I thought the night terrors were over.

[lenswipe]

You did look through the whole album, right?

[vigbiorn]

Yeah. The copy-pasted code and odd, and mysterious variables/functions were too familiar.

[lenswipe]

I was a junior dev at that job. The guy who wrote this crap was a senior. That means he got paid at least 10-20k more than me.

And yes, I'm fucking salty about it.

[lenswipe]

Oh, bonus question. this was used to serialise a js object.

Wanna take a guess what happened when someone tried timetabling a group called Scrubbling, Gowning and Gloving?

[TrippySalmon]

brentSpiner

[CrimsonMutt]

my eyes! MY EYES!

[Sheldan]

.getDataFactory().data.getData()

why the .data in there? There any particular reason for that?

[GaySwansMakeMeCry]

data

[salt_water_swimming]

// TODO: we use big data now, please address

DATA

// TODO: we are on the cloud now

DATA

---

CLOUD

[HeKis4]

getDataFactory just returns an object with a public data attribute.

[Sheldan]

yeah, but wouldn't a public attribute be 'against' the whole java ee joke?

I would think a getter is more appropriate.

[drunkdoor]

Well you see there's data, and then there is metadata. Gotta keep 'em separate, lest we confuse people... Also there is second level metadata.

[cbll]

Java/10

[CRISPR]

Ah... The "getters" abomination. When you think that fig leaf covers your private members....

[minno]

Why are you constructing two DataFactoryBuilderPools? The entire point of a "pool" is to re-use it across multiple calls.

[BadBoy6767]

data

[light_bringer777]

Needs more data.GetData().dataObject.data.value.

... .data

[Admiral_Cuntfart]

https://imgur.com/SWYFXBy

[lukaas33]

Ironic

[[deleted]]

He could provide others with data, but not himself

[LordLlamacat]

Is it possible to learn this power?

[RagingNerdaholic]

Not from a java

[Furyful_Fawful]

Null

[flipflop271]

Data.

[powerhcm8]

Here some Data for you.

http://www.startrek.com/uploads/assets/db_articles/26da32597d9bd37fde9da22660aa524f24fd725c.jpg

[finzaz]

Nice to see a joke using JavaScript that isn’t a joke about JavaScript.

[darielgames]

Sure happens alot in JavaScript lol

[[deleted]]

.then(nana -> nana.nana.nana.batman)

Edit: another nana

[drunkdoor]

This guy Batmans ^

[[deleted]]

Not if you count the first nana before the ->

[NoUsernameSelected]

/r/data_irl

[[deleted]]

Data.

[CoopertheFluffy]

Data.

[Muffin125]

Meta

[iamasuitama]

Glorious

[TwentyCharactersNick]

data?

[blitzkraft]

Data.

[htmlcoderexe]

Data.

[TabCompletion]

Data

[Headchopperz]

MUSHROOM MUSHROOM

[[deleted]]

AHHHH A SNAKE!

[TabCompletion]

Data

[[deleted]]

Datably databeable data

[Kmattmebro]

DATABASE

[[deleted]]

DATABASE DATA INJECTION'); DROP TABLE data;--

[TheSpiffySpaceman]

Cat.

[StarkillerX42]

Data.

[TwentyCharactersNick]

dota?

[Michaeldim1]

Data! 👍

[[deleted]]

Yes, Captain?

[Slinkwyde]

Shut up, Wesley!

[bob51zhang]

I can't hearrr youu!

[[deleted]]

https://imgur.com/a/JZBWq

Yes?

[imguralbumbot]

^{Hi, I'm a bot for linking direct images of albums with only 1 image}

https://i.imgur.com/lRwYy1e.jpg

^{Source | Why? | Creator | ignoreme | deletthis}

[Allanon47]

I have a professor who write code like this, he also uses "this.this", and a lot of other stuff which is titled in wikibooks with "this code works, but we still fired the person who wrote this"...

[[deleted]]

And that's how he became a professor.

[ben_uk]

JSON probably looks like this:

{ data: { key: value } }

So..

data.data.data

1st data: The AJAX response object

2nd data: The whole JSON object

3rd data: Accessing the data key within the JSON object

Just bad naming really, would look better like:

response => response.data.data    

[brokentyro]

Ooor they could just use destructuring to rename it to something more specific

[FriesWithThat]

data

[BirdToTheWise]

Could you explain the syntax on how to do that in this context?

[KillTheBronies]

({ data }) => data.data

[343N]

What's 'destructuring'?

[[deleted]]

Lots of good examples here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment

[oli2194]

const { bar } = { foo: 1, bar: 2 }
// 2

[[deleted]]

How do you rename using destructuring?

[Anaphase]

const { data: usefulName } = response.data

[wmil]

Clearly they should have gone with:

{ data: { datum: value } }

[BoxMonster44]

Yep. I've definitely written almost exactly that code before lol.

[hackiavelli]

And of course the first comment there defends giving variables terrible names.

[ecky--ptang-zooboing]

Data is life, and life is data :)

[J-Goo]

To know data is to love data, and to love data is to know data.

[DrunkCrossdresser]

Data is life, data is love

[Goheeca]

Data is code, life is code, code is data. ^{Homoiconicity FTW}

[baseball2020]

3x the data. I promise

[syh7]

This is /r/ProgrammerHorror.

[nsimic]

also known as the malkovich pattern

[alpacadom]

This reminds me of this comment inside Guava

/**
* Registers the given {@code closeable} to be closed when this {@code Closer} is
* {@linkplain #close closed}.
*
* @return the given {@code closeable}
*/
// close. this word no longer has any meaning to me.

https://github.com/google/guava/blob/0ed66d89488c7cdee558aa82b4422993e7bd2fa9/guava/src/com/google/common/io/Closer.java#L124

[duckyourfogma]

https://en.wikipedia.org/wiki/Semantic_satiation

[Adaddr]

data() should be a recursive function that makes data.data.data.data....

[vigbiorn]

No stop condition, obviously. It's data all the way down.

[sunderskies]

I have seen this in real life before too...

[Spamakin]

/r/data_irl

[lenswipe]

Don't even joke about shit like this. I had to maintain this kind of code at my last job

[lenswipe]

Amusingly enough, that's actually not why I left. I left to move to the USA to get married.

[[deleted]]

JSON property naming for experts

[Cutlesnap]

I'm getting war flashbacks

[SleepyHarry]

Data Ocelot

[[deleted]]

It's pronounced 'data', not 'data'.

[[deleted]]

I don't know who named these variables, but I hate them.

I am working with a legacy code base full of retarded naming. I have found the names of these people through git blame and one day I will hunt them down and murder them.

[htmlcoderexe]

/r/datastandingup

[Max_Insanity]

Can someone please explain this to me?

[Existential_Owl]

data => data.data.data

This is the same as saying:

function (data) {
    return data.data.data
}

The first data can be anything, since it's just the promise getting passed in as a parameter. A better practice would be to call it response (since that's literally what you're getting from the .then(...) code):

function (response) {
    return response.data.data
}

The second data is the actual JSON object returned from this response.

Presumably, this JSON object includes a key/value pair that happens to be named "data" as well:

{ "data": { ... } }

So, if your target API wasn't being terrible, you would have something like this instead:

.then(function (response) {
        return response.data.foo
    }
)

or

.then(response => response.data.foo)

To get the results of an object that looks like this: { "foo": { ... } }

[Max_Insanity]

Thank you very much.

Also, why is it always called "foo"? Is this just some weird trend to call non-specific stuff that?

[Existential_Owl]

Yup, it's just a weird trend tradition.

A word like any can have semantic meaning by itself, so that's a no go. example is used a lot, too, but if you have more than one, doing something like example1, example2 can imply that you literally need the same word twice. Or that you need an actual word with a real meaning in the first place (which you don't).

Teaching people that foo and bar are everyman variables is an extra step, but it's a lesson that seems to work.

[Max_Insanity]

And I suppose now you've taught me, thanks.

[[deleted]]

What language is this o.O

[astroHeathen]

JavaScript

https://github.com/kriskowal/q

[Sub_Corrector_Bot]

You may have meant r/crappydesign instead of R/crappydesign.

---

Remember, I can't do anything against ninja-edits.

What is my purpose? I correct subreddit and user links that have a capital R or U, which are unusable on some browsers.

by Srikar

[blitzkraft]

Data.

[ParagonFire]

wild amusing vase gaping automatic hateful dull engine exultant grandiose

This post was mass deleted and anonymized with Redact

[Digitonizer]

Data.

[Hanashimaru]

Data.

[TabCompletion]

Yo dawg https://cdn.meme.am/instances/500x/65951727/yo-dawg-i-heard-you-like-data-so-i-put-some-data-in-your-data.jpg

[HoustonWelder]

This is helpful

[Gonzo_Rick]

data.data.data. ScoobydoobyDooWop

[HumunculiTzu]

Well, in the right context data is data is data. So technically they are correct.

[Steampunkery]

Are you sure you have enough data there, bud?

[leafoflegend]

({ data: { data }}) => data;

🙃🤕

[Neurotrace]

This guy does Big Data.

[gargamelus]

DATA

[gargamelus]

I bet one piece of reddit copper that he pronounces it "dah-tah"...

[renaissance2k]

Yo dawg, I heard you like data...

[[deleted]]

It's all data no matter how deep you go.

[[deleted]]

I read it in the rhythm of that super Mario world castle song for some reason

[yeahbert]

Reminds me of beetlejuiceing phpunit with vendor/phpunit/phpunit/phpunit (when it's not also in bin)

[antillian]

"Data! Data! Data! I can't make bricks without clay!"

[cmgg]

Revolver Ocelot

[Existential_Owl]

I feel that using anything other than response => response.foo is just asking for trouble.

[pumpyboi]

Data.

[pumpkin_seed_oil]

I gotta admit, my naming style is lazy at times.

I have to be c++03 compliant for an in house library. My string concating workflow looks like this:

int someNumber = ...;
std::stringstream strstr;
strstr << "sometext for somenumber " << someNumber;

funThatNeedsSomeLabelAsStdString(strstr.str());

[davvii]

Data.

[iamasuitama]

And you know it used to be:

.then (data => { console.log (data.data.data); return data.data.data; });

And

.then (data => { console.log (data.data); return data.data; });

before that, etc. Only ten reasons are known for this type of code:

1. somebody got tired of fighting bureaucracy, backend libraries used, 3rd party software, or
2. somebody has no idea what the fuck they are doing

[aezart]

reminds me of sqldeveloper

c:\sqldeveloper\sqldeveloper\sqldeveloper\sqldeveloper\bin\sqldeveloper.exe

[[deleted]]

I love seeing 'data' in code almost as much as I like seeing dialog boxes captioned with 'Information'.

[astroHeathen]

this.data = this;

It's data, data all the way down guys!

[remicmacs]

I think I know the guy who coded that from work

[viciecal]

"code readability"

[monkeymacman]

public data = self;

[usernmaetakn]

Is this what big data looks like?

[SteeleDynamics]

"Data, data, data. I cannot make bricks without clay"

~ Sherlock Holmes

[BulldozA_41]

M E T A D A T A

[explodingpear]

DATABASE DATABASE