News for hackers. Stuff that matters.
Re:Advice to Aimless, Excited Programmers (2010) by amonith on Wednesday March 01, 2023 @07:51AM (#34981795)
Good advice to advance your career, but I'd say there's nothing wrong with being passionate/excited about the craft and not the result. Newbies should just be aware that this can affect their career (they will have better job security as they won't be picky about the domain, but they will probably earn less as they won't ever be domain experts).

There are endless examples from other "industries". There are people that love painting, but never care who sees their work. They love the creative process. There are people that love carpentry, but hate doing utilitarian furniture that sells well. They love how zen manual labor can be and that the result is physical.

It's not "wrong-way-aroundness", it's just a different goal.

Re:Advice to Aimless, Excited Programmers (2010) by Ensorceled on Wednesday March 01, 2023 @08:36AM (#34982211)
I disagree, imagine if someone showed up to a construction site and said "I bought a new hammer and have little to no idea how to use it, are there any cool or important projects I can pound nails into?"

If it was my home, I would hope the crew boss would tell them to go build a shed or something first.

Re:Advice to Aimless, Excited Programmers (2010) by amonith on Wednesday March 01, 2023 @08:43AM (#34982281)
In this scenario he'd just be told exactly which nails to pound and his work would be inspected. This is a very good example actually, construction work is a really popular summer gig for students in my country (Poland). They know nothing and don't care about the domain (building houses), they just follow supervisors and the designs. You can't give them an entire house to build, but they are very useful and cheap members of the crew.

They'll never be architects (they don't want to), but they'll earn enough to buy whatever students want and they'll always find some work no matter what is being built and where.

Re:Advice to Aimless, Excited Programmers (2010) by AuthorizedCust on Wednesday March 01, 2023 @08:46AM (#34982307)
In other words, the supervisor holds the vision of the output, and that person assures that the people interested in the craft are acting towards creating the desired output.
Re:Advice to Aimless, Excited Programmers (2010) by baremetal on Wednesday March 01, 2023 @11:31AM (#34984234)
1. A supervisor will demonstrate what is expected.

2. Then the worker tries it while the supervisor watches.

3. Feedback is given

4. Repeat 2-4 until satisfactory work is achieved.

Depending on the task this may be as little as 5 minutes for something simple or much longer for more complicated things.[1]

[1] I own a rough framing business

Re:Advice to Aimless, Excited Programmers (2010) by aynyc on Wednesday March 01, 2023 @08:53AM (#34982383)
I worked construction in high school and college in the US. This is not how it generally works. If you are a high school kid, your summer construction gig is usually slave labor, meaning carrying ton of stuff up and down, cleaning stuff as you go and be a general gopher. You don't do anything remotely close to the construction of the house. The only exception is being a roofer, which you just tar stuff with other crew members.
Re:Advice to Aimless, Excited Programmers (2010) by moremetadata on Wednesday March 01, 2023 @09:32AM (#34982802)
There isnt anything stopping you from asking questions like why is something done this way. You might see it as slave labour, but if you laid bricks for example, you cant lay bricks in temperatures below 3 or 4 degrees C, and you can only lay so many rows of bricks high as the mortar has to set.

Where most people are failed by those around them, like parents and school's is pointing out when you leave education, you wont stop learning, and its always good to ask questions and plan ahead what you want to do with your life.

Arguably have a bucket list which will change as you age in order to have something to aim for, and dont get caught in the trap of settling for second best or end up being used by people who think might be your friends but only knew you because of what you could do for them on the cheap.

Now you might have called your summer job slave labour, I look at it as being paid to exercise as well as learning new skills and make new contacts.

On the subject of aimless excited programmers, there's lots of ways to look at programming before learning a language.

If one wants to earn a lot of money, then consider database related programming, everything is data, even spreadsheets can be considered flat files of sorts. And whilst you probably wouldnt use javascript to write a database app in, even though you could stuff data into a cookie and run it client side, there are better general purpose languages suited to database work, besides the obvious sql languages.

If chasing the money, consider looking at what's involved in high frequency trading where you'll be writing your own OS to maintain the super high speeds required for algorithmic trading. Co-locating data centres as close as possible to trading exchanges is just one part of the problem. [1]

IF you want to do apps for smart phones, again look at the languages that deliver the most for you, but also consider whether you should go with a popular language like dotnet or java thats portable across platforms, or whether you want to go with a niche language that might become less popular over time especially when considering there are thousands of languages that exist, with many having fallen by the wayside.

[1] https://www.ted.com/talks/kevin_slavin_how_algorithms_shape_...

Re:Advice to Aimless, Excited Programmers (2010) by amonith on Wednesday March 01, 2023 @09:12AM (#34982586)
I think that's a bit outside of the topic. The comparison is not perfect of course. The point is that enjoying the process and not caring about the result is more than enough. If you enjoy the process of tiling and you have some experience with tiling, you don't have to care about what kind of building/room you are working on. Somebody designed the room, somebody picked the right materials, somebody probably bought them and it's in the spec/design. You can just "tile away" and make a career out of it.

Similarly in software, if you care only about programming and languages and whatnot and not the product - it's all you need with the right team/org. You won't be a product owner and you wont advance to "decision-making" levels in the company, but if you don't want to why would you need to.

Re:Advice to Aimless, Excited Programmers (2010) by aynyc on Wednesday March 01, 2023 @10:29AM (#34983405)
I can't really agree to what you are describing, despite the fact that certain parts of my career, I fit your description perfectly.

The issue I have with is the statement of "make a career out of it". I don't think you can, at least not in the software industry, a lot of folks are perfectly competent developers but can't move forward and eventually get replaced by younger/cheaper developers because they are basically doing the same thing for the past 10 years.

I agree with having passions for something, but making a career out of it is a lot harder if you don't do the "extra".

Re:Advice to Aimless, Excited Programmers (2010) by amonith on Wednesday March 01, 2023 @02:41PM (#34987249)
> a lot of folks are perfectly competent developers but can't move forward and eventually get replaced by younger/cheaper developers because they are basically doing the same thing for the past 10 years

I'd argue that they are replaced (if they are, because I'm not sure, there are not a lot of old folk because IT industry is pretty young, I already worked with a few 50+ mid devs and the pay is kinda reverse, because old folk already have homes and don't need to pay off huge mortgages) not because they didn't get promoted (mid dev -> product owner / domain expert) but because they stopped upgrading the skills relevant to their current job.

So in terms of the example presented by the author it would be developers that are no longer even hyped about languages/tools. And in our imaginary "tiling specialist" it would be a guy that didn't care that the current fad is some kind of funky pattern + new material of tiles and still wanted to lay old ceramic square tiles for his entire life.

I'm still not convinced that there is a scenario where you __have to__ care about "the domain" / "the problem being solved" / "the bigger picture" that much. You can, it will improve some aspects of your career, but you don't have to and it would degrade other aspects of said career (we all have about 16h max productive hours daily, and I'm being generous).

Re:Advice to Aimless, Excited Programmers (2010) by tom-thistime on Wednesday March 01, 2023 @09:38AM (#34982867)
Feels like a central issue. I find a lot to agree with here, and a lot to agree with in the comment you're responding to.
Re:Advice to Aimless, Excited Programmers (2010) by Ensorceled on Wednesday March 01, 2023 @10:02AM (#34983125)
I think the original articles message could boil down to "start small" and people are taking that to mean "don't start"
Re:Advice to Aimless, Excited Programmers (2010) by marcosdumay on Wednesday March 01, 2023 @10:22AM (#34983333)
That sounds a bit out of place in a construction site, but every mechanical shop has something to try the new hammer on, and the equivalent in a physics lab would stop everybody so they bring stuff to try the hammer on.

The difference is mostly of culture, and seems completely irrelevant to what you are trying to say.

Re:Advice to Aimless, Excited Programmers (2010) by khaledh on Wednesday March 01, 2023 @08:56AM (#34982422)
Well said. I spend my day doing professional software development in a particular domain, where I solve real, tangible problems. In the evening I like to spend some time on aimless programming, tinkering with new languages, technologies, tools, etc. I do it for the enjoyment of the learning and the creative process as you mentioned, with no particular goal in mind.
Re:Advice to Aimless, Excited Programmers (2010) by alvis on Wednesday March 01, 2023 @09:14AM (#34982602)
There are 2 things that excite human -- learning and realisation. The author pointed out the way how to realise a thing.

But as many are also saying, being aimless is an opportunity to learn, explore and discover new possibilities. It's like how many of us are playing with ChatGPT at the moment. It's a journey of discovery that can lead you to realise the potential and create something truly amazing in later time. Would anyone say porting ChatGPT to many existing applications aimless?

Re:Advice to Aimless, Excited Programmers (2010) by shanebellone on Wednesday March 01, 2023 @10:09AM (#34983188)
"Would anyone say porting ChatGPT to many existing applications aimless?"

I would. It's FOMO not innovation.

Re:Advice to Aimless, Excited Programmers (2010) by solarmist on Wednesday March 01, 2023 @11:41AM (#34984420)
Until it is innovation.

The problem is you can't tell which it'll be in advance.

Re:Advice to Aimless, Excited Programmers (2010) by shanebellone on Wednesday March 01, 2023 @11:52AM (#34984605)
Can you name one innovation derived from a remixed API?
Re:Advice to Aimless, Excited Programmers (2010) by bdcravens on Wednesday March 01, 2023 @09:49AM (#34982996)
Fortunately in software you can pursue your passions in your free time for no pay.
Re:Advice to Aimless, Excited Programmers (2010) by Dave3of5 on Wednesday March 01, 2023 @10:09AM (#34983195)
> but they will probably earn less as they won't ever be domain experts

I disagree.

I've rarely seen any programmers that are domain experts, most of those domain experts are actually hired in a consultancy role.

As they work through the projects programmers can become very familiar to a specific domain but in general that's not their job and they will be treated as such. They will be consulted on implementation but less likely, if at all, on strategy. Which is what I would expect from a domain expert i.e. a consultant.

The highest paid programmers move jobs most often the lowest paid don't that'll tell you what becoming a domain expert means for a programmer.

Re:Advice to Aimless, Excited Programmers (2010) by dasil003 on Wednesday March 01, 2023 @10:55AM (#34983696)
While it's true that in practice most programmers are bricklayers (especially given the growth of the industry leading to a young-skewing population), that doesn't invalidate the GP's thesis that domain expertise is a good lever for compensation growth. The biggest mistakes and greatest successes of my programming career have always been related to the breadth of my understanding of the product domain and UX that I was operating in.

The other thing I find curious in your comment is the implication that strategy is usually set by domain experts who tend to be consultants. This very much runs counter to my experience, where consultants are brought in for specific jobs or problems where an outside perspective is needed, but generally those things are scope-boxed or time-boxed tangents to the business. The big strategy is generally set by leaders and influencers within the company via a mix of formal and informal venues. These individuals will have the most knowledge of the context specific to that business and how it competes in the marketplace. Consultants, by contrast, can develop a cross-cutting knowledge of industry, which can be a valuable data point well worth paying for, but a company who relies on consultants as the primary driver of strategy is rudderless and probably in decline.

Re:Advice to Aimless, Excited Programmers (2010) by Dave3of5 on Wednesday March 01, 2023 @11:52AM (#34984608)
You are probably thinking of management or business consultants like McKinsey and the like. A lot of companies will hire a consultant as a permanent member of staff when they are working in a specialist domain note they may be called something different like solution architect or suchlike but they are acting as consultant.

I've been in several that had these types. I think the only companies that didn't were companies in industries that didn't need any specific domain experience example here are one that did:

* Oil and Gas (Flow metering)

* Network Timing and Sync testing

* Health and Care (Worked in Care and had several)

* Practice Management

Ones that didn't

* Data analysis

* Data warehousing

Re:Advice to Aimless, Excited Programmers (2010) by jrm4 on Wednesday March 01, 2023 @10:13AM (#34983237)
Hmmm. I don't know, I'd argue these are the people that might just happily write the proverbial DestroyBaghdad function.
Re:Advice to Aimless, Excited Programmers (2010) by greenhearth on Wednesday March 01, 2023 @10:16AM (#34983266)
Yeah, exactly. What if there're no problems to solve? I like the metronome just fine and I want to write a Tetris in Haskell just to see if I can do it, or something like that?
Re:Advice to Aimless, Excited Programmers (2010) by amonith on Wednesday March 01, 2023 @03:06PM (#34987555)
Even if someone created a design that solves "the problem", there are probably thousands of subjects/situations where that design needs to be actually applied. No single software scales infinitely and is infinitely customizable. Some software even is customizable too much and that becomes its own problem.

We need a lot of "bricklayers" that don't care about the problem but can be elastically moved around between projects to implement the ever increasing backlog of "solutions". Entire companies are created that solve that exact problem.

Re:Advice to Aimless, Excited Programmers (2010) by greenhearth on Thursday March 02, 2023 @11:39AM (#34998030)
This is the old Joseph Weizenbaum observation that the computer is a "solution looking for a problem," which, now that you mention it, I think can be applied to the entire tech industry.