Live data from Hacker News

The cloudy layers of modern-day programming

vickiboykis.com

121–130 of 177 posts

Re: The cloudy layers of modern-day programming

#121
post #90
post #85

Earlier quoted context omitted.

Or, just don't work in webapps. Get into embedded programming. Or join a games studio. I have a friend who is writing code to run on a sort of exoskeleton meant to benefit disabled people and help them walk. He has never in his life "deployed to the cloud" and wouldn't have the foggiest idea of how to do it.

It’s only a matter of time before someone realizes how helpful a GPS transmitter would be in an exoskeleton for disabled people. Now you have a cloud component.

You know that all GPS transmitters are in space, right? GPS is a unidirectional technology where GPS receivers don't (and can't) talk back to GPS satellites in any way.

Re: The cloudy layers of modern-day programming

#122
post #90

Earlier quoted context omitted.

It’s only a matter of time before someone realizes how helpful a GPS transmitter would be in an exoskeleton for disabled people. Now you have a cloud component.

You know that all GPS transmitters are in space, right? GPS is a unidirectional technology where GPS receivers don't (and can't) talk back to GPS satellites in any way.

If the caretaker wants to get the coordinates back, then you have to go through a server at some point. I think GP was thinking along the lines of something like Find My iPhone, where the GPS coordinates are sent to the cloud. You will need a mobile baseband radio alongside the GPS receiver.

Re: The cloudy layers of modern-day programming

#123
post #90

Earlier quoted context omitted.

It’s only a matter of time before someone realizes how helpful a GPS transmitter would be in an exoskeleton for disabled people. Now you have a cloud component.

I wouldn’t call GPS the cloud

Yeah it's way beyond that

Re: The cloudy layers of modern-day programming

#124
I agree that most of the routine software work feels like, umm, filling forms? The way I've made peace with it is to accept that the work that pays the bills is going to be boring. After considering ourselves to be special as software developers for many years, maybe we accept that it is not so special after all, like flipping burgers.

Two ways to out from the existential dread: one startup on a problem statement that feels exciting to you, so that you get to pick your tools, processes and what not. But this is not a realistic/affordable option for most people. Also, if your startup achieves even a moderate level of success, you'll be back to solving boring problems.

The other is to find a pockets of software development outside work, where you can still solve interesting problems, like developing small games. Joseph White, who created the famed programmable fantasy game console Pico-8 alludes to this (https://youtu.be/87jfTIWosBw?t=1080) ! It was an explicit goal to build a tool to solve cute, interesting problems because routine software development feels like glueing things together. The whole youtube talk linked above is worth watching. But the trick here is to forgo commercial motivations. People make fun, cute little games on Pico 8, distribute them as cartridges. Occasionally, there's a hit like Celeste. But otherwise its a small community of people solving problems and building things just for fun.

Re: The cloudy layers of modern-day programming

#125
Quote: "Although it’s something I’ve only thought about recently, top computer scientists have been recognizing this as a problem for at least the past ten years"

10 years? Try since the dawn of computing, this was always a problem. Wanna know the most famous one, older than 50 years? Here it is:

In 1969, when Apollo mission on moon was live broadcasted by all the TV networks around the world, the image is of a grainy white and black, despite the fact that both NASA and TV stations already had color transmissions. Why? Because of the incompatibility of NASA transmission (which was a format more closer to our current HD - btw, can you imagine having HD format being common in 1969?) with NTSC/PAL systems at the time.

And what was the "API" that bridged (or in terms of the article "VendorOps") married these 2 incompatible formats? Use a projector on a wall and all TV stations filmed that wall instead of getting the real transmission. What a shame. Also NASA handling of the role films is abysmal, to say the least (https://www.nasa.gov/feature/not-unsolved-mysteries-the-lost...)

Re: The cloudy layers of modern-day programming

#126
post #83

Earlier quoted context omitted.

Challenge yourself to use stdlib only for a while, or the future. It sounds unrealistic and I'm going to get flamed, but hear me out. It works. Most of my development these days is in reasonably complete languages like go, rust, zig, and various scripting languages, so your mileage may vary if you're writing in something like rune, hare or carbon that is still taking shape. If you think I'm crazy but have a lingering…

I'm not gonna flame you, but I will note that, as someone who gets paid to use my judgement to decide on the optimal trade-off between quality, time spent on the project, and its future maintainability... I feel like all three will suffer quite a bit with this self imposed "handicap".

[deleted]

Re: The cloudy layers of modern-day programming

#127
post #30

Earlier quoted context omitted.

> Today, I can deploy a high available cluster in minutes using any cloud technology + kubernetes and my favourite web framework. I think the point is (at least for me it is), when you do that, have you done anything new that few or nobody else has done before? No, it's just a well worn path which thousands of organizations have done already.

We blaze through those well-worn paths so that we can quickly get back to the interesting things. I orchestrate clusters at a high level and still get to solve difficult, stimulating problems every day. The world of software development is immense. You can treat it like a job, or like a creative path, but to synergize both requires a lot of effort. Complaining that there aren't interesting programming jobs comes acro…

> We blaze through those well-worn paths so that we can quickly get back to the interesting things.

I could sign up for that! But what interesting things? That cluster will in nearly all companies just be used for yet another CRUD API supporting yet another social or adware platform. Yawn, please no.

If you are aware of companies doing actual intellectually creative programming anymore, please share them. I have no doubt they exist, but they are becoming way too rare.

Re: The cloudy layers of modern-day programming

#128
Summary:

The cloud takes inefficiency to a whole new level.

Cloud vendor tools are designed to sell cloud services, not solve developer problems.

Jupyter notebooks are buggy and unnecessary (You can execute Python without a browser) and won’t work with medium sized data sets.

Excel handles larger datasets than pandas and small datasets more efficiently.

You could parse the 2gb of data from goodreads easily on a 486 in a raw text file about as fast, but fetching the data over a 14400kbps modem would take all day.

Re: The cloudy layers of modern-day programming

#129

Earlier quoted context omitted.

> Nowadays when it's just gluing frameworks together and configuring AWS services... it doesn't really feel any different intellectually than cleaning toilets. Comparing your six figure white collar job to basic janitorial work is pretty damn cringe and pretty objectively untrue.

OK, what if we say plumbing then? Same idea, and the pay is within an order of magnitude at the median.

Some developers even make more than plumbers.

Re: The cloudy layers of modern-day programming

#130
post #38
post #4

oh yea. using a software framework like django for "rapid application development" gives me a feeling closer to writing configuration files rather than actually "programming" (where "programming" is writing hardcore algorithms). but don't get me wrong, I liked doing that, I got paid to do it. But let's call it for what it is: that python code (django app) was really django framework config. this is a simlar phenomeno…

I think you nailed it with configuration vs programming. modern software development is configuration. notice that "development" is not programming either. so this trend has been going for long time

Good development is 99% configuration.

The problem is, that the tools and frameworks we use have such bad configuration.

Post reply on HN