The OFFICIAL programming thread

[Kilemall]

@rote7 said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

@Tazz said in The OFFICIAL programming thread:

Longcode!

Nope: Long Linux Kernel boot messages

I was going to say it reminded me of a card boot deck.

[Tazz]

[Jerraye]

Not sure if this belongs in here, but since we don’t have an OFFICIAL crappy special effects thread, I can drop a gif of my crappy smoke effect in here:

[Kilemall]

@Jerraye said in The OFFICIAL programming thread:

Not sure if this belongs in here, but since we don’t have an OFFICIAL crappy special effects thread, I can drop a gif of my crappy smoke effect in here:

Highly relevant, many programs pretty much are special effects that do nothing.

If you had added mirrors, pretty much every product demo ever.

[Tazz]

When your code is shit but it still works

[Jerraye]

I managed to make a thing for rotating a thing back and forth.

[Tazz]

@Jerraye that’s very good

[Gators1]

@Jerraye said in The OFFICIAL programming thread:

I managed to make a thing for rotating a thing back and forth.

I think you are good enough to join the Star Citizen team now!

[Wingmann]

Overqualified, even.

[Jerraye]

Ha! Star Citizen isn’t even worthy of kissing my medieval peasant feet!

[Gators1]

10 Programmer Stereotypes

[Kilemall]

@Gators1 said in The OFFICIAL programming thread:

10 Programmer Stereotypes

Utterly accurate.

[Gators1]

@Kilemall said in The OFFICIAL programming thread:

Utterly accurate.

I trust the opinion of the silver beard programmer.

[Kilemall]

@Gators1 said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

Utterly accurate.

I trust the opinion of the silver beard programmer.

Once you go mainframe you can never go back.

[tigger]

@Kilemall said in The OFFICIAL programming thread:

@Gators1 said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

Utterly accurate.

I trust the opinion of the silver beard programmer.

Once you go mainframe you can never go back.

Until the first time you write a mapreduce.

[Kilemall]

@tigger said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

@Gators1 said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

Utterly accurate.

I trust the opinion of the silver beard programmer.

Once you go mainframe you can never go back.

Until the first time you write a mapreduce.

Hmm, mainframes can operate linked and synchronized but they aren’t really built for massively parallel processing problem sets per se.

[Gators1]

@Kilemall said in The OFFICIAL programming thread:

@tigger said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

@Gators1 said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

Utterly accurate.

I trust the opinion of the silver beard programmer.

Once you go mainframe you can never go back.

Until the first time you write a mapreduce.

Hmm, mainframes can operate linked and synchronized but they aren’t really built for massively parallel processing problem sets per se.

So they are obsolete.

[Kilemall]

@Gators1 said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

@tigger said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

@Gators1 said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

Utterly accurate.

I trust the opinion of the silver beard programmer.

Once you go mainframe you can never go back.

Until the first time you write a mapreduce.

Hmm, mainframes can operate linked and synchronized but they aren’t really built for massively parallel processing problem sets per se.

So they are obsolete.

No they are just really good at financial work.

You bank or deal with brokerages, you are connected with a mainframe.

[A Former User]

@tigger said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

@Gators1 said in The OFFICIAL programming thread:

@Kilemall said in The OFFICIAL programming thread:

Utterly accurate.

I trust the opinion of the silver beard programmer.

Once you go mainframe you can never go back.

Until the first time you write a mapreduce.

I had to look that up.

A MapReduce program is composed of a map procedure, which performs filtering and sorting (such as sorting students by first name into queues, one queue for each name), and a reduce method, which performs a summary operation (such as counting the number of students in each queue, yielding name frequencies)

That part is pretty vanilla functional programming .

JavaScript:

const foo = myArray
    .map(fn1)
    .reduce(fn2);

I guess it’s the parallelization and distribution part that makes “mapreduce” it’s own thing but the name is a bit generic.

[Gators1]

@Hog yeah it’s about parallelization. These days the applications are mostly straight SQL and the distribution happens on the back end unless you want to add some tuning commands and depending on the platform you use.