121–130 of 301 posts
Programming is tedious when your implementing someone else's vision, thats why I stopped doing it professionally. I still write a ton of code to make my life easier but since I'm not a developer by title I can pick whatever language and tools I want. I often use SQLite just to keep the DBAs out of the picture also.
What do you do now? Are you happier?
The red tape is garroting us. My wife's dev environment VMs are 'remediated' at 8pm regardless if she's using them or not - there is no override policy - and the company is singing the success story of saving 40 dollars in licensing. At another corporation, it can take several weeks to learn how to fill out the IAM role and permission boundaries to allow a new app to run - and a governance board has to review it and…
The red tape is garroting us. My wife's dev environment VMs are 'remediated' at 8pm regardless if she's using them or not - there is no override policy - and the company is singing the success story of saving 40 dollars in licensing. At another corporation, it can take several weeks to learn how to fill out the IAM role and permission boundaries to allow a new app to run - and a governance board has to review it and…
It makes me wonder whether companies should consider hiring more people dedicated to dealing with the red tape to unblock engineers. I suppose managers to a certain extent are the ones doing this work, but in many cases it's not enough, how about a new role that is dedicated to cutting the red tape?
That doesn’t sound like you’re falling out of love with programming. It sounds like you’re frustrated with the red tape at work. Try working on something fun on the side. Make a game, or a mobile app, or something you’ve always been curious about that doesn’t have anything to do with your job. You might be amazed by how productive you feel when you work on something ambitious that doesn’t involve all of the corporate…
The only time I coded anything in the last 3 years (been a manager) was during a hackathon -- I made a videogame that integrated our technology in a novel way to expose a new market segment. It was by far the most engaged I have ever been to the extent that I booked weekend nannies around the clock to get more time put into it, probably 130 hours spent that week. The end result was something I was actually proud of,…
I ask as a matter of curiosity and personal interest--it's something I'd like to learn as a hobbyist, but my knowledge is limited to simple OpenGL tutorials and the (relatively speaking) watered-down Graphics course I took in College years back.
The red tape is garroting us. My wife's dev environment VMs are 'remediated' at 8pm regardless if she's using them or not - there is no override policy - and the company is singing the success story of saving 40 dollars in licensing. At another corporation, it can take several weeks to learn how to fill out the IAM role and permission boundaries to allow a new app to run - and a governance board has to review it and…
This sounds so much like my company. Add in that management will make commitments to customers without having any idea what it will take to execute, schedule 20 hours of meetings per week, expect us to work a total of 60-80 hours a week to meet the arbitrary schedule, and also change priorities seemingly at random based on which customer is making the most noise. The best part is HR regularly talks about how we are a…
Have had this problem so much. The problem is managers and analysts are productive through meetings.
Software Engineers are productive in blocks of 4-6 hours of focused concentration. Many managers don't realize this and forward FYI meeting invites to developers all day long.
I'd argue the current culture is set up to create this very scenario. You've realized that your work is stripped of many elements of creativity in the name of making you replaceable. Of course, we can't say that last part, so we instead talk up how great tooling is, and how quickly we can onboard people (Nobody asks why there is such a need to onboard people so often, or so quickly.) When your pursuit of mastery is t…
I really wish there were more non-web dev remote coding jobs. Web development is never-ending and super thankless. Plus there seems to be a brand new language popping up every 2 years now. With C I just needed to study the Kernighan-Ritchie book and that was it. I think my quality of life was a lot higher as an embedded dev, web stuff is just too easy to get into in order for companies not to treat you as disposable.
If your career is made to be safe and as similar to everyone else, it is much harder to gain leverage.
You can't trust capital to take care of you.
The red tape is garroting us. My wife's dev environment VMs are 'remediated' at 8pm regardless if she's using them or not - there is no override policy - and the company is singing the success story of saving 40 dollars in licensing. At another corporation, it can take several weeks to learn how to fill out the IAM role and permission boundaries to allow a new app to run - and a governance board has to review it and…
It makes me wonder whether companies should consider hiring more people dedicated to dealing with the red tape to unblock engineers. I suppose managers to a certain extent are the ones doing this work, but in many cases it's not enough, how about a new role that is dedicated to cutting the red tape?
They tend to be people who couldn't cut it as actual engineers, and so they end up in administrative roles, the ones that OP lambasted as writing stories to write stories, and causing more work, because they need things explained to them slowly and with crayons, and that takes more time, because the engineers just want to be left alone meanwhile the PM gets yelled at by customers, and decides to side with the customers and is just one more person yelling at the devs.
Earlier quoted context omitted.
I do the same but Go can't help me with frontend, right? What do you do?
I stay away from all the JS dependency bullshit as much as possible. I use vanilla JS & CSS wherever possible, usually in a Go template. If I have to create a SPA then I use Vue - I've found it's the least complex of the front-end frameworks. I build it using ESBuild from the flat JS files downloaded from the Vue site and stay as far from yarn/npm as possible. I'm trying to work out how to compile Go to WASM and mani…
1. Since WASM doesn't yet expose a feature to share GC with the host, the GC functionality with necessarily be bundled with your outputted code, making your WASM size larger than ideal.
2. All calls from WASM have to go through a JS layer in order to interact with the Web APIs anyway, so now you actually have _two_ GCs to run.
3. The developer experience is going to be poor unless you write a shit ton of wrappers for the existing DOM API.
I say the above not to dissuade you, I find WASM an attractive value proposition and use WASM in all sorts of ways in personal projects. Good luck