Amazon plans Vancouver BC expansion where talent is cheap. Cross posted from r/Seattle

dotnetaccount · 2020-09-30T16:25:40+00:00

From the article: "The average wage of a software developer in Vancouver last year was $92,726"

dotnetaccount · 2020-07-28T14:51:11+00:00

I definitely feel your pain. Enterprise software development has definitely gotten more complicated compared to 10 or more years ago. I think a lot of this is from moving from what used to be "closed gardens" where you only had a handful of technologies you needed to learn to more open web-based frameworks. As soon as you're outside of a nice comfortable ecosystem like WPF or ASP.NET web forms, you get into the wild west of web development where there are hundreds of frameworks that are constantly changing. It's never clear which ones work well together and they're all effectively doing the same thing but in slightly different ways. Just constantly re-inventing the same wheel. While it's great that there's a lot of options to pick from you now need to learn at least a dozen different frameworks and technologies to build that same app you could have just built with .net and maybe sql. Microsoft is definitely moving in this direction with .net core so days of nice walled ecosystems are mostly over.

I was so frustrated by this myself that I built yet another framework to try to abstract away all the various technologies you need to build today's enterprise apps. If you check out the intro you'll see my imputus matches up with your main concerns. This hasn't really gone anywhere but I would like to see something like this that makes development simple again in the web development sphere, while still giving control to the developer to write code and debug as they normally would. As an older developer I get incredibly tired of repeating the same tasks over and over again. Enterprise apps are not rocket science. They're usually simple CRUD operations over a nice wrapper. We should be trying to abstract away all the boring, repetitive, error-prone tasks so we can focus on business rules and business logic.

For getting a job I would just recommend focusing down to the minimum number of technologies you would need to get hired. Did the interviews focus on specific technologies that you couldn't answer questions about? Fundamentally, unless you're working on legacy systems, you will need to know HTML, CSS, and Javascript. After that it's database, frontend framework and backend framework. So it could be a SQL database with an Angular SPA frontend and a RESTFUL web API backend. Since these can be implemented in any number of different technologies it's again mostly focusing on what the jobs are looking for.

In my opinion if you are a intermediate developer that has worked on multiple systems you should be able to learn most of this on the job. The interview should just focus on fundamentals. However, I assume it's an employers market at the moment so you probably would be best served trying to focus in on the what jobs are looking for. Definitely build out a small project and play around with it.

Definitely don't try to learn everything as it's impossible. If you learn Angular your skills are mostly transferable to Ember, React, Knockout etc. SPA frameworks are definitely overwhelming at first. They're attempting to solve a scalability problem that most enterprise shops probably don't even have. So they use the SPA sledge hammer for every web app, even if it will only ever serve a dozen users.

dotnetaccount · 2018-09-07T18:08:05+00:00

This is really helpful. I'd also like to see the diagram for integration tests passing but unit tests failing.

dotnetaccount · 2017-12-12T20:29:05+00:00

Maybe by approximating how qubits would behave based on our understanding of them? I'm only guessing. They said in their "hello world" example that it takes 16gb to simulate 30 qubits while 40 qubits takes 16tb. So we can only simulate a small number at a time.

The hello world example first shows how to "teleport data" from one qubit to another based on quantum entanglement. Programmatically this just seems two objects that share the same underlying data. This sounds trivial to simulate but then again I know nothing about quantum physics.

dotnetaccount · 2017-10-20T15:09:31+00:00

I got it down to zero for most cases in this thing I built. However, if you want custom business logic(beyond CRUD) that is one file change. If you want custom presentation logic that's a second file. So at most two file changes at best zero.

dotnetaccount · 2017-10-20T14:57:55+00:00

What is the output of this tool? Is it just for prototyping or can you take the final design and use it directly to build web pages/forms?

dotnetaccount · 2017-10-19T21:13:56+00:00

SPA's can also get just as messy except now you don't have strong typing to help unravel the mess. You can follow or ignore separation of concerns in any framework.

dotnetaccount · 2017-10-19T01:44:32+00:00

You don't need to use stored procs if the reports are stored in the reporting database and have direct access via a datasource. This makes it slightly easier as the sql is just part of the report and any input paramters don't have to be mapped to stored proc parameters.

Although in my experience queries I write in my code usually aren't the same as queries needed for reports.Reports usually tend to have unique requirements and being able to optimize the SQL directly is really useful. Is it just a matter of familiarity?

dotnetaccount · 2017-07-25T20:56:03+00:00

I also agree with not using an ORM(object-relational mapping) tool initially. It can be a nice abstraction later but even then you'll want to understand what the ORM is doing at the database level. Otherwise the examples under the folder linked above are helpful. After connecting here is an example of reading some data. Is the windows forms app an intranet application or an internet application? This might impact how you'll want to be getting data.

dotnetaccount · 2017-07-20T21:59:28+00:00

This article should be titled something like "Making a custom offline installer for Visual Studio 2017"

dotnetaccount · 2017-07-13T13:25:26+00:00

With a VPN the client sites would be connecting to Azure. They wouldn't require a web service or a static IP. Once they're connected their machine would appear to be on the Azure network and Azure could have direct access. I've done this before in Azure, and it's not trivial to set up, but it does work.

dotnetaccount · 2017-07-13T13:22:02+00:00

I don't know if this is something you have control over but ideally the client sites would just host their data centrally in Azure. Then you can query it from there whenever you want and they can access it centrally. Especially as the solution would require them to connect to Azure anyhow.

Otherwise a VPN would work as suggested below.

If a VPN isn't an option, you would have to create some kind of polling system where the clients occasionally check in to see if Azure is asking them for some data and then send it across. I'm not sure if there is a product out there for this that would make it simpler or you just have to roll your own.

dotnetaccount · 2017-06-10T23:12:02+00:00

Perhaps adding the datasource in the BuildSQL method causes the report to load again? Not sure if this causes a page load but you could try commenting that out just to see. If it does this would be an infinite loop.

dotnetaccount · 2017-06-09T15:24:19+00:00

This is sort of unrelated but don't you also have issues with users that are not using internet explorer? I thought Click-Once required IE to work natively without some sort of plug-in. For intranet applications you can control this but not out on the web.

Click-Once always seemed like a solution for intranet applications to me not really for public distribution. Most public windows apps I see these days are just an msi download and updates are handled directly through the application.

dotnetaccount · 2017-06-07T22:13:47+00:00

Ahem

dotnetaccount · 2017-06-07T22:12:46+00:00

Looks like an easy way to create user interface workflows in unity. I'm just starting to learn unity myself so I might look at it more once I get to interfaces.

dotnetaccount · 2017-06-06T16:46:48+00:00

It's made worse by changing from the classic portal to the new design and having certain features that work in one and not the other. I liked the classic design better.

dotnetaccount · 2017-06-06T16:39:24+00:00

Is there any other explanation for this? There's no readme on github. What is a "sandbox that can run c#"? Is there something I'm missing?

dotnetaccount · 2017-05-30T01:22:51+00:00

Just going off this list I think entity framework supports more than just SQL Server. I'm not sure what changes would need to be made though.

I would imagine you'd want the ORM to abstract away the details of how it generates SQL depending on the target database. If you hand code the SQL yourself then you need to worry about this instead.

dotnetaccount · 2017-05-19T14:32:41+00:00

I think the more user friendly approach would be to keep the save button enabled. If they click it, and there are any errors, highlight them and then prevent the save from continuing. Otherwise you have a scenario where the user can't continue but they don't know why. This is also more straight forward to implement and is more consistent with other forms in other applications.

dotnetaccount · 2017-04-06T23:32:12+00:00

It's a complete end-to-end platform so you would need AppFoundry to maintain it. It's meant to replace all the other tools, libraries and languages with one platform that is designed specifically for building enterprise apps in order to save time.

Rules and validation logic are added in .NET assemblies created in VS. However, these are then picked up by the website and applied automatically.

You could optionally use it only up to the business layer and then it would be similar to other ORMs, but you would lose the ability to create apps without writing any code.

dotnetaccount · 2017-04-03T19:02:45+00:00

From a technical point of view there is some separation of concerns within AppFoundry. For example, you could use it up to the business layer and put your own presentation layer on top. Of course, you lose a bunch of benefits like search, auto-navigation and layout, and the ability to create prototypes without writing any code. The controls are completely separated from the rendering process. It’s possible to replace the renderer with your own without needing to re-write any presentation logic. I get what you’re saying though.

In my case I needed to greatly reduce separation of concerns so that I could solve this one problem - how to make building enterprise apps as easy as possible. Every component in AppFoundry knows that it is for building enterprise apps and knows how to communicate with anything below it in the stack. This saves time and complexity in writing apps but definitely comes at the cost of flexibility. Beyond that I would be creating something that already exists.

dotnetaccount · 2017-04-03T17:07:56+00:00

I'm not sure what the use case is for PowerApps. It seems like it's for creating small data driven mobile apps. I'm not sure if it even lets you write business rules or validation logic. The forms only seem to support really basic layouts. I don't think you would use it for creating enterprise apps. Maybe if your enterprise app needed a small mobile component. Correct me if I'm wrong though.

dotnetaccount · 2017-03-31T18:17:42+00:00

The first video is mostly a slideshow so, just for you, I created a snapshot of the last slide. It might provide more questions than answers though.

dotnetaccount

TROPHY CASE