Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

“It's The Future”

circleci.com

Post reply on HN
Print view View original

321–330 of 536 posts

Re: “It's The Future”

#321

Post by mamcx »

rajeshp1986 wrote: post #109

The article perfectly summarizes my frustration and sentiment. These days I hear these buzzwords all time. I work as a consultant for an enterprise product and most people whom I meet they somehow catch these buzzwords and blurt it out in front of everyone during meetings and discussions to either showoff that they know technology and things that are in the market these days(also latest iphone, apple news, tesla, spa…

This is how we manage this problem at the times when Visual Basic was the king and we use instead Visual FoxPro.

People want theirs apps to be made with Visual Studio (BTW, FoxPro was part of the package).

So they ask: "In what is the app made"?

"In Visual, Sir."

Done. End of story (like most of the time, obviously some times people are more dangerous and press it ;) ).

----

The point is not focus in the exact word but in what the people know the word will give to them.

So, for example "Big Data". The meaning for us matter zero. The meaning to some customer is that it have a largeish excel file that with his current methods and tools take too long to get results.

So. Do you use "Big Data Tools"?

"Yes Sir."

And what about use Hadoop?

"We use the parts of big data tech necessary for solve this, and if we need to use hadoop or other similar tools that fit better with your industry and that use the same principles will depend in our evaluation. Not worry, we know this"

Or something like that ;). Know that worry the people behind the words have help me a lot, even with people with WORSE tech skills (damm, I have build apps for almost iliterate people with big pockets but only witch cellphones as references of tech!)

And the anecdote about the largeish excel file that was too big and take too long? Yep, true. And was for one of the largest companies in my country ;)

Re: “It's The Future”

#322

Post by sanderjd »

vonmoltke wrote: post #296
wtbob wrote: post #259

Earlier quoted context omitted.

> If another team breaks your build in a monolithic repo, you may or may not be able to resolve this quickly. With a monolithic repo done right, the other teams broke their build of their branch, and it's up to them to resolve it. You, meanwhile, are perfectly happy working on your branch. When their changes are mergeable into trunk, then they may merge them, not before — and likewise for you. With multiple repos, th…

> With multiple repos, they break your build, but don't know it. You don't know it either, until you update your copies of their repos — and now you have to figure out what they did, and why, and how to update your logic to handle their new control flow, and then you update again and get to do it again, until finally you ragequit and go live in a log cabin with neither electricity nor running water. I don't see how t…

> If it broke, don't pull the project with the breaking changes.

I agree with the overall sentiment of your comment, but the quoted part is where I've seen trouble brew. The tendency is to be conservative about pulling updates to dependencies, which can easily get you into a very awkward state when a critical update eventually sits on top of a bunch of updates you didn't take because they broke you. It is usually better to be forced to handle the breakage immediately, one way or another.

Re: “It's The Future”

#323

Post by discordianfish »

ryanmaynard wrote: post #232
rajeshp1986 wrote: post #109

The article perfectly summarizes my frustration and sentiment. These days I hear these buzzwords all time. I work as a consultant for an enterprise product and most people whom I meet they somehow catch these buzzwords and blurt it out in front of everyone during meetings and discussions to either showoff that they know technology and things that are in the market these days(also latest iphone, apple news, tesla, spa…

> I am frustrated by the industry as a whole. I feel industry is simply following marketing trends. My work lands me in a number of different conferences in non-software industries. This is true for all industries. Its just that ours has a faster revolving door. That, in addition to a low barrier to entry (anyone can claim they're a web developer), leads to a higher degree of this madness. Its just part of human beha…

Another way to signal others that you, too, are an insider is by calling a current trend a hype.

Re: “It's The Future”

#324

Post by fl0wenol »

Waterluvian wrote: post #268
huuu wrote: post #160

Earlier quoted context omitted.

"I am frustrated by the industry as a whole" Unfortunately I have to agree as a developer. My job is to make a fast, reliable, stable product but at the same time I'm questioned the tools I use by people who don't have any knowledge but heard the latest trend. But sometimes it's also very easy to please people. Big data: just insert 10M records in a database and suddenly everyone is happy because they now have big da…

These discussions are perfect examples of why building good social skills can be more important than learning the next greatest programming language 5.0.

I love you for saying this because it needs to be said.

Thank you.

Re: “It's The Future”

#325

Post by IshKebab »

mbrock wrote: post #203
IshKebab wrote: post #194

Earlier quoted context omitted.

How often do you actually need to do that. 99% of `foo | bar` command could easily be `foo > a && bar < a` which is pretty trivial to do in Python.

Well, how do you write that in Python? I'm curious because these simple things that are delightfully easy in bash often turn out to be surprisingly tedious in other languages. Of course, some things are tedious in bash too. But a basic principle of shell scripting is that you call other programs to do the stuff you don't want to do in shell.

Like this: http://stackoverflow.com/a/1996540

I agree it is tedious, but to be honest, reading and writing to stdin/out isn't something that would commonly need to be done in a robust system. If the world were perfect you would use library functions.

I definitely think there is scope for a language that works well as an interactive shell, and as a general purpose language. They have somewhat conflicting constraints but I'm sure we can do better than Bash. Have you seen how [ is implemented?

Re: “It's The Future”

#326

Post by Svenskunganka »

alexandre_m wrote: post #267
IshKebab wrote: post #186

Earlier quoted context omitted.

Doesn't statically compiling programs solve the deployment issue better? I mean, as far as I can tell Docker only exists because it's impossible to link to glibc statically, so it's virtually impossible to make Linux binaries that are even vaguely portable. Except now Go and Rust make it very easy to compile static Linux binaries that don't depend on glibc, and even cross-compile them easily. Hell I think it's actual…

Binaries are one thing, but there are the other abstractions that containers bring in regard to networking and storage. You expose what are the network APIs of your apps (e.g open ports), filesystem mounts, variables (12 factors), etc. Your application becomes a block that you can assemble for a particular deployment; add some environment variables, connect a volume with a particular driver to a different storage bac…

> add some environment variables, connect a volume with a particular driver to a different storage backend, connect with an overlay to be able to talk to other containers privately across different servers or even DCs, etc.

But environment variables already exists without docker. Volumes already exists, aka partitions. "Overlay network" already exists, aka unix sockets or plain TCP/UDP/etc over the loopback interface.

I'm not trying to be a dick here, it's just that the points you brought up doesn't really bring anything new to the table. How is this different from just having a couple bare-metal or virtual machines behind a proxy?

There are some aspects to containerization that are very feasible, but only at certain scales and the points you brought up makes me question whether you perhaps might be over-engineering things a bit.

Re: “It's The Future”

#327

Post by jondubois »

nbevans wrote: post #65
jondubois wrote: post #15

Earlier quoted context omitted.

Um no, Rancher is open source can run and manage ANY infrastructure (including Amazon EC2) - You can run it on your own datacenter or even on your own local machine. Also Baasil.io is essentially just a control panel/dashboard (Rancher-as-a-service), you can quit Baasil.io at any time and switch to your own hosted Rancher instance and you don't have to change any of your application code or change infrastructure prov…

I took one look at "baasil.io" and saw the typical landing page with a "Plans" link at the top and questioned why anyone would want to take a dependency on this. If there is some OSS project behind the plan-based charade then that's fine. "Also Baasil.io is essentially just a control panel/dashboard (Rancher-as-a-service), you can quit Baasil.io at any time and switch to your own hosted Rancher instance and you don't…

The main benefit of Baasil.io is that it offers developers a boilerplate/framework which they can extend with their own code (to build scalable realtime apps and services) - Any app/service built on top of this boilerplate can be automatically scaled to 1000 hosts/nodes using a single command.

Users don't have to use Baasil.io, but if they do, they will get the best possible support - For example, a customer can give us access to their Rancher control panel and this would allow us to SSH into their machines to help resolve any problems in a hands-on way.

It's probably more accurate to describe it as "DevOps as a service - With a focus on realtime apps/services". The value proposition is probably closest to Cloud 66 http://www.cloud66.com/ except more focused on realtime apps.

Another similar service is Zeit.co https://zeit.co/ - Except Zeit.co only runs Node.js. Baasil.io can be extended with components written in any language.

Re: “It's The Future”

#328

Post by szxnyc »

rajeshp1986 wrote: post #109

The article perfectly summarizes my frustration and sentiment. These days I hear these buzzwords all time. I work as a consultant for an enterprise product and most people whom I meet they somehow catch these buzzwords and blurt it out in front of everyone during meetings and discussions to either showoff that they know technology and things that are in the market these days(also latest iphone, apple news, tesla, spa…

Yea, but does it scale?

Re: “It's The Future”

#329

Post by gizzlon »

droidist2 wrote: post #133
robteix wrote: post #62

"Why don’t I just use Google’s thing? "-You think that’s going to be around in 6 months?" Isn't reputation a thing of beauty?

So true. Why people often use "it's backed by Google" as an argument in favor of anything is beyond me.

Hasn't App Engine been around for more than 4 years by now?

Re: “It's The Future”

#330

Post by ryanmaynard »

discordianfish wrote: post #323
ryanmaynard wrote: post #232

Earlier quoted context omitted.

> I am frustrated by the industry as a whole. I feel industry is simply following marketing trends. My work lands me in a number of different conferences in non-software industries. This is true for all industries. Its just that ours has a faster revolving door. That, in addition to a low barrier to entry (anyone can claim they're a web developer), leads to a higher degree of this madness. Its just part of human beha…

Another way to signal others that you, too, are an insider is by calling a current trend a hype.

I agree, and am guilty as charged.
Post reply on HN