GitHub having a separate Discussions board might accelerate 1) over time. There it is more encouraged to ask more open ended questions than on Issues, and they explicitly have Q&A type features like marking as answered.
Interesting! Are you planning to keep recollecting data for the year 2023?
> the major job offer portal in Germany for over one year
I hope that's Linkedin. Because if it's another site like Monster, StepStone or similars, I'm afraid the data is probably garbage. I don't know a single engineer in Germany who uses anything but Linkedin (well, many engineers use niche job boards like remoteok, or directly use the company's career section... but no single one uses Monster/StepStone/Glassdoor, because they are total crap)
Edit: the data source seems to be stepstone.de. That's unfortunate. Is there any chance to run this against Linkedin for 2023? That would be awesome!
seems stepstone is the only source... perhaps try to compare against "agentur für arbeit", see https://github.com/bundesAPI/jobsuche-api (there are multiple issues with the api - some parts/parameters are broken....)
Interesting to see many comments regarding "Go is my favourite programming tool, but not my favourite programming language". I totally agree. I love the tooling (go build, go fmt, etc.), the performance, the ecosystem... but the language itself is not the best out there. I would love a mix between Python and Go: Python as the language with Go's tooling. That would be amazing!
The most important asset I have is my bank account. In case of death, wife can take over (the only thing needed from wife is to proof she's my wife... so pretty much her ID card and marriage papers). That's it. Subscriptions? GitHub account with private side projects? Digital libraries? HN account? Email? All of that is not that important. If my wife has access to my bank account she can either transfer all of it to hers and effectively cancelling all my subscriptions or reject individual subscriptions manually.
A note on photos: If you use Google Photos you can have photos with a specific person automatically added to a shared album. So my wife can always see every photo I take of her or our daughter. I just did it for day to day convenience but it'll also come in handy if I pass since she'll have all the most important photos already.
Yep, 95% of anyone's needs in this regard can be taken care of by a spouse or relative, possibly with the aid of a death certificate. I highly doubt anyone would be interested in taking over most of my digital files.
What if you have children? In Turkey the bank account can be taken over only by legal inheritors, and all of them should be present together physically at the same time in the bank with a document, most of the time obtained from notary, called inheritance document (plus a document that shows that there is no debt). Inheritors in a normal family are spouse and children. Ratio for inheritance for a children and spouse are different. Spouse gets most of the inheritance.
It needs to be Plan A, as well. But a shortcut to get access to your accounts without having to go through a will and lawyer will be appreciated by your wife if only you die.
Who's the real target audience of these kind of tools?
- Developers who work at a company (e.g., as employee) and need to spit out features every sprint? Velocity is important, so I imagine these kind of developers need to squeeze every minute they are in front of the screen in order to produce working code?
- Developers who think of written code as one way to solve (tech) problems, so they don't really care much about the process of creating code, but mainly about the output (i.e., does the running program solves the issue at hand?)
- Senior developers who don't like to write boilerplate code?
I don't see myself as the target audience of Copilot or Ghostwriter. I do work as an employee, but I'm not a "feature machine". Usually the hardest part about my job is solving problems while communicating with other people. I don't need to write code "fast", and by the time I hit the keyboard to start coding, I don't really need that much help (granted, I'm not working on code that goes into space rockets... just normal e-commerce stuff)
I like to work on side projects and learn new technologies. When I was starting with programming, as part of the learning I liked to write boilerplate code (actually, that's how I learnt programming. I remember writing C boilerplate code by reading "The C Programming Language". Skipping the "boring" parts wouldn't have helped me in my learning).
If any, Copilot and similar tools take away all the joy of actually writing code (because, when I work on side projects, 50% of the satisfaction comes from actually writing code for the sake of writing code. The other 50% comes from the ability to solve a problem). So, yeah, maybe for the people like me who does find the act of writing code for the sake of writing code (you know like painting or taking photographs), Copilot seems like an unneeded tool?
> If any, Copilot and similar tools take away all the joy of actually writing code
I like to challenge my own beliefs, and I reluctantly tried it out. At least I would have a basis for my criticism, so I thought. I'm about 10 hours into using it, maybe.
If anything it has increased the joy of writing code for me. It eliminates the mundane busy work and lets me focus on solving problems. For me, the "real" coding happens in my head, putting it into an editor is just process. I still also have to check it's work whenever I use it, so I'm still deeply embedded in the coding process.
I believe it's akin to an easel vs Krita/Photoshop. Some people enjoy interacting with the physical medium, others enjoy the creative process.
I would strongly recommend trying it out in anger (i.e. a reasonably real codebase), at least for 30 minutes. Form a better opinion after that (which may well be the same as yours right now).
For reference: I've been coding since I was 8 (almost 30 years).
For me, not a senior dev, Copilot is useful for: discovering API, generating parts of docstrings, and generating bits of code that don't require too much thinking but go beyond simple copy and paste. It is really quite useful and helps to keep my RSI in check.
My primary UX issue with copilot is that it is trying too hard to be helpful, often suggesting code that I don't need. You also can't trust it with more complex cases but that's actually pretty reassuring : - )
I would like to give some context, still not onboard with these tools but we have a lot of chore like work of adding some very similar things but with some changes, complicated or otherwise.
So we have been considering using Codex or something for generating the code in a more streamlined version, the key reason of it being a benefit is we are a small team with each person owning more than one large repositories. It's gotten very annoying and our pace is far slower than what we would like, here something like this makes quite a lot of sense.
Though the problem with such specific tools is they can't generate any customized code for our codebase, we can finetune other codegen models and that's what we plan to do down the line, but this specific tool just not really useful if it can't specialized for our codebase.
So, does your team then spend considerable amount of time writing boilerplate/chore code? Isn't that a sign of: "Hey, we actually need to improve our code base guys!". I don't know, if your solution to "I don't want to write chore code" is "let's use Copilot to do the boring stuff"... well, I have bad news for you: "chore code" needs to be maintained and/or fixed, and I don't think Copilot maintains code (for now... :D)
yeah we work on linters, tooling and the like highly specific single page, highly similar code.
you can't get around it. We have pretty low boilerplate in all the codebases I happen to manage but the sad part is there is no getting around porting of specific rules, setting up better metric analysis and reporting systems and such.
If you have been involved in programming professionally for a while, you would know you just can't get around the chore like works sometimes. Ofc it's not a long term goal to keep going this way but we needed a solution to simplify our challenges as we move on.
I admit I haven't used it (I have used IDE autocomplete features and don't like them)
For me, same as writing actually, the thinking of what I want to do is everything, and the doing it is nearly trivial. I don't picture having copilot write nontrivial code for me and then reviewing it would be different than writing it, even if I didn't know the exact syntax and had to look it up. So I agree, it feels like a solution to a problem I don't have, like is solves something that I don't spend time on.
Cynically, like GPT-3 probably help write content farm stuff, copilot probably helps write some junk code for something, but there are probably domain specific low code tools that do that better as well
I love writing code, but I don't love searching the docs for the sixtieth time to find the correct combination of brackets, .groupBy's and .agg calls that gets the baroque horrorshow that is python's Pandas lib to wrangle some data for me.
See it as a better autocomplete for people who don't want to or can't learn by diligently doing the boring parts.
> In order for her to work on the movie while out, they had plugged the machine up to the local network and copied the whole file tree over.
Now image the same situation in 2022:
- there is no acceptable backup for the whole movie (or let's say, app)
- only you know there is one acceptable copy... but it's on your personal laptop. You did copy it back in the day because, well, let's say you wanted to run the app in our local machine
There is no way you would tell your team/boss: "Hey guys, no worries! I have a perfect copy of it!", because why on earth did you copy work material into your personal laptop?! That's the rule number 1 of every modern tech company: don't mix work stuff with personal laptop (and the other way around: don't use work laptop for personal stuff).
- If you can trust an employee with a $25K ($50K today) computer, trusting them with a complete source tree isn't a stretch.
- I'd be more pissed off that somebody didn't have a complete backup somewhere, even if it was a personal laptop they used for work.
- Back then, most people didn't have home computers. Hell nowadays a home pc isn't a guarantee, as most of my (non-engineering) coworkers only have cellphones and ipads at home. And while I agree don't mix work and play, most of these people do.
The computer in question was a Silicon Graphics workstation (pictured in the article). What the image does not convey is the sheer gargantuan size of SG machines. Desktop computing it may have been, but in some cases people actually used their SG boxes as physical desktops.
The SG Octane that features in this story was actually one of the more petit versions, but still it would take two people to move comfortably.
> The story likely takes place in 1998, though Jacob admits he’s foggy on the exact date.
In 1998 we were living in Internet Time. The amount of stuff that changed from '97 to '98 and from '98 to '99 made people's heads spin. Google incorporated in September of 1998. 56K modems were brand new that year. At the end of 1999 when Toy Story 2 came out, Napster had been out for 5 months, and Java 1.2 was just about to exit from beta into general availability.
People were still introducing each other to WinAmp when they started storyboarding this movie.
True. Most of the people I knew with computers back then had them provided by their work, or bought them for university.
But then I lived in a small city in Texas not near a major metro. Most people there didn't buy a home pc until the DotCom boom brought those cheap emachines.
And by the next year that had jumped to 56% and 50% respectively. That's 25 million Americans who got the Internet in a 12 month period. And that 2000 number was up from 36.6% and 18% in 1997.
You can't project backward two years from a 2000 number during that era. You're missing data points during the steepest part of the curve.
Susman was the Supervising Technical Director and the machine was a Silicon Graphics workstation. Certainly sounds like she was given a work machine to do her job.
I think we are exaggerating. I started a new position 5 months ago (with a significant raise of around 20% my previous salary). Within these 5 months the company fired a significant portion of their employees (some techies, but mainly non-techies like HR); it made it to HN (not the front-page I think). Hiring freeze for around 3 months... but since about a month ago they started to hire again. Now on Linkedin you can see the company is posting around 200 job offers... although, sure before the lay-off they had like around 1000 job offers (crazy).
My point is: if you go to Linkedin right now and filter by location=Europe, remote=yes, you get like 160K job offers (tech ones). Sure, you can filter down that number by removing managerial positions and other roles you are not interested in, but the thing is companies are still hiring (not all of them, but the majority).
Most of those EU remote jobs will not even glance at your resume twice if you don't have x years of experience in their stack. I know this because I just ended a two month long interview loop for remote positions within EU as a senior developer who only has C# experience(on paper). There were literally two companies that would give me time even though I didn't have experience in JS and Go respectively, one of them also offered very much under market average salary. European job market is retarded like that, still living in ages where companies think you can't learn any other web framework in a week even if you worked with another one for years. I actually hated interviewing these last two months, granted I didn't even try to approach faang level companies, still, most processes are terrible, long and even disrespectful. Also for the LinkedIn "remote+EU" search you mentioned, a lot of companies on LinkedIn will list remote but in fact will not hire outside country they're in. You will only find out if recruiter graciously tells you that, most will just ignore you. I found it baffling considering that you can simply invoice them within EU but suddenly it's a problem.
Product developer (or Product Engineer since we use the word engineer everywhere). Compare team A = {software engineer, product engineer, design engineer, qa engineer}, and team B = { software engineer, product manager, design engineer, qa engineer }. Team A screams "all team members collaborate the same way when it comes to build a product". Team B screams "there is 1 manager, and the rest are not"
1. GitHub. Many times I have found my answer to a problem with a specific library/framework in GitHub issues.
2. Seniority. As I gain more experience, I tend to ask/answer less in SO. From time to time I still read answers.
3. To a lesser extent, chatgpt. I usually have to double check the outputs, but it works fine some times