Hi guys! My name is Karina, I am a graphic designer from Ukraine. I want to show you my work about gopher) My husband is a golang developer and my little hobby of making him T-shirts with gophers has grown into the fact that I now draw them. Do you like my work?

Every time someone compares Golang to Rust an angel falls, a unicorn dies and a Java developer writes another class.

Please stop doing that.

Dear Java library developers. The javadoc is not an excuse to not write documentation.

Signed,
a very annoyed golang developer

Sooooo this is the thing.

For a stupid fucking project at work we basically have to scrum manage a bunch of individual components on a rather large web app.

We start with the html and css and js bs and we all have to work on different sections of one page at a time. Large blocks right? Ok cool.

Originally I had suggested to build everything inside individual php files and then stack them up with require(). As fucking simple as fucking that. Except that the manager does not have php on her pc. The other two developer don't either. I am the only one that fucks with php OUTSIDE our fucking servers.

Go fucking figure...the lead developer does not fuck with php outside the servers.....man

So, because i know it would be a shitstorm with something as basic as installing i dunno...fucking xampp my manager said that she needs a different solution.

Fuck it...fine...whatever. i know go. So i make a fucking server wich upon being fired you can just code the templates and paste them where they need to go. Docs and everything..a sane folder structure and everything and a fucking pipleline for the assets and everything. I would have thought that shit was good enough but I even added a cmd tool that merges all the fucking html files together into one html file with all the shit included.

All in Golang. It works, its fast and i can just give them the fucking folder with the exe and it will work.

I dunno if this was the best way to do it. But it took me maybe 20 mins to do it and it works.

I would have expected our manager to be impressed but she legit did not gave two fucking shits about the fact that one of her developers is able to create this mini server for static sites shitstain project in 20 minutes.

Man I don't want praise. She thinks that jquery is the best thing in the world so I don't expect much. But shit man.......a better reaction would have been better. She basically went meh ok as long as it works.

I also showed them a demo of a flutter project to replace the shitty ass webview filled school app that they have for android and ios. Shit is native and it looks beautiful. Ask me what she said.

Go on, fucking ask me.

She said tha if it would take me much time to continue on that the she would rather leave it to the third party vendor that currently makes the app.

I told her that such shitty app costs the school 40 fucking thousand dollars a year that I could do in a fucking month, which would also be better since it would raise the salaries of me and the other 2 developers and will more importantly make us more valuable to the school.

Said that she would think about it because we have a lot of projects.

I
Fucking
Hate
It

When someone fucks with my ability to make more money. I hate it fam. And i fucking despise being limited by other people.

Fuck this week.

I am never gonna grow in here. Ever. But it pays the bills so fuck it.

To Golang or not to Golang?

I'm seeking a job change. Should I go for it?

So I’ve asked one hipster js developer what does he think about golang. His answer was:
- it’s the same as nodejs, but difference is that go has pointers
O_o

Ok, so I need some clarity from you good folk, please.

My lead developer is also my main mentor, as I am still very much a junior. He carved out most of his career in PHP, but due to his curious/hands-on personality, he has become proficient with Golang, Docker, Javascript, HTML/CSS.

We have had a number of chats about what I am best focusing on, both personally and related to work, and he makes quite a compelling case for the "learn as many things as possible; this is what makes you truly valuable" school of thought. Trouble is, this is in direct contrast to what I was taught by my previously esteemed mentor, Gordon Zhu from watchandcode.com. "Watch and Code is about the core skills that all great developers possess. These skills are incredibly important but sound boring and forgettable. They’re things like reading code, consistency and style, debugging, refactoring, and test-driven development. If I could distill Watch and Code to one skill, it would be the ability to take any codebase and rip it apart. And the most important component of that ability is being able to read code."

As you can see, Gordon always emphasised language neutrality, mastering the fundamentals, and going deep rather than wide. He has a ruthlessly high barrier of entry for learning new skills, which is basically "learn something when you have no other option but to learn it".

His approach served me well for my deep dive into Javascript, my first language. It is still the one I know the best and enjoy using the most, despite having written programs in PHP, Ruby, Golang and C# since then. I have picked up quite a lot about different build pipelines, development environments and general web development as a result of exposure to these other things, so it isn't a waste of time.

But I am starting to go a bit mad. I focus almost exclusively on quite data intensive UI development with Vue.js in my day job, although there is an expectation I will help with porting an app to .NET Core 3 in a few months. .NET is rather huge from what I have seen so far, and I am seriously craving a sense of focus. My intuition says I am happiest on the front end, and that focusing on becoming a skilled Javascript engineer is where I will get the biggest returns in mastery, pay and also LIFE BALANCE/WELLBEING...

Any thoughts, people? I would be interested to hear peoples experiences regarding depth vs breadth when it comes to the real world.

Hello everyone, looking for some career advice here.

First of let me list my credentials off here. I graduated in 2016 with a BS in Computer Science. While I was working on my degree I worked as an engineering for 3 years in a cell phone repair company. What this entailed was managing/reverse engineering a software solution of one of that companies vendors, writing documentation etc (it started as a summer internship and became a job that I worked full time over Summers and up to 30/week in the school year).

Anyway, the vendor I acted as a point of contact offered me a job before I graduated and I started with them in May 2016 as a junior most Dev. Since then I have have maintained the same job tittle (software developer), however my duties have increased.

Currently I maintain several of our build servers, manage software releases (as in I am the lead developer of this application) for the service that makes 90% of this companies money, and am the subject matter expert for everything regarding smartphone diagnostics. I've literally been entrusted with access to all of the company servers for if something goes wrong. I'm also training our newest developers and being told I'm doing a good job at doing so.

Currently with my job on a day to day basis I'm working with Java, Android, C++, Golang, MongoDB, iOS in Objective C, and Python

(Please note this is a small company of less than 50 people)

Currently I'm only being paid 60k USD and am wondering if I should hold out for a raise or consider looking for a better job? ( Please note I live in the east coast in an area where the cost of living isn't absurd).
Because this job was practically handed to me I don't know what to expect and feel imposter syndrome as I think I deserve better pay but think I don't have enough years experience. All advice is welcome

So, after studying software development and games programming, I ended up working as a Salesforce developer. Been doing it for over a year now, but it's still not something I'm passionate about.

I got invited to an interview for a different job. Games industry related, using golang to do backend work.

Switching from Salesforce to Engine. From frontend to backend. I have faith that I can do it, the question I'm struggling with is... Should I?

I have no idea what the pros and cons are, junior dev In both roles, pay is about the same but for the fields themselves, is being a backend dev better than frontend? Is golang a desired language? Do I have career security by learning these things?

Or should I stay where I am now, give up enjoying my job in favour of something I class incredibly easy?

Any advice would be greatly appreciated.

Nothing like constantly having to spend 3-5 days of spin up on trying to help another team with their microservices because they have such a severe lack of documentation that I can't just follow a readme to get their projects running. Instead, I have to bug one of their developers to help me get it up and running (because they use non-standard project setups and dependency management), delaying things even more. No matter how much I scream that we need documentation no one makes it a priority.
Did I mention these are microservices written in Golang and I'm a front end developer? And I'm being made to work on back end tasks because we have a crazy high attrition rate and they won't back fill the back end positions.

Is Manjaro good for web and mobile developer? Currently I'm using Kubuntu, but I'm thinking about switching to Manjaro with i3. I'm using Andoroid Studion, Intellij, VS Code, GoLang and Java. I might replace VS Code with Vim later down the line.

I am doing Golang training. Can someone share some tips to boost my skills more quickly?

What can I build on a weekend which I can add in my portfolio and also learn golang. I am a web developer with sound knowledge of react, vue, node, django. I am learning golang.

PS - please suggest the project even if the project is not is golang. I want to improve my current skills also.

what are the basics I should know about "data streaming" for working on video streaming companies as a future senior backend Golang developer?

I got my first developer job three years ago. I’ve always had a great eye for detail, and getting things done while following best practices. I learned that a few years ago from typography, which I think is a fascinating subject, which has a lot of shared ideas with software development.

In my first job, I immediately took a lot more responsibility than what I was assigned to. This job was as a React Developer, but I quickly got into backend development and set up kubernetes clusters, CI/CD.

Looking back, this was to me quite an achievement, considering I had never done anything even remotely close to it.

I did however, work my ass off. 18 hours work days without telling my boss, so only getting paid for 8. Plus I worked weekends.

I did love it. After a while, I got promotes to Senior Developer, and got responsibility for everything technical. I tried asking for help, but everybody else was either a student, or working purely front-end or app-development. Meanwhile, I was Devops, API-design, backend, Ci/CD, handling remote installations (all our customers are Airgapped), customer support, front-end and occasionally app-development when the app-developers could not handle their shit. Basically, I was the goto-guy for every problem, every feature, every fix. I don’t say this to brag.

I recently quit my job, started working as a consultant, because I almost doubled my pay. However the new job is boring as shit. I’m now an overpaid React Developer. And I really hate React. Not because it is shit, but simply because it is boring.

I’m thinking of going back to my old job. It was a lot of work, but it was really interesting. However, after I quit, they have changed their whole stack. No more Golang, Containers, Kubernetes, webRTC and other fun new technologies. Now, it is just plain, PHP without any dependecies. It is both boring, and idiotic. So I’m thinking of just quitting. Either doing some personal projects like game-development. I dont know.

panic() in golang. Aptly describes the state of every developer when code explodes.