@Proximyst Not sure what you mean by that.

All I know is the minute the project manager that was at the firm I freelance for was fired, giving time management of the projects directly to my dev team, productivity shot up and customers were much happier.

I have yet to find a single place where project managers didn't create a disconnect between clients and developers. It's either lying to the client to buy time they underestimated, pressuring devs to meet unrealistic goals or both.

Project managers are glorified middle managers. I like to call them seagull managers, because they fly in, shit all over everything, then fly out.

Every task I give to a developer gets done in a timely manner because I let them manage the schedule of their work. If they can't manage their schedule, I find a developer who can. It's that simple.

@gitlab True, but I'm also the developer, so I know how to schedule my own work so that doesn't happen.

The most general definition is someone who is comfortable with all layers of development.

For example, a full stack web developer is someone who is experienced and comfortable working in both back-end and front-end.

How could you be sued? Did you sign an NDA? So long as you are writing truthful statements that are documented with proof and you didn't sign an NDA, the only reason for a lawsuit (libel) would not hold up in court, because they would have to prove that what you're saying is definitively false. If I were you, I'd most certainly reach out to these clients with a security notice, because this is something that should be brought up to everyone involved immediately for their security. As long as you aren't bad mouthing this agency and just calmly and professionally laying out the facts, you would be legally in the clear.

If however you are uncomfortable taking that risk, send out anonymous emails to these clients to raise awareness. They can't sue someone they can't find 😉

Oh c'mon! You can't build it up like that and not share it!

Don't get me wrong, CSS preprocessors can save time and help organization, but it really depends on the project it's being applied to and how that project uses elements on a page. I personally never use LESS/CSS/Stylus/[whatever other preprocessor] because it creates a few problems.

1.) I now need to rely on something to process the pre-processed CSS into a production-ready stylesheet before it is production ready. If I rely on a javascript-based processor, that's more unnecessary overhead on the page. If I'm on a different computer, I need to install that preprocessor's or find a web one.

2.) If there is a minor emergency and something needs to be fixed on the CSS while I'm on the go, I have one of two options. Either I open the production, minified CSS and make my edit, or I need to install said processor, edit the preprocessed code, process it back into production ready CSS and upload it. Neither option is fun when I'm needing to modify this while all I have on me is a phone.

3.) In the past 10 years of front-end development, I have NEVER needed a CSS preprocessor. Why? Because I have never needed to write more than 2,000 lines of CSS at the very most. Typically I have an entire website designed writing at most 500 lines of CSS for the design and another 150-200 for the responsive adjustments. A preprocessor's methodology of organizing and ordering code actually hinders my ability of styling a website fast and putting it in what I feel is a more human-friendly structure. Variables and mix-ins are nice and all, but not at the cost of what I feel is an unnatural order of operation and less freedom of specificity.

All of the above is subjective of course, but for me a CSS preprocessor does more harm than good on my own productivity.

@jhh2450 Pinball truly was the greatest feature of Windows XP. Played probably 1000+ hours of that.

@jhh2450 except it's not as good as pinball or minesweeper 😂

@PikaDude They do it to make money from the developers of the game in order to entice people to play it since it's already installed.

They are actually not taken. 2 letter entries for domain extensions are almost always reserved for special use cases. You could contact the main .li registrar and ask them if you can buy it, but they'll probably tell you no.

Life is full of #666666 areas.

@MrCSharp You "interpreted" it a certain way. Keyword here is "interpreted". Well guess what? You interpreted it wrong, I tried to explain it to you better and you threw it in my face. Providing clarification and more thorough explanation on one line of text to help you understand the reasoning behind it is not "spinning" anything. You can't completely discern intent from that one sentence.

But as I've said, if there is an issue that effects the ability of reading or traversing the website, that is classified as a layout issue and of course that would be handled. Good for you and your company for supporting a browser almost nobody will use. We're not going to recode a purely aesthetic feature because Edge doesn't support it using a standard that every other browser does, especially not with less than 5% market share. I guess by your logic that GitHub dropping I support makes them lazy oo, right?

Arguing that Chrome also shares usage information doesn't magically make IE/Edge any less of a shitty browser than it currently is. That's a diversionary tactic and a weak one in an argument, rather than actually addressing.

You've clearly shown that you want to come in and insult like a dick based on one sentence that you decided to fill in the blanks for, rather than be a reasonable person and just ask for clarification, and I'm done trying to be reasonable with you. You're just an asshole and I have more important things to do than address your holier-than-thou admonishing.

I see no problem here.

@Devnergy "Winamp! It really whips the llama's ass!"

😂

@Cyanide I had to condense it because of character limit sadly. 😂

@argorain You're welcome!

Try Ctrl+Fn+B for Break and see if that works.

@darkMatter You bet it is! Gotta get my daily dose of iron somehow! 😉

@Michelle the fact that you're still commenting suggests otherwise, but whatever makes you happy I suppose.

@seraphimsystems Mustn't forget mace 😂

@irene and you are welcome to your opinion.

@Michelle War? I'm just sitting here laughing at your comments. I can't begin to take you seriously. 😂😂😂😂😂😂😂😂😂😂

@Michelle

@Michelle Yes, I consider it a joke, as do others. I was playing the stereotype on devRant for laughs, and if even one person enjoyed it, it was a success. If you want to be in an uptight, pissy mood, good for you.

@AlgoRythm @Michelle If you look at the tags for this rant, you'll notice a couple that help explain the context of the rant.

If you took this rant seriously, you lost. 😂

Howdy Neighbor! Greetings from Missouri! 👋

@shellbug I hear ya. And yeah, the looking down part is utter bullshit.

@mmcorreia Please don't read too far into my comment. Take it for face value. I'm full stack and have worked both ends for years. When it's relevant, I discuss backend with frontend developers and vice-versa. It's not a matter of not valuing their input (I have a coding standard in place that prohibits pulling rank), but from a practical standpoint.

Well, I probably wouldn't want to discuss backend API endpoints with someone who works solely frontend either. Mainly because the thought and development process of the two ends tend to widely vary. While frontend is prioritizing UI/UX, backend is prioritizing data and resource efficiency.