@Voxera yeah, I've tried navigating around it by using Cake. It gets me some of the way, but I'm running into issues where MSBuild.exe is being looked for in different places - some that don't exist on my machine.

If run through the dotnet CLI, MSBuild is packaged separately. Then, visual studio has its own version depending on which version of visual studio you're using (hate the IDE as well) when you build.

Ideally, I'd just have all my build tooling in the repo, but I have to fight the tech stack every goddamn step of the way. I'm getting too old for this crap...

I blame hollywood for the wizkid hacker stereotype.

"I'm an idea"
- The Joker as portrayed by Jared Leto

So yeah, I think you're spot on.

Stared at my monitor, then out the window, then back at my monitor. Tried to deploy something, it broke. Had to roll back and nothing was accomplished.

So I feel pretty great.

@r-fu they have 30 years of stagnation more like

@LotsOfCaffeine There's a "new" sdk format that differs a lot from the previous one and you can even target Framework and Core simultaneously. The new format is amazing and perfect and I love it. But I'm still stuck on the old one for my web application that I am unable to update due to it being built on top of a third party CMS we can't get rid of.

So tired of shit not just working consistently in an idempotent manner...

Status update:
I had to scrap the whole thing. I would complain about juniors, but I know I wrote way better code when I was one. Completely unmaintainable, and they spent several WEEKS on it. I'm not sure how many man-hours went into it and I don't think I wanna' know to be honest.

@marcorodnav obviously it depends on the code base, but you can still apply patterns in your code and write it fast. Sometimes I'd argue it's faster, because it's something you probably have done before and can copy/paste where needed. :)

People who excuse their deeply nested unreadable code on tight deadlines have always bothered me.

I can't even write that sort of code anymore, because I can't keep track of what I'm doing.

@CoffeeNcode Yeah, luckily our deadline was moved back one week. I'm already rewriting the entire API layer for this component. I'm thinking of pretty much only keeping the styling. I only skimmed the code, but wouldn't be surprised to find DOM selectors in there as well...

Why not just use Trello then?

Blender's the only 3D program I ever "got". I remember using Maya once for some uni project for a couple hours because it supposedly was the "real thing". Then I gave up and went back to Blender since Maya want explicitly required. I mean, don't know about now, but Maya's UI was an absolute clusterfuck compared to Blender.

Angular ... JS

I mean, I guess if we're just redifining words, you can make anything sound profound. It's like saying it's lazy to take out the trash because it'll be harder to get around if you don't.

@JAY505 Frameworks solve common problems and abstract existing complexities. It would be like saying using patterns is adding complexity. I mean, sure, but at least there's documentation for it. There are many reasons to not pick frameworks for a particular project. In this instance none of them apply.

@shivam-singh
Well, if you're getting paid hourly, then that's great haha.

Just show them differences in estimates, then they can figure out if they're willing to put their money where their mouth is.

And when they complain you can simply say: Well, you wanted us to reinvent the wheel for a prototype, so we did.

When you say "vanilla" JS and "no framework", does that exclude libraries like jQuery, bootstrap and the like? I mean, there's really no reason to reinvent the wheel in terms of grid techniques etc here if what you're doing is simply prototyping.

At my place of work we use UX tools for these things, although you can pretty much get away with simple ms paint images or physical drawings most of the time. It seems very expensive to implement functionality for the purposes of UX.

@FranklySimple
Alright. Here are some arguments you can use if you haven't already. Obviously I don't know the whole story and scope of your solution, but I think this is a good place to start:

1. It's more cost effective in both the short and long term to fix the current web app.
2. The app will perform better in Google search rankings as a result.
3. Users don't like installing your app from the app store if they can avoid it. They RARELY search for it in the app store.
4. Users expect native capabilities from native apps and will hate your solution if their expectations aren't met.
5. The app will get buried in down votes and leave a negative impact on its users.

You can also start questioning the business case behind the native app. Why does it need to exist? What business goal does it solve? I firmly believe this "solution" of his will do more damage than solve any particular problem. Truly a "don't build something nobody wants" scenario.

Depends on what you are building and your level of experience.

For me and my use cases it goes as follows. Keep in mind that everything in the end is just JavaScript:

Plain JavaScript: Minor DOM manipulation and some basic functionality.

JavaScript with jQuery library: Advanced DOM manipulation and some data fetching / posting to and from a server.

Angular/Vue/React: When you need reusable components in your web application and/or plan to turn it into a Single Page Application (SPA).

Bootstrap is not a JS framework and can work with any of the above approaches, although it does require jQuery regardless.

Once you get deeper into the weeds, you should start thinking about how you want to bundle your application's code and styles to minimize download size. There are many tools for that - webpack, gulp, grunt are the most popular right now.

I personally only write typescript and less at this point - simply because it results in more maintainable code compared to vanilla JS / CSS.

I really have to question why this needs to be a native app when most users hate installing yet another app and would rather access the site directly via Google in a browser.

You should really just fix the mobile frontend, then optimize for PWA standards. With service workers and the likes these days, you don't need a native app to do most common things. It would also get you a better ranking in Google. If you do it right, you can even mimic a real app on Android (don't know about iOS) when people add the site to their home page.

That really is the smartest solution and would stick to the "one code base" rule.

Legacy codebases? Older developers refusing to learn git? Who knows...

I've been fortunate enough to only use git in my career.

+1 for VS Code.
It's technically not an IDE, but with the right extensions it can have IDE like features.

@TheOct0 Thanks :)

I mean, as someone who made the switch to C# when I started working, NET Core especially is great to work with. Can't in all honesty say it makes sense to jump ship like that though.

@TheOct0 Yeah, hope so.

It's kind of a catch 22 though.
Loneliness makes me depressed, depression drives me away from people. Ech, life. ¯\_(ツ)_/¯

As I get older, my social skills worsen. I'm increasingly more awkward and I can't casual talk. I simply cannot bring myself to pretend I'm interested in people's vacation to [insert traditional vacation spot here]. I have never had a girlfriend, and only a couple of friends I actively talk to.

Then again, I've got depression to worry about on top, so that probably skews my personality. I still talk to people every day and can be quite sociable when the situation calls for it. I wouldn't really call myself anti-social for that reason, but I suppose it's in the eyes of the beholder.

Most people seem surprised when I tell them about my situation, so take that any way you wish.

Essentially (varies about 50/50, sometimes overlapping):
good days => very sociable
bad days => complete shutin

REAPER is really cheap and can do pretty much anything you want.

I'm a musician on the side and use it both for home production and live performance.

It's also extensible as hell. I haven't delved into ReaScript much, but you can program a lot of custom behaviors if you're into that sort of thing. I'd also recommend getting the SWS extensions (free, open source) that give you more advanced functionality in REAPER.

Feel ya.
I often start introducing bugs during the end of sprints to get the last stuff done in time. A lot of last-minute refactoring and reckless breaking changes will do that.

Sounds like you could use a bit more testing and code reviewing. (Something I wish I had the time for)

Unpopular opinion time:
Sometimes you have to swallow your pride and work with what you have. Sure, there was a bug in there, probably even major, but some of those 3 days you spent trying to get it to work on your OS could have been spent getting to know the project and maybe even developing it. I'm not saying ignore the bug, but I'm also not saying that it should stop you from working in the project. Report the bug, then try a different OS in a VM or something and see if you can get it working. The bug eventually resurfaced anyways, and at that time you would have a much better understanding of the project.

Of course, I can sit here in hindsight and all, but I think that's something valuable to take away as well on your part.

@rootshell Bad analogy.
Unless you want to extend it to something like: You have to paint the wall, making sure the color matches any house it's applied to. Also, while you're doing that, fix the sink will ya'? And we need a foundation, why haven't you made that yet? Oh, you made it, but the wall looks out of place in MY outdated house. How come the paint looks different on my wall? I thought you were a professional painter?

Read: Frontend is more akin to constructing a building than simply painting it. Centering a div is a common usecase, but not common enough so that it's all you'll be doing, far from it.

This is a prime example of why I despise "clever" analogies between traditional professions and software development.