|
I think I have a desk somewhere. When I find it I'll let you know what's on it...
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
|
Was checking your list of items on your desk. Are you sure you didn't forgot to mention your boots and an obese tomcat? Maybe some spare motorcycle parts as well? 
|
|
|
|
|
Orson farm[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
excellent 
|
|
|
|
|
reason 2 for why I had my tongue cut off.
|
|
|
|
|
Is it valuable or a good idea to know more than one web stack? I've spent most my time working with C#/ASP.NET and associated tech but the majority of guys I am close with in my area use MEAN stack, in addition, my goals are to work for a startup or smaller business and they tend to use MEAN stack around here as well.
For this reason, I've been learning MEAN, which, in reality, the A and other front-end stuff is actually used in ASP.NET often anyway, so there is some overlap in knowledge.
However, my OOP brain isn't used to thinking functionally like I have to in MEAN sometimes, and it's a challenge for sure, but also fun. If nothing else, I figure I can weigh the pros and cons of both stacks and use them when convincing an employer to use either one.
|
|
|
|
|
TheOnlyRealTodd wrote: Is it valuable or a good idea to know more than one web stack?
For me it is. This will enable you and your team to have greater flexibility on which stack to use for each projects that requires it. We've been doing MS stack before but now, we are starting to explore on MEAN to cater projects that needs it. At the same time, we've been exploring into .NET Core too to build xplat apps.
|
|
|
|
|
There's a world of difference between SQL and NoSQL, though in both cases, the back-end can hide the implementation details, which has its pros and cons. Pros: You usually don't have to think about it. Cons: When you do have to think about it (optimization, digging into the data to figure out how to model a particular bug) it can be a real PITA if you don't know it well.
Be careful of why startups tend to use the MEAN stack. The two most common reasons I've found is:
- They don't have any money to invest in proper tooling, so they go open source (which isn't bad, per se, but...)
- As I've encountered all too often among hackers that just want to start coding their new cool idea, "let's use NoSQL!" followed by a group mind-fart: "oooh, yeah, cool tech I've been wanting to use."
More generally, yes, learning the nuances of thinking functionally vs. imperatively is definitely a worthwhile exercise, as is learning more than one web stack, if you have good reason too.
Marc
|
|
|
|
|
|
As a rule, knowing more stacks allows you to choose the appropriate technology for each project (e.g. the requirements for Amazon's web site differ from those for your local church). The catch here is that you must know the technologies well enough to be able to determine when each is appropriate. This comes mostly from experience.
By analogy from the physical world, a good carpenter should know when to use carpenter's glue, nails, screws, or other fasteners. Each has their place, and it is a poor craftsman who believes that only one type of fastener answers all problems.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Or rather, a good carpenter should know how wire a new plug onto any of his power tools, and maybe do very simple mechanical repairs to them.
|
|
|
|
|
Daniel Pfeffer wrote: it is a poor craftsman who believes that only one type of fastener answers all problems
What, you mean that all those other things you mentioned can be used as stand-ins for nails?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
No, I mean that different types of fasteners are used in different circumstances.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Really? Golly.
Given that that's precisely what you said, I'd never have guessed that it was what you meant.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Never heard of the term MEAN before, but often come across, and am currently using that exact stack to tutor myself on nodejs hosted web sites. All the resources I've found use Mongo, but I feel Mongo is just not right for tabular data, and will eventually substitute PostgreSQL. Overall, I think it's a good stack though.
|
|
|
|
|
Have you found any solution to debugging in MEAN? I'm struggling hard on this right now. It seems to be hell/non-existent compared with ASP.NET.
|
|
|
|
|
Well, for Angular, the Chrome console is magic, and there are extensions for viewing Angular entities, and for nodejs, there is Node Tools for Visual Studio. I haven't played with it much, but it looks promising. With node, you don't need a web page or browser, you can write some JS functions and debug them straight in VS. I only started my first project with Express last night, but I think there, the node tools will allow you server side debugging, e.g. a breakpoint when a request is received. I'm also very optimistic that Google can integrate Chrome with nodejs, just as MS allows you to debug JSD running in Edge on breakpoints set in VS.
|
|
|
|
|
If you anticipate using some of the underlying technologies within the MEAN stack, then there is obviously a benefit to be had from learning all and / or part of it. I've looked at at parts of it previously, in particular Node.js but have never had a reason to explore any further.
If you want to learn something new and feel there is value to be gained from doing so, then go for it.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
I don't have an opinion on MEAN; however, you should learn technologies other than C#/ASP.NET.
Every single technology that is mainstream at the time someone enters the IT field will fall by the wayside during their career. I can't think of any technology that was hot when I graduated college that is still mainstream. Many no longer exist in any real sense. Yeah, some are still in use, but it's legacy code.
The IT world will migrate to newer, different technologies. Those that don't migrate get stuck in a backwater niche. I've known far too many people who clung to an old technology because they knew it well, and ended up unemployed while they frantically tooled up on newer technology.
MEAN sounds like a good choice -- it's totally different from C#/ASP.NET and you can learn it OTJ and get practical experience with it. If you never use it again? You've learned another way of thinking, and that is critical to each technology. You will carry the knowledge with you for the remainder of your career.
It is very true that the more we know, the easier it is to learn new things.
|
|
|
|
|
How to prepare a tofu:
Step1: Throw it in the trash
Step2: Grill some real meat
Done.
|
|
|
|
|
Wrong. Don't waste food, not even that stuff.
0) You need two X chromosomes to happily eat that stuff, so invite some over to get rid of it.
1) If it's not enough, lay out additional breadcrumbs.
2) Now get some real meat.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
That will work, too!
|
|
|
|
|
Tofu is not bad, but you should not expect "meat". It's not, and should stop pretending it is. It soaks up other tastes well, so it's best baked with bacon. Still not meat, but now you have bacon-tasting bean-blocks.
..but I'll prefer a block of tofu (even raw) everyday over that modern insect-meat. Bugger me, something bugs me 'bout those burgers 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
But I like real food. Real meat rocks! 
..and oh.. can you just leave the bacon out of tofu?
|
|
|
|
|
Vincent Maverick Durano wrote: But I like real food. Real meat rocks!
Well, yes, that's evolution. If you were created to eat plant-material you would have had as many stomachs as a cow. Would also mean that your brain would need to be somewhat smaller.
Vincent Maverick Durano wrote: ..and oh.. can you just leave the bacon out of tofu?
No, otherwise it will taste like tofu
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
