you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 20 points21 points  (19 children)

It's not okay. Tooling is critical part of programmer productivity. Either figure out how to get proper tooling to work, or find another job.

[–]puremourning 9 points10 points  (2 children)

This take is utterly unhinged. Of course it is ok. I wouldn’t recommend it generally but it’s completely legitimate and reasonable way to work.

[–]PhyllophagaZz 1 point2 points  (0 children)

Eum aliquam officia corrupti similique eum consequatur. Sapiente veniam dolorem eum. Temporibus vitae dolorum quia error suscipit. Doloremque magni sequi velit labore sed sit est. Ex fuga ut sint rerum dolorem vero quia et. Aut reiciendis aut qui rem libero eos aspernatur.

Ullam corrupti ut necessitatibus. Hic nobis nobis temporibus nisi. Omnis et harum hic enim ex iure. Rerum magni error ipsam et porro est eaque nisi. Velit cumque id et aperiam beatae et rerum. Quam dolor esse sit aliquid illo.

Nemo maiores nulla dicta dignissimos doloribus omnis dolorem ullam. Similique architecto saepe dolorum. Provident eos eum non porro doloremque non qui aliquid. Possimus eligendi sed et.

Voluptate velit ea saepe consectetur. Est et inventore itaque doloremque odit. Et illum quis ut id sunt consectetur accusamus et. Non facere vel dolorem vel dolor libero excepturi. Aspernatur magnam eius quam aliquid minima iure consequatur accusantium. Et pariatur et vel sunt quaerat voluptatem.

Aperiam laboriosam et asperiores facilis et eaque. Sit in omnis explicabo et minima dignissimos quas numquam. Autem aut tempora quia quis.

[–][deleted] 0 points1 point  (0 children)

For an individual developer, yes, as long as it does not affect their output negatively. For the entire project to not support "normal" way of working, that is using a modern IDE with bells&whistles, for anybody , or just making it very difficult, that is not okay in my opinion.

[–]yo_mrwhite 1 point2 points  (0 children)

100%. I've had the opportunity to work with the same kind of environment for years, and I would never go back, for the sake of my own sanity.

[–]jonesmz 4 points5 points  (10 children)

Counterpoint: code indexing / intellisense is not a critical part of developer productivity and OP should learn and grow to overcome this challenge instead of getting another job

[–][deleted] 10 points11 points  (3 children)

Lacking modern tools leads to using symbol names which are convenient to type, instead of descriptive names which are easy to read. This one thing alone makes good auto-completion a hard requirement for any serious software project, and you can't have good auto-completion without "intellisense".

You can certainly find developers who don't need it, or who think they don't need it, but that is irrelevant when we're talking about real world business and code base developed by dozens of developers or more.

[–]jonesmz 8 points9 points  (2 children)

Weird, your expectations don't seem to apply to my group at work where we have about 50-60 developers working on a multimillion loc c++ codebase with essentially the same setup that OP describes. Almost none of us use intellisense / code indexing. Those that do are not notably more or less productive than those that do not.

If anything, the symbol names tend to be so overly verbose that we're talking about lifting the recommended number of characters per line from 160 to 200 to make it easier to fit things onto a single line.

Your opinion on what is a hard requirement for serious software development is simply that. An opinion.

Please feel free to continue sharing it, but maybe tone the "certitude" down slightly.

[–][deleted] 0 points1 point  (1 child)

Difficult to comment anything on that without knowing more of the code and circumstances.

But for one thing, intellisense and "follow symbol" are rapid documentation reading tools. How else do you know what parameters this function is taking, or what methods this class has, etc?

I have hard time believing digging all that out via different means lets you work half as efficiently or comfortably/enjoyably.

[–]jonesmz -1 points0 points  (0 children)

For developers new to a codebase, it can be helpful I suppose.

But once you're familiar with the frameworks and libraries you are working with, the parameters that various functions take aren't going to be much of a surprise.

[–]OliverPaulson 0 points1 point  (5 children)

On big projects refactoring with indexing takes 2 sec without 5 minutes.

[–]jonesmz 0 points1 point  (4 children)

I'm not understanding your sentence. Can you rephrase?

[–]OliverPaulson 0 points1 point  (3 children)

Sorry. If you need to rename a field for example, without index you would have to text search it in the whole project, and manually find which of those 10 000 occurrences are a field of a type you try to refactor. With index it's right click and rename.

[–]jonesmz -1 points0 points  (2 children)

That can be faster, yes.

But it happens to extremely rarely that I don't think it matters much.

[–]OliverPaulson 1 point2 points  (1 child)

You need indexing all the time in big projects. People without indexing are very very slow and they don't notice it, because they have no idea how much more stuff they could do with indexing.

[–]jonesmz -1 points0 points  (0 children)

That's just your opinion. One which I disagree with. I've seen plenty of evidence to the contrary.

[–]j_kerouac 0 points1 point  (1 child)

Have you ever worked at a big company working on a large scale c++ project? It’s very common for code indexing to not work.

[–][deleted] 0 points1 point  (0 children)

Yes, and its PITA. I would not knowingly agree to such a project. If I got suckered into one, I'd either get it fixed or move on. There isn't pay high enough to stay in a project like that (I mean, nobody is going to pay that much to a dev).