Trump will probably just sell our military tech to Putin to make a buck so there's that.

F-16s sold to Ukraine flying against F-16s sold to Russia = mo money, mo money, mo money!

The assets of the US are just things to be sold to make money in his eyes. That's how companies work!

It's all part of the master plan: https://www.facebook.com/share...

We are only allowed to use Copilot at work. Itâ(TM)s a dumpster fire. The unit tests it writes are so naive they might as well just be âoeassert trueâ. Most of the time I have the line of code written before it suggests something. Half the time what it suggests is wrong. It gets in the way more than it helps.

A coworker tried ChatGPT on his home laptop for a problem we were working on. It had the right approach but didnâ(TM)t understand the data so it wouldnâ(TM)t work but at least it set you in the right direction.

So far Iâ(TM)m not impressed.

Agree with the point that if you are wanting to improve developer productivity give them silence and offices with doors first like the research has proven out. There is over 100 years of research on human performance that is ignored by companies. Start there.

I can see the point on restricting languages too as it can go too far into there always being some subset of the developer population in learning curve mode if you have too many. We recently did that and I think there are like 7 or 8 approved languages at work now which I am ok with.

OTOH, I'm less impressed with the kind of thing Golang has done with the attitude of, "we'll just make the language itself simple and remove useful constructs because developers can't handle the mental complexity." The idea makes sense (less complex = less errors) but in my limited experience with it I had to over-complicate the design to support unit testing and having paths with "www.github.com" in them made feel like it was designed by weirdos. The single workspace thing didn't fit with us either. At the time there was also no debugger which was a dealbreaker for me. I hear it is better now though on some of those points. Dumbing down the language so that you can hire developers that are less smart seems like a lose / lose if you actually take the bait.

Because the common cold doesn't give some subset of people who catch it permanent brain fog via a mechanism we don't understand.

To me it's like Pascal's wager. I will continue to wear an N95 in public which isn't a significant cost or inconvenience. If it prevents me from being unemployable due to long COVID brain fog it was worth it. If I wouldn't have gotten long COVID anyway without the mask I don't lose anything significant. It's a win/win. If I did get permanent brain fog via long COVID it's a huge loss of my huge salary. For me it's not a risk worth taking.

Same reason I lock my car and the door to my house. It costs me nothing and may keep out some subset of thieves.

There was a British Documentary in the 1978 called Connections where a science historian walks through the history of different technologies and shows how a bunch of often unrelated discoveries led up to something we take for granted today. When I was a kid that was one of the things that really got me interested in science.

Because Snowden said so.

It's way better. If I am in a meeting and get an IM and can respond now I will. If I get a voice mail or call, it's too disruptive and I won't.

Also there is an underlying false premise that when in the office people don't:

ever leave their desk
ever have meetings with people who aren't you and can't be found
ever use the bathroom
ever go to the kitchen to get coffee
ever go talk to their friend on another floor
etc.

The idea that people in an office are always at their desks and available is BS. I have IM on my phone. If I'm at home and get IM I will respond. If I'm in the office and get an IM I will respond. If I don't respond, I'm either talking to someone more important than you or taking a dump so back off already...

Any response to articles like this talking about how the runtime is crap?

http://dtrace.org/blogs/wesolo...

Outdated was your word not mine.

The way you blithely dismiss anyone's "anecdote" on how Eclipse was an epic fail for them makes it quite clear you think they are a moron. I don't have time to go back through your posts to pick out everywhere you blame flaws of Eclipse on operator error.

The button was "stop debugger". Every time I started Eclipse the UI state was as if the app was running in the debugger. Bizarre to be sure.

All I know is that one IDE let me get my work done and the other was a constant battle to keep running.

So, it sounds like you are saying that you love Eclipse for what you are doing and you want people to try and convince you otherwise. Why?

If it works for you, that's great, but this approach you seem to be taking that anyone who doesn't like Eclipse is, "outdated", or a moron because you've never had that problem before is just petty and ridiculous. You've obviously been using Eclipse for a long time and have it set up in a way that works for you. Good for you.

For folks who are new to Eclipse, like me, I have to agree with the folks who say that the UI is heavy, ugly, and stale. In my limited experience (on OS X, a year ago) I saw toolbar buttons enabled when they weren't applicable. If I pressed one then a dialog would pop up saying something like, "That button isn't enabled." Really? If it wasn't enabled then how did I press it and make you show me that message? So, first impression was that it is low quality. If the UI can't even keep state straight then it feels like a toy. I know, it never happened to you, so it never happened...

So, then I'm working on a RESTful API and the "built in" Tomcat just stops working. So now I can't debug the thing I was able to debug 5 minutes ago. What happened? So I ask the developers who are familiar with Eclipse and they can't get the "built in" Tomcat working again either. Lame. Time to hit Stack Overflow...

So, I take the time to set up key mappings and Fonts & Colors (for which the settings are spread out in different sections). Almost every other time I start Eclipse, my key mappings have been reset for no apparent reason. They're just gone. If I change workspaces I have to set it all up again as well. Lame.

So, yeah, I expect that if you have been working with Eclipse for many years and have already learned its quirks then it seems natural to you now.

My experience with IntelliJ Community Edition on the same machine was that the UI was more modern / consistent, debugging from IJ to standalone Tomcat never gave me a problem, and my fonts, colors, and keystroke mappings never got reset to default values. Everything just worked out of the box with minimal learning curve whereas with Eclipse I was burning too much time on Stack Overflow trying to figure out why it was broken again...

RIght, but the contention was that it has no bearing at all. As you admit it is one of the questions so it obviously does have bearing. So, who are you arguing against?

IRS regs specifically mention working for only one company as an indication that you should probably not be considered a 1099. The company I used to work for offered me the option of being 1099 but the IRS guidelines clearly stated that was not appropriate so I asked to be brought on as W2. Even if the IRS wouldn't check, I don't see the point in putting myself in a position where I give them a reason to screw with me...

MS is laying people off left and right. What do they need more CS grads for?

I pretty much use the same tools for Windows / Java / OS X/ iOS and started my career about the same time. Pick the best IDE for the target environment / source language rather than one to rule them all.

I started my professional career writing Windows apps in C++ and never saw the point of the 80 character per line limited text mode editors that were available on Windows / DOS at the time. After college it was a long number of years before I saw Unix again, and by then I was accustomed to GUI based editing. I will never forget fighting with folks in the early 90s who wanted to impose a 80 character line limit as part of our coding standards because that's all they could see in their text mode editors. Bogus!

I have to say though that the worst IDE I have used is Eclipse. I spent about 6 months in Eclipse 3 years ago before a more senior Java developer showed me IntelliJ and I never looked back. Major gripes:

When you start Eclipse, the UI is already in a bad state. The toolbar buttons are enabled as if you are debugging. If you click the "Stop the Debugger" button, you get a dialog telling you that the button you just pressed is not enabled. Uh, yeah it was otherwise how did I press it to get this dialog? If you can't even get the initial UI state right, it doesn't inspire confidence! I still saw this in the last version I tried. I'm assuming that the design of the code must be so bad that this must be very hard to fix so it stays broken in version after version. And no, I'm not going to pull down the code and try to fix it when the community version of IntelliJ is free of cost and works fine.

So many times Eclipse would show all these red underlines in my code but when I compiled the code from the command line there were no warnings or errors. Deal breaker! Absolutely unacceptable waste of my time! All of the files had been saved. If it has no errors from the command line compiler it shouldn't be showing errors in the IDE. It's like the IDE is senile or something...

When I was developing servlets, every month or so the integrated Tomcat would just stop working for no apparent reason. I never had a problem with IntelliJ and standalone Tomcat.

Having to reset your font and color settings for each workspace is tedious. Having the IDE forget some of your key mappings when you start it, even if you haven't changed workspace is downright annoying. Another waste of my time. The whole thing just feels so brittle.

That's interesting. In retrospect, did you figure out what aspect of the communication was a barrier in the remote case that wasn't a barrier in the in person case (e.g. whiteboards)? Did you have video, shared whiteboards, shared document editing in the remote case?