Just called Asus for a problem with my router, went to send them my systemlog.txt for analysis

"Oh we don't have an email you can send that to"

Me: "(me calling bullshit) let me talk to the tech team.."

*Get transferred*

"Hello this is the supervisor"

Me: "fml"

"Ya we don't have an email you can send that to, but we can use a different departments verification services to get a file from you, has to be a picture though"

Me: "What? I got a .txt file here, I just want to get it to you, does it really have to be a picture?"

"Has to be a picture or a PDF, we can't take txt files"

Me: "fkin.. srsly? Fine"

I can't believe Asus's system srsly. I think it's for virus protection, but viruses can be embedded in both picture formats and PDF, but not in txt. So wtf is going on lol

It's maddening how few people working with the internet don't know anything about the protocols that make it work. Web work, especially, I spend far too much time explaining how status codes, methods, content-types etc work, how they're used and basic fundamental shit about how to do the job of someone building internet applications and consumable services.

The following has played out at more than one company:

App: "Hey api, I need some data"
API: "200 (plain text response message, content-type application/json, 'internal server error')"
App: *blows the fuck up

*msg service team*

Me: "Getting a 200 with a plaintext response containing an internal server exception"
Team: "Yeah, what's the problem?"
Me: "...200 means success, the message suggests 500. Either way, it should be one of the error codes. We use the status code to determine how the application processes the request. What do the logs say?"
Team: "Log says that the user wasn't signed in. Can you not read the response message and make a decision?"
Me: "That status for that is 401. And no, that would require us to know every message you have verbatim, in this case, it doesn't even deserialize and causes an exception because it's not actually json."
Team: "Why 401?"
Me: "It's the code for unauthorized. It tells us to redirect the user to the sign in experience"
Team: "We can't authorize until the user signs in"
Me: *angermatopoeia* "Just, trust me. If a user isn't logged in, return 401, if they don't have permissions you send 403"
Team: *googles SO* "Internet says we can use 500"
Me: "That's server error, it says something blew up with an unhandled exception on your end. You've already established it was an auth issue in the logs."
Team: "But there's an error, why doesn't that work?"
Me: "It's generic. It's like me messaging you and saying, "your service is broken". It doesn't give us any insight into what went wrong or *how* we should attempt to troubleshoot the error or where it occurred. You already know what's wrong, so just tell me with the status code."
Team: "But it's ok, right, 500? It's an error?"
Me: "It puts all the troubleshooting responsibility on your consumer to investigate the error at every level. A precise error code could potentially prevent us from bothering you at all."
Team: "How so?"
Me: "Send 401, we know that it's a login issue, 403, something is wrong with the request, 404 we're hitting an endpoint that doesn't exist, 503 we know that the service can't be reached for some reason, 504 means the service exists, but timed out at the gateway or service. In the worst case we're able to triage who needs to be involved to solve the issue, make sense?"
Team: "Oh, sounds cool, so how do we do that?"
Me: "That's down to your technology, your team will need to implement it. Most frameworks handle it out of the box for many cases."
Team: "Ah, ok. We'll send a 500, that sound easiest"
Me: *..l.. -__- ..l..* "Ok, let's get into the other 5 problems with this situation..."

Moral of the story: If this is you: learn the protocol you're utilizing, provide metadata, and stop treating your customers like shit.

I have been a team leader for about 2-3 years. My boss announced that the company will be accepting WordPress Development services and it will be fucking assigned to me and I will be given a new team. Don't get me wrong but WordPress has been my bread & butter when I'm still a college student for I have to fund my own tuition and apply for free-lance and part time jobs. But those days have been a pain in the ass and I don't want to experience those days anymore. Well, I will definitely going to look for a new job. Bye

Our Service Oriented Architecture team is writing very next-level things, such as JSON services that pass data like this:

<JSON>
<Data>
...
</Data>
</JSON>

the fuck kind of manager are you that you tell your leads not to fucking answer their damn phones when services need restoring????? If your fucking team member can do his damn job like a grown ass adult, but sees that you (his lead) made a change and has questions, your ass better answer the phone, or i will rocket launch it up your ass, straight into your brain so it's the newest, latest, fucking hippest trend and hooked into your system so you answer every fucking call hands-free. Even when fucking "Windows Tech Support" calls you every 30 minutes because your keep expired.

There are people counting on you, worthless fuckwipe. Get. The. Fuck. Over. Yourself. And do your fucking job.

Edit: phone tried to censor me

Got laid off last week with the rest of the dev team, except one full stack Laravel dev. Investors money drying up, and the clowns can't figure out how to sell what we have.

I was all of devops and cloud infra. Had a nice k8s cluster, all terraform and gitops. The only dev left is being asked to migrate all of it to Laravel forge. 7 ML microservices, monolith web app, hashicorp vault, perfect, mlflow, kubecost, rancher, some other random services.

The genius asked the dev to move everything to a single aws account and deploy publicly with Laravel forge... While adding more features. The VP of engineering just finished his 3 year plan for the 5 months of runway they have left.

I already have another job offer for 50k more a year. I'm out of here!

A personal memo to all developers on devRant:

* Assume every external line of code, (including every service you consume) is an unreliable crock of flaming shit. These services can and will fail in the most glorious ways. Write your code to be resilient, and ASSUME FAILURE of dependencies. Even if it's your own team writing the other service.

Heard in a meeting today: "Your team's service outage is going to cause my service to corrupt the database!"

Response I wanted to give: "No, you asshat, my service outage is a normal part of living with microservices. Your app should have been smart enough to recognize the failure."

There is a company providing a very speciffic service. And it has a core application for that svc, supported by a core app team.
That company also has other services, which are derivations of the core one. So every svc depends on core.

Now that we're clear on that... I was working in a team of one of the subservices. We very strongly depended on core. In fact, our svc was useless if integration w/ core broke down.

The core team had an annoying habbit. They refused to version their webservices and they LOVED to push api updates w/o any warnings. Our prod, test, other envs used to fail bcz of core api changes quite often. Mgmt, IT head was aware of the problem and customers' complaints as well.

So as a result, once core api changes we're all in a panic mode: all prior priorities are lowered and revival of prod is to be our main focus. Core api is not docummented, the changes are not clear, so we have to reverse engineer the shit out of it. We manage to patch our prod up w/ hotfixes, but now we have tech debt. While working on the debt, core api changed again, in test env. Mgmt pushes debt back and reallocates us to hotfix test. Hotfix is 80% done when another core api breaks. Now mgmt asks us to drop wtv we're working on and fix that new break. By the time we're to deploy the hotfix, another api breaks in another env. The mgmt..... You get the picture :)

2 years go by, nothing has changed so far.

I'm a backend (Java, Kotlin) developer and I mainly design & develop services and Android apps which consume these services.

My team in my current organization (I've been working here since past 2 years) just got merged with another team.

And now the new boss wants me to fix some fuck ups in their project which is written in C#, with some WCF and other stuff.

As this stuff is completely new for me, I asked for some time to get familiar with the environment. But the answer was a big NO.

As a result, "I've started looking out for a new job"
😡😠

Fuckin management screws up everything!

> worst coding procrastination story

worst and best at the same time:

If you wait long enough things might resolve themselves.

My team inherited an ancient site. Hosted on an old host that the org wanted to kill, using an old log service the org wanted to kill.

A ticket was written in 2021 to migrate that site's hosting and logging to the new services our org started using.

My team kept avoiding it since it was a cheap unimportant site.

in 2023 we were about to finally take action - then we hear "Turns out the new hosting platform and logging platform are way too expensive - I know all of you have migrated to these new services but you gotta revert and go back the old ones til we figure this out"

We didn't have to do squat.

Problem solved by procrastinating ✅

Dear everyone who doesn't write JS and has some hand-wringing concern about its lack of static typing, lack of threading, or its suitability for large back-end services:

It's fine, we've got this. You go back to discussing contravariance or whatever it is you do.

Signed,
Team JS

Team of developers suggest one of our legacy services is a nightmare to maintain, terrible to develop on top of and is fundamentally wrong in terms of data and application structure.

They are 100% correct and I fully endorse their request to redevelop it.

I'm less enthusiastic that their new version is much worse than the original...

I wish I can fucking clone myself.

We have been providing digital marketing services for like 5 years without having a proper QA team. Well because we cannot afford to hire one. Technically I am supposed to check and control the quality of our operation team. But I have been juggling so many balls and couldn't do that properly.

So this year we decided that we have to seriously take care of that. But we are providing all kinds of services and creating a QA team for all those services is gonna be costly. We wanna solve it, but also doesn't wanna hang ourselves with another rope. So we have decided to just found a QA team with leaders from various departments mainly Sales and Customer Services. They are the ones who have talked with clients. So they should be able to judge the quality of the services our operation made.

It is a fucking nightmare. It is like we have doubled the amount of clients. And that extra half of those newly popped up clients are sitting in our office.

CTO: We'll use epochs for any time related fields in our services.

After service integration...

Dev from producer team: Hey the time field is showing up as 1970 and not null in your table. That seems to be a bug.

Me: Code looks fine. We are converting epochs to timestamps here. Null is taken care by the library function itself.

The same dev: Actually we are sending zero instead of null values in that time field. But we'd want the end table to treat that as null.

Me: Why can't you send null then?

The dev: Actually avro doesn't support nulls. Hence the zero.

Me: WTF??????

Manager to me: Actually you need to convert them as null. Anyways, this is not a blocker and we can live with it for now.

END OF RANT

Why can't they fucking send it as null? And when I asked about the details, that particular event type doesn't require that field. Still the manager insists on sending that field for it.

!rant

I promised myself I wouldnt cry but ... nah I wont.

So I got the job and today was my first day of work, well not precisely work but introduction to the cultuure of the place, signing tons of paper, I probably sold my soul but who cares?, and I met my team, so far everything seems cool, except tthat I will be using windows and wont be able to use any streaming websites or services (yt, spotify, deezer, etc) yes I know, there are ways around it, but come on guys I dont wanna start screwing my first week of work, anyway everything is cool, even the food is tasty there iis only one thing left, my workspace Im an extremely bad decorator so I need ur help, (and yes I know i have to have a duck and a devrant stressball) but apart from that guys and gals, any ideas? So far ive thought about a debugging body, a lava lamp and an extra monitor.

Another unrealistic deadline from our non-software developer PM.
He agreed to client upon delivery of a complete system consisting of 4 micro-services in Node and 4 front-end Angular application integrated with each micro-service accordingly.

Project Delivery date is December 31. I have told him It is impossible to deliver complete solution on December 31.
Now he wants me & my team to come to office even on weekends.
What an idiot !

dev, ~boring

This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.

I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:

1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by

I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.

At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:

"Hierarchy and structure should arise from an understanding of a problem domain"

As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.

In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.

Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).

I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:

1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth

Given that, I can devise a heuristic, organic framework for growing a team:

- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it

Last thing isn't derived from the train of thought, just things I feel are true:

- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy

/rant

How common is it for development job applicants to lie about their skillsets and experience?

Had an applicant come interview for a senior software engineer role, has been in the same company for 8 years and his resume is sprayed with almost every tech speciality and language there is, claims to be proficient in 8+ languages, done AWS server migrations, built CI/CD pipelines from scratch, written CloudFormation scripts, built microservices, worked with AWS services and serverless platforms, has managed a team, does salary and performance reviews

My gut feeling is when someone claims to have knowledge and experience across multiple specialities, they’re skills in any of those domains are only skin deep

Conversation yesterday (senior dev and the mgr)..

SeniorDev: "Yea, I told Ken when using the service, pass the JSON string and serialize to their object. JSON eliminates the data contract mismatch errors they keep running into."
Mgr: "That sounds really familiar. Didn't we do this before?"
SeniorDev: "Hmmm...no. I doubt anyone has done this before."
Me: "Yea, our business tier processor handled transactions via XML. It allowed the client and server to process business objects regardless of platform. Partners using Perl,
clients using Delphi, website using .aspx, and our SQLServer broker even used it."
Mgr: "Oh yea...why did we stop using it?"
Me: "WCF. Remember, the new dev manager at the time and his team broke up the business processor into individual WCF services."
Mgr: "Boy, that was a crap fest. We're still fighting bugs from the mobile devices. Can't wait until we migrate everything to REST."
SeniorDev: "Yea, that was such a -bleep-ing joke."
Me: "You were on Jake's team at the time. You were the primary developer in the re-write process saying passing strings around wasn't the way true object-oriented developers write code.
So it's OK now because the string is in JSON format or because using a JSON string your idea?"

SeniorDev turns around in his desk and puts his headphones back on.

That's right you lying SOB...I remember exactly the level of personal attacks you spewed on me and other developers behind our backs for using XML as the message format.

Keep your fat ass in your seat and shut the hell up.

We had a school project where we where supposed to implement a software with a heavy client in C# and web services for it in C#, but the web services HAD TO COMMUNICATE WITH SMTP AND IMAP. And do that in 8 days.

We were 6 in the team. 4 had no idea what a web service is, and I and the designated project lead were the only ones knowing what to do. The lead had paperwork to do for the project, so I had to do everything but the UI alone. So 1 guy did the UI, 3 were... Playing Minecraft... The lead was doing paperwork and ranting about how noisy idiots these guys were... And I was sick as hell and could not eat anything, I was vomiting all day in between which moment I managed to make half of the functionalities of the project, despite having to go to the hospital and have to continue working despite the medical request not to work.

So the day before the presentation I had half of the functionalities done and I had to explain them yet another time what web services are so they can answer the questions and cover for themselves.

On the day of the presentation it went kinda fine. It was not finished but it worked like asked.

We were asked for peer evaluation and I gave A to the lead and the UI guy and B to the 3 other lazy asses.

Shortly after I am called by the tutor in the office : "What happened on this project? Were you not working at all? Apart for the lead who gave you an A, every one gave you a D (lowest grade). I demand for explanations"

I said never mind and got back to studying. I got a B, all the rest of the group an A.

I just found out last Friday that my team collegues (all of them are team leads) are suffering from depression or the so called burn out syndrom. I guess it's my boss' fault. He never gives clear jobs, changes his mind from day to day, we have to manage unclear responsibilities and the baddest thing is that we think that our boss is too stressed out himself.

Do you have any advice for me how we as team could solve that besides changing employer? One thing to mention is, that my boss likes to hear himself talking. That makes it even harder for a guy like myself who is more or less introverted to come up with good arguments which are not overheard or overtalked immediately. What are your feedback strategies to your own boss, how do you bring such stuff on the table?

I fear that when nothing happens, my company will suffer very hard when the whole product engineering departement will fall apart (¼ of the whole company and is responsible for engineering and maintaining of internal services and managed services for our customers).

Well at least it was worth writing about it, maybe my subconcious mind will come up with a brilliant idea itself in the near future in some asynchronous way. But you might be the one with that valuable input, then don't hesitate to share, it will be welcome.

I explained last week in great detail to a new team member of a dev team (yeah hire or fire part 2) why it is an extremely bad idea to do proactive error handling somewhere down in the stack...

Example
Controller -> Business/Application Logic -> Infrastructure Layer

(shortened)

Now in the infrastructure layer we have a cache that caches an http rest call to another service.

One should not implement retry or some other proactive error handling down in the cache / infra stack, instead propagate the error to the upper layer(s) like application / business logic.
Let them decide what's the course of action, so ...
1) no error is swallowed
2) no unintended side effects like latency spikes / hickups due to retries or similar techniques happens
3) one can actually understand what the services do - behaviour should either be configured explicitly or passed down as a programmed choice from the upper layer... Not randomly implemented in some services.

The explanation was long and I thought ... Well let's call the recruit like the Gremlin he is... Gizmo got the message.

Today Gizmo presented a new solution.

The solution was to log and swallow all exceptions and just return null everywhere.

Yay... Gizmo. You won the Oscar for bad choices TM.

Thx for not asking whether that brain fart made any sense and wasting 5 days with implementing the worst of it all.

better late than never.
So I just decided to go with Gitlab after being a Microsoft Team Services user.
To do next on my list:
Move away from .Net for backend services, any suggestions? I use dotnet core due to being able to easily finish what I want and with less code to write. Tried Springboot for Java but not a Java fan, might checkout kotlin though

Follow up on a previous rant:

I visited a customer to talk about the reporting discrepancy between two applications.

It turns out the applications were custom built by outsourced developers from Russia, that communicate with each other through a byzantine (and completely undocumented) series of web services, excel import/export tasks, and a customized SSRS environment.

These are spread across at least half a dozen servers, some on-premise and some cloud based, there are at least 3 SQL servers (2 running 2005, one running 2000), a 10 year old local install of TFS (which no one knows a username/password for), and who-knows-what-else.

They laid off their entire IT team years ago, and they have no backups.

I'm not certain anyone there even understands what the software is supposed to be doing beyond the most general terms.

No one knows if they even have source code.

Biggest case of "nope!" I've encountered in more than 20 years of IT experience.

Providing hosting and site management services to clients was the best decision Ive ever made. Now they don't get access to their websites until I get paid.

Getting a managed dedicated server was an even better decision. Allowing me to focus on the development while a professional team takes care of my clients security.

I am working with a team that's producing tons of new services..
And me being a fresher, reading new designs every other day with God knows complex implementations and business requirements and attending design review meetings(where I can barely understand anything)
having a great learning curve..
Hopefully, I survive this period and cope up with the inputs...
Note: Just don't ask what's my contribution.. I am gearing up for the D-Day to make my impact(not a negative one).. 😎

Yesterday, microsoft showed me once again, what it means to "obey".

I tried to install Microsoft SQL Server 2012 on a virtual machine with OS Windows7.
The installation-center asked me to choose an installation-folder for SQL-Server.
No matter what, for any folder i had chosen for the installation, the setup replied with the errormessage "The installation-folder is invalid"

So i considered asking our platform-services team, whether they gave me administrative rights for the vm.
They did. I had full access to the components of my vm.

After a few days i finally recognized, that i had picked a wrong iso for the installation of sql server.

Instead of sql server 2012 + Service Pack 3, i picked sql server 2012 ServicePack 3.

So after all, Microsoft tried to tell me by showing the message "The installation-folder is invalid", that the setup weren't able to find an installation of Microsoft SQL Server 2012.

God damned!!1!

TL;DR Calendar services sucks.

Imagine yourself as startup. You don't want to spend fortune on paying $5 per user per month for Google Services. Also you don't want to pay that to Microsoft for O365. You want to run it itself because you already have droplet running with your other services (ERP for example. Funny story too btw.) Ok, decision has been made, let install something.

I have pretty good experience with OwnCloud from past as Cloud file sharing service. Calendar is not bad for single user purpose (understand it as personal calendar, no invitations to others, sharing is maximum I tried) What can possibly go wrong when I deploy that and use its Calendar?

Well, lot. OwnCloud itself runs well (no rant here) but Calendar is such pain in ass. Trouble is with CalDav under hood and its fragmented standards. So, you want to send invitation to your team for recurrent meeting. Nothing weird. It sends as one invitation to each one, good. Now you realize you have a conflict, so you need to change time of one occurence. Move it, send update. And here comes shitstorm. It is not able to bisect one occurence from series. So it splits it to separate events and send invitation for every single one. 30 INVITATIONS IN 2 SECONDS! Holy sh*t! You want to revert that. Nope, won't do. So you accept your destiny and manually erase every single one with memo in head about planning recurring events.

Another funny issue is when SwiftMailer library (which is responsive for sending e-mails from OwnCloud) goes to spamming mayhem. It is pretty easy to do. When e-mail doesn't comply to RFC, it is rejected, right? So if because of some error CalDav client passes non-compliant e-mail (space as last character is non-compliant btw) and SwiftMailer tries to send it to multiple recepients (one of them is broken, rest is fine), it results in repetitive sending same invitation over and over in 30 minute interval. Sweet.

So now I am sitting in front of browser, looking for alternatives. Not much to choose from. I guess I'll try SOGO. It looks nice. For now.

So I was told to look into a new project management tool to replace our home grown one that must be free, decided on visual studio team services because we all have msdn so it's free. We just got everything migrated and we've been using it very successfully for the past few months and it's honestly made task management so much easier.
Get back from vacation and my company just spent $100k on sales force agile accelerator... 😑 I don't understand how upper management works

* Developing a new "My pages" NBV offer/order solution for customer
_Thursday
Customer: Are we ready for testing?
Me: Almost, we need to receive the SSL cert and then do a full test run to see if your sales services get the orders correctly. At this point, all orders made via this flow are tagged so they will not be sent to the Sales services. We also still need to implement the tracking to see who has been exposed to what in My Pages.
Customer: Ok, great!

_Friday
Customer: My web team needs these customers to have fake offers on them, to validate the layout and content
Me: Ok, my colleague can fix this by Tuesday - he has all the other things with higher prio from you to complete first
Customer: Ok! Good!

_Sunday
Me: Good news, got the SSL cert installed and have verified the flow from my side. Now you need to verify the full flow from your side.
Customer: Ok! Great! Will do.

_Monday
*quiet*

_Tuesday
Customer: Can you see how things are going? Any good news?
Me: ???
*looks into the system*
WTF!?!
- Have you set this into production on your side? We are not finished with the implementation on our side!
Customer: Oh, sorry - well, it looked fine when we tested with the test links you sent (3 weeks ago)
Me: But did you make a complete test run, and make sure that Sales services got the order?
Customer: Oh, no they didn't receive anything - but we thought that was just because of it being a test link
Me: Seriously - you didn't read what i wrote last Thursday?
Customer: ...
Me: Ok, so what happens if something goes wrong - who get's blamed?
Customer: ...
Me: FML!!!

Today I talked to a cousin who works in Tata Consultancy Services (TCS) and he told me precisely why companies like Infosys, TCS and Wipro are moving towards ending WFH and mandating working from office.

He told me that post-COVID hires are treating these software jobs so casually, that they don't ask for leaves. They decide, on their own, when they want to take leave(s) without telling their team members.

They don't pick up phone calls when someone from upper management tries to reach out and they magically show up 3-4 days later. They don't value deadlines.

He told me that these companies do see the benefit of letting people work from home, but the new generation hires are creating a joke out of these positions and are taking blatant advantage of the situation. So they are forced to mandate working from office.

At my previous company, we used tools from all over the place. We switched between tools at will. Sometimes, some team would decide to use some tool while the rest of the company would use something else. The worst part was that there was no Single-Sign-On (SSO) either. Everyone would need to have an account on all of these said tools. It was chaos.

I realized that being integrated into one environment (even though would have the cost of a vendor-lock-in) was the best option to have because in that case, we wouldn't have to deal with operational hurdles like having integration from one tool to another. They would just come baked-in with the whole environment. That's how GSuite (formerly Google Apps for Work), Atlassian and other players succeeded - they gave a complete suite of services / software that integrated well with each other. You could jump back and forth between services without having to bother about integration with other tools. They'd all be there wherever you wanted them to be. Even cloud providers so that opportunity and built on it - Amazon Web Services (AWS), Google Cloud Platform (GCP), Kubernetes (in itself).

Another example is a company that used Jira, Confluence and Hipchat but for some dumb reason used Gerrit for their code review / hosting. Eventually, they realized that managing the integration with the Atlassian tools was far more expensive than getting bitbucket and migrating completely into the Atlassian environment.

It's always the integration that matters. Everything else is secondary.

Two (2) senior developers and one (1) senior tester left our team and I am left with two (2) Java legacy applications that are hard to maintain. Here is a list of things I hate about these old webapps (let's call them app A and B):

1. App A depends on 80% web services. If one web service for a product or warehouse goes down, work flow is impeded while prod support team checks with the core services team for repair

2. App B is a maven project with multiple modules dependent on libraries that are dependent on company's internal libraries. So if we want to upgrade to OpenJdk 9 and up, the project will definitely produce a lot of errors due to deprecated/unsupported codes

3. App A is dependent on Tibco and I have no experience on that

4. App B's continuous integration build tool is Jenkins and the jobs that build it has a shell script that wasn't updated during the tech upgrade enhancement. The previous developer who did the knowledge transfer to me didn't tell me about this (it should be considered a defect on her part but she already resigned)

5. App A when loaded in eclipse IDE is a pain to work with since it is only allowed to build a war file using ant. I have to lookup in quick search instead of calling shortcuts (call hierarchy) because the project wasn't compiled via eclipse.

6. It's impossible to debug app A because of #5

7. Both applications have high priority and complex enhancements and I have no other teammates to help me

8. You never know what else can go wrong anytime

I'm in a team of 3 in a small to medium sized company (over 50 engineers). We all work as full stack engineers.. but I think the definition of full stack here is getting super bloated. Let me give u an example. My team hold a few production apps, and we just launched a new one. The whole team (the 3 of us) are fully responsible on it from planning, design, database model, api, frontend (a react page spa), an extra client. Ok, so all this seems normal to a full stack dev.

Now, we also handle provisioning infra in aws using terraform, doing deployments, building a CI/CD pipeline using jenkins, monitoring, writing tests, building an analytics dashboard.

Recently our tech writer also left, so now we are also handling writing feature releases.

Few days ago, we also had a meeting where they sort of discussed that the maintenance of the engineering shared services, e.g. jenkins servers, (and about 2-3 other services) will now be split between teams in a shared board, previously this was handled only be team leads, but now they want to delegate it down.

And ofcourse not to mention supporting the app itself and updating bug tickets with findings.

I feel like my daily responsiblities are becoming the job responsibilities of at least 3 jobs.

Is this what full stack engineering looks like in your company? Do u handle everything from app design, building, cloud, ops, analytics etc..

This is odd for me to say this.. but Microsoft is kind of impressing me right now. I haven’t had many issues, and kind of testing out visual studio team services and liking what I’m seeing. Started out with VS code at work and here I am using it on small projects at home and seeing what else MS has to offer. Granted I’m still using my linux boot more but it’s been 8 days since my Win10 partition hasn’t crashed and that’s 8 days longer than when I first got this computer a few months ago when it was crashing hourly even after a fresh install and updates.

I really like my position as the head of my department. But I am most definitely hitting walls(and in some way breaking them) concerning the way the CTO(my direct boss) deals with a lot of the things that his management team wants to do.

For example, the previous manager could only do so much in terms of directing a software team since she did not have a formal background in computer science or engineering, thus the developers that she had would tell her the different deals with many things and she would have to take their word for it. Nothing necessarily bad with this, but it just meant that a lot of things could have gone smoother had she the knowledge to fix said items. Whenever she would try to use resources(dev time or such) the CTO will resort to the all powerful manthra of "if it ain't broke don't fix it!".

but it was about more than fixing things that were breaking, our internal services and admin boards were built using all of the WRONG proper development practices, it feels as if they took the book of best practices.....and said fuck it and did whatever the fuck they wanted. It is the worst PHP/Java/JS code I have ever seen in my entire life and the reason why even though I do not concur with it I will always understand the dislike from other developers. Our services look like something that came out from the 90s, no style, no engineering concepts in place, no versioning no testing NADA zip(these are all web based services)

One in particular, it was an admin board used internally to let students evaluate their professors, the entire app is shit, and it was broken, for some UNGODLY reason, the original dev decided to use some weird external libraries he got from some blog somewhere and as such something that would take about 5 or 6 files is now a mess with over 200 php/js files all over the fucking place. The CTO insisted on fixing them, they were all broken, and I continuously told him that redesigning the application would be faster.

Mofo fought me on it, and in the end I did what I wanted and rebuilt the app.

It took me one afternoon. One fucking afternoon, over possibly 2 weeks of fixing it.

See, I am not one to just do whatever he pleases, but I am firm in my belief that if I know a better way I will do it and save precious time. The dude had to agree with me on this and promised to consider this shit on other items that will undoubtedly come up. He was lying out of his ass but oh well..........

W

!rant

In my team, I am not allowed to use ANY comments except for the really lengthy classes in the backend.
Thus, the code of the whole project (a complex webapp, consisting of 20-something Django projects and various services) is basically undocumented.
The slogan sounds "good code doesn't need commenting".
Seriously, fuck this and all of the times I scratched my head wondering "what the fuck is this spaghetti about".

Have any of you encountered something like this? Usually people don't want to comment, I would do it gladly but can't even make a small inline about what complex method is exactly doing :P

So I get these spam messages all the time, but correct me if my math is wrong. 15 years of combined experience / 155 employees = 0.096 years experience per employee which is about a month experience each assuming everyone has the same amount of experience. (15 / 155) * 12 = 1.152 (rounded of course). Now I know having the least amount of experience isn’t always a measure of quality since I have about the least in my team yet have been teaching some of the more experienced coworkers of mine some things but if I am trying to sell services I would probably pump up the collective years of experience a bit. Especially if there’s 155 of you.

So I'm getting brought into a team for our backend services of our administration application, and they're explicitly using Flask (Python library) for their exposed API in their application and data tiers.

As I'm familiarizing myself with their code, utilities, and dependencies, I notice they're stacking 7-8 decorators on their routes from their in-house utility module.. After further investigation, I realized half of them were entirely unnecessary, and they were proofing payload responses three times for the same JSON format.

The fact that we're using Python instead of Node or GoLang for our REST services is pain enough, but these god damn in house utilities are killing me.

My ideal dev job, would be a job I can show compassion towards. A team I can be proud of and learn from. And a vibrant workspace with likeminded individuals who just want to improve themselves even if they feel their at their pinnacle.

My current office tries to make use of new technologies, we've embedded docker, vagrant, a few ci systems on an in need basis per team, and a lot of other tools.

My only real qualms are they feel indifferent towards new languages and eco systems ( Node.js, GoLang, etc ). Our web team is still using angular.js 1.x, bower, refuses to look into webpack or a new framework for our front end which is currently being bogged down by angulars dirty checking.

Our automated quality assurance team is forced to use Python for end to end testing, I've written an extensive package to make their lives easier including an entire JavaScript interface for dispatching events and properly interacting with custom DOMs outside of the scope of the official selenium bindings.

Our RESTful services are all using flask and Python, which become increasingly slow with our increase in services. I've pushed for the use of Node or GoLang with a GraphQL interface but I'm shot down consistently by our principle engineers who believe everything and anything must be written in Python.

I could go on, but tldr; I'm 21 and I have a ton of aspirations for web development. I'd like to believe I'm well rounded for my age, especially without any formal education. I'd love to be surrounded by individuals who want the same, to learn and architect the greatest platforms and services possible.

Just migrated to Gitlab from Microsoft Team Services

Just thought it is better to have gitlab online and gitlab locally so I can use same configuration on both

FUCK you "WP iThemes Security Pro".

First of all, your FUCKing services isn't really secure, more like security by obscurity.
Don't get me started on how you probably don't have a dedicated team of security experts.
But oh well, the customer insisted I must install you, despite my advise.

Second of all, Don't FUCKing send me emails regarding "Scheduled malware scan failed" without it containing the FUCKing error message, not some generic "http_request_failed" error, why did it FUCKing fail?

Last but not least: Don't FUCKing clutter is with with your giant ass logo that takes up half my screen or FUCKing spam such as your upcoming events, newly published books/articles, incorrect "documentation"

Cybergoattechie ETH, USDC Recovery Firm.

It was never an easy ride to recovering my lost investment funds with the help of THECYBERGOAT RECOVERY FIRM. I lost my hard earned funds $600,000 worth of crypto currency when I invested with a binary option site. A broker I met on Instagram last year deceived and lured me into investing with their crypto company. It wasn’t the right decision by me trusting a total stranger with my hard earned funds which really hunted me. Without the recovery services of thecybergoat(@)techie. com, I could have been out on the streets since I could barely take care of the kids let alone paying the rents which were almost due to expire. thecybergoat professionals took control of my case after I had reached out to them which turned around my story. I was in awe the day when thecybergoat sent me an email requesting I send them my wallet that my lost investment funds have been " SUCCESSFULLY RETRIEVED " and on sending my wallet I received back most of my funds which I thought I had lost forever. about $430,000 was recouped. I never thought it would all end up in glory which is why I urge any victim of scam that there is refuge in thecybergoat team with their mind blowing and efficient recovery services. They were equipped with the necessary tools for a successful retrieval pushing themselves beyond their limits to attain remarkable results for their clients. Well, ask me about a recovery firm which is trustworthy and I tell you thecybergoat can be trusted with the retrieval of your lost investment funds. Don’t let doubts stop you from making the right decision and choosing the right and trustworthy recovery firm to handle your case, with the services of thecybergoat recovery firm, you can be sure of a successful retrieval of your lost investment funds.

Given an opportunity to develop an application for R&D. What do we do as a team? Let build it exactly the same way our current stack is built. (This app won't actually be used for anything useful, just an exercise for a fun R&D task)

It still amazes me with the number of developers that literally have the mindset, let's just do what we know & don't want to learn anything new.

Let's showcase new technologies? No. Let's create a serverless application? No. Let's create some microservices? No. Let's wrap the application in a Docker container so we can easily spin it up? No. Let's have multiple services that sit behind an API gateway? No. Let's for fucks sake at try a different design pattern? Why would we do that? Can we do anything differently? No.

No innovation, nothing - it just blows my mind. Everyone seems to think that the way the stack is built is how every application is. Sorry but a huge monolithic application that can't scale isn't how the other half live...

I don't know why the lack of wanting to try something new bothers be so much, but it does.

Had a real opportunity to showcase some cool tech, design patterns, new services in the cloud. Show not only other devs but upper management that there are alternative ways to develop. It's not like anything that I put together was "new or shiny" - I just wanted to do anything... Anything that isn't how currently do things.

Full disclosure, I'm not a great Dev - I'm pretty dam average but I'm always willing to try new techniques or approaches.

The service hooks at Visual Studio Team Service are a mess. A new subscription for every single event. Really?
Is it that hard to add an "everything" field? Instead I can now add 25 events one by one - for every project.

The first dev project, like real dev project, I participated in was a school one and it was double.
The class was meant to make us learn about the software's life cycle, so the teacher wanted us to develop a simple, yet complicated, thing: a Web platform to help tutors send/refer students to the university services (psychologist, nutriologist, etc) and to keep track of them visits.
We all agreed on it being easy.
Boy were we so wrong.
I was appointed as dev leader as well as some others (I was the programming leader, the other ones were the DB guy and the security guy) and as such I was in charge of the technology used (well, now we all know that the client is the one in charge of that as well as the designer) and I chose Django because we had some experience with it. We used it for the two projects the teacher asked us to do (the second one was to find a little shop and develop something for it, obviously with the permission and all that), but in the second one I decided to use React on top of Djangl, which ended being a really good combination tho.
So, in the first project, the other ones (all the classroom) started to discuss and decided to use some other stuff like unnecessary carousel for images, unnecessary functions, they created mock ups for stuff that was never there to begin with, etc. It was really awful, we had meetings with the client (the teacher) with updates on the project, and in not a single one he was satisfied with the results. But still, we continued with the path the majority chose and it was the worst: deadlines were not met, team members just vanished until the end of the semester, one guy broke his leg (and was a dev leader) and never said a word not did anything about the project. At the end, we presented literal garbage, the UI was awful, its colors were so ugly because we had to use the university official colors, the functionality was not there, there literally was a calendar to make appointments for the services (when did the client ask for that? No one knows), but hey, you could add services and their data to it, was it what the client wanted? Of course not! What do you think we are? Devs?
Suffice to say that, although we passed with good grades, the project and the team was shit (and I'm counting me in)
The good part is that the second project was finished by me and it looked really good, yet it didn't matter, the first project was supposed to be used by the university, but that thing was unusable.
Then, in the subsequent vacations I tried to make pretty and functional/usable, yet I failed because I had a deadline for another thing I had to do, but hey, the login screen looked amazing!

Imagine you're in a company, one year in now. You've tried your best to amass as much knowledge of legacy services as you can (specially given no documentation) and you think you've done the best you can.

Now imagine your manager is upset that you haven't gotten as much domain knowledge as an engineer who's been in the team for five years now. Then also imagine that your manager whenever asked about specific product or tech or any knowledge on a service just keep tagging the 5 year engineer. If he ever gives an update in slack on any incident, he doesn't read what everyone has written in the channel so far, but invites the team on a call, and asks them to verbally tell him what to write as an update so as to show he actually understands it all and is showing leadership. What do you do?

Also I've read a good manager let's his team self function without any micromanaging but I feel this is literally hypocritical (lack of knowledge comparison) and useless of him to essentially making no decisions or understanding anything without pointing fingers. What would you all do about this kind of manager, or am I just inexperienced and maybe not seeing what he's actually doing and contributing.

There's a team where the leader has some real weird/bad ideas here, it's like, ugh, no. I can't say no because I'm not in position to contest, but geez I so want to.

Like, we wanted to load data with pagination because there could be a lot of them (could reach thousands objects of data easily).
Team Leader: No, no pagination because that ask to call those services several times. Only one call, you load all the data in the same single page and you don't call the service again, so stock them in cache.

So the idea at first looks bad, and after analysis and research, it is real bad, of course.

I've been writing on this TCP server the last few days to integrate our software with some services used by the rest of the company.
Noticed the company service keeps making a new connection for every single message, and closes this at client side (without signifying the server).

So I contact the team who wrote these services and ask them what's happening. Team lead of that team doubts that I know what I'm talking about and tells me TCP automagically signals the server on disconnect, and this probably is a .Net only problem.

5 seconds of googlefu: half open tcp connection.

Apparently, the application doesn't care about dropped connections and losing connection states even though every service should be checked for licensing when connecting to the server. With this set-up everyone can just send a message other than the registration and pass through any 'validation' due to the fact there can be no connection state.

F*CKING INEPT IDIOT(S) OF TEAM LEAD/DEVELOPER TEAM!

This morning at 5:30 AM I was awoken to 20 text alerts for services being down.
Seems they had been down since 2 AM but the previous shift didn't take action.

Long story short:
An outsourced common component is unavailable, and the team responsible doesn't know how to troubleshoot.
I pointed them to the exact issue.
We are now 10 hours into the outage and they still don't know what to do.

What CI software are you using?
Are you happy with it or what do you hate about it.

I tried 5 different CI platforms in the past week, and I did not like any of them..

Any recommendations? (Can also be self hosted, I have a k8s cluster at my disposal)

// a short rant about team city
wE uSe koTliN dSL to reduce how much configuration is needed, fuck you I ended up with even more, it's horrible I have 40+ micro services, meta runners sounded like a awesome feature until I found out you need to define one for ever single fucking project...

Oh and on top of that, you cannot use one from root parent, but also it cannot be named the same.

Why is all ci software just so retarded - sorry I really cannot put it any other way

My afternoon has been worse than pulling teeth:

Me: "Hey services admin group, I need a ClientSecret generated."
Services Admin: "We can't do that, but we talked to the original dev team and they can. Go to their Slack channel and someone there will do it for you."
Me: "Hey original dev team, can you create a ClientSecret for me?"
Dev Team: "Does your team lead sign off on this?"
Team Lead: "Give him whatever permission he needs!"
Dev Team: "You should be able to give him whatever permissions he needs"
Team Lead: "I cannot"
Dev Team: "We just gave you permissions to give him permissions"
Team Lead: "I don't know how to give him the permissions he needs. Why didn't you just give him permissions"
Dev Team: "This scales better"

That moment when I suddenly notice that I've been working for two days on my repo that is hosted on Microsoft Team Services, while the active repo is hosted on Gitlab

Luckily changes where on a sub library can be managed to integrate a diff

Microsoft Visual Studio Team Services absolutely crushes Bitbucket for personal private repos.

Client would say we do not want to be billed on per manpower basis, but on entire managed service basis

However, the pricing for managed services they would agree on, can only pay for a team of 4, and the project requires a team of 8

I’ve been at this issue at work for four days now and no progress and I feel really bad because we have important stories to pick up and I feel I’m wasting my capacity like this because I haven’t fixed it. Basically, only in our QA environment (one before production) our services is not acknowledging duplicate events posted by Kafka, thus keeps reprocessing them. I’ve spent so long trying to diagnose the code, which is the same in all envs currently, seeing how this suddenly occurred, restarted things, went through complications of using different tools, asked for help from others a lot but IVE gotten NOWHERE. Idr wanna say to my team that I should prioritise other things because we have deadlines but I feel this issue is important to fix but I just can’t figure out how. Now I’m worried this whole sprint will go without me doing anything and then fingers pointed at me later

When the services team asks the mobile team what the response on a request is... And then requests console logging on the app so that they can test their code.

I work solo on the Network Services Team at American Eagle as a developer. I've been working on an application for diagnosing wireless from a devices perspective.

I'm extremely happy that my app will be rolled out to the first store for real testing, and get some feedback :)

Hey, so i am a junior dev and work on core services of the company. The work is great, my team is great and manager is pretty helpful. I have been with the company for almost 3 years now and was my first role out of college. My manager has been really relaxed in working with alot of my irl stuff and seems pretty leniant than what i usually hear from others.

Question is there is a smaller company trying to build a new team in my city and is offering an intermediate role with about 30-40% increase in salary if i clear the interviews. Is it a good idea to switch if i am really comfortable in my spot and even during the pandemic my company was super stable.

Also i have been hinted that might be getting a promotion by the end of the year or something like that. But when i asked bluntly about the compensation change i wont be getting as big of a change as the other company. A friend suggested that i go through the interview process and use that offer to get better comp, i have read somewhere that that tactic might be harmful in the future. Just wanted some pointers or anything you could pitch in :)

Sharing WSDL documents with the outsourced team multiple times through the course of a project leading me to Google mental health services in their location.

After a year of this I'd willing to try electro shock therapy if it gave them peace from what I can only imagine is a confused nightmare of forgetfulness.

I was trying to add someone to a team project on visual studio team services; i saw "no identites found" when i typed their email in so i thought it wasn't the correct way
I wandered around fiding nothing, eventually coming back to the first form
I type the email again, i don't pay attention to "no identities found" and add anyway : it works
wow didn't expect it to be that simple

Does anyone here have any experience in the Collegeint Cyber Defense Competition (CCDC) or similar red team / blue team competitions? I am trying out for my schools team in the fall and am looking for any advice or resources anyone may have.
.
.
So far I am leaning towards Phantom as far as what service I would be best equiped to admin but would also love to hear everyones experience with other services if they would like to share.

In few months I went from working independently on a project while developing lots of vertical knowledge to being body rented to another company where I spend most of my time doing calls and continuously reworking a suite of over engineered micro services (after ages instead of progressing we’re rewriting for the nth time basic CRUD because the team keeps coming with new refactoring ideas and since budget/time limit aren’t tight nobody on the high management seems to care of the time we’re wasting). I miss being able to stay “in the zone” for hours without calls, being challenged and learning on the job so I’m considering to find another job.

So I work with another team that develop services I use for my website.

The thing is, when they do big changes, I am not warned. So when I update my proxies, surprise, don't compile anymore, have things to change.

Worse is, I have their code right now. And the code that is deployed right now. They're not the same. So I know that I'm gonna have to change again things some days, but that's because I searched through the code.

I was away sick for a week. Come back to a chat log with messages about how the other dev team is trying to figure out a solution to a bug that they only show three services listed in the system.

Me couple of weeks ago on my second day in the project figured it out relating to a task I was doing. It's not a bug, it's a feature. It's a constant defined in the constants-file.

And the best thing: my team mate quoted me and said "Lankku figured it out last week". And it was passed down back to the team who had actually developed the whole feature and couldn't figure out why it was working so now. xD

Is OMEGA CRYPTO RECOVERY SPECIALIST a Genuine, Legit Lost Crypto Recovery Company.

OMEGA CRYPTO RECOVERY SPECIALIST is a company that was founded 22 years ago by a team of experts in the field of cryptocurrency. The company offers a range of services, including recovery of lost or inaccessible crypto assets, forensic analysis of blockchain transactions, and security consulting for individuals and businesses.

The company has gained a reputation in the industry for its expertise and professionalism, with many customers praising their services on social media and review sites. One of the key services offered by Omega Crypto Recovery Specialist is the recovery of lost or inaccessible crypto assets.

The company uses a variety of techniques and tools to recover lost assets, including forensic analysis of blockchain transactions, brute-force password cracking, and social engineering. The company also offers security consulting services for individuals and businesses to help prevent future losses.

Webpage: omegarecoveryspecialist . c o m

Alessandro Demarinis Yonkers

Address: New York, USA

Alessandro Demarinis of Yonkers owns and operates a reputable plumbing company in New York. Alessandro Demarinis of Yonkers provides top-notch plumbing services tailored to meet individual residential and commercial business needs. Alessandro Demarinis of Yonkers employees a team of highly skilled and experienced plumbing professionals, dedicated to delivering exceptional results in a timely and professional manner.

#Plumbing #Alessandro Demarinis Yonkers

Plz help me to choose between two offers.
First one is a services provider firm where I would get to work alone on projects for clients. The con is their is no Senior Android Developer's in the firm
Second one is a startup where I will be working with a team on their product.
Points to be noted :
1) I am a fresher
2) both companies are offering me same position (Android Developer ) and salary.