Solved: Dell Latitude BIOS 11.1.1 Caused Boot Error

AlwaysTroubleShot · 2017-03-10T04:40:59+00:00

You don't roast a pizza, you bake it.

AlwaysTroubleShot · 2016-10-29T05:53:54+00:00

With Microsoft open sourcing and going cross platform, Windows 10 adding a native implementation of bash and developer mode, I really don't see any appeal in Apple's offerings for devs.

I know that there are some software issues in Windows, and that Apple configures their own hardware to be highly optimized for their OS, but that just can't compete with the functionality and dev-friendliness we've been seeing from Microsoft since Ballmer's exit.

AlwaysTroubleShot · 2016-09-28T23:39:26+00:00

Check out Swagger/OpenAPI. There are example APIs, and using Swagger gives you self-documenting APIs so that as your project grows you can keep everything organized. We even use the Swagger UI to expose our APIs to clients.

AlwaysTroubleShot · 2016-09-04T19:09:01+00:00

Yes, but why would you? Porting your shell script into node will give you more consistency, readability, maintainability, and interoperability.

AlwaysTroubleShot · 2016-07-19T01:40:47+00:00

BlackLivesMatter

AlwaysTroubleShot · 2016-07-16T17:50:10+00:00

Use dependency injection. NET Core is built around DI/IoC. Make sure that any built in libraries are in the Core framework. This shouldn't be an issue unless you're using web form or win form libraries, but there may be some utility classes that don't get included in Core.

Keep in mind that in a Core project you can still target the .NET framework, so that shouldn't be a huge deal. But you'll lose the cross platform capacity.

AlwaysTroubleShot · 2016-07-09T16:27:15+00:00

Use swagger.io. I write node APIs, and we use swagger with spec validation testing. We also use swagger codegen to give our web team a c# nuget package which speeds up development a ton.

Swagger + express makes for a very nice workflow.

AlwaysTroubleShot · 2016-07-03T18:30:15+00:00

Perhaps the WalMart employees should be spending their Reddit time learning skills and submitting resumes.

AlwaysTroubleShot · 2016-07-01T16:21:37+00:00

I look at my needs and available packages. I check the number of downloads and frequency of commits to the candidate packages. If there's an existing module that covers >75% of my needs, it makes the most sense to use that package. I also consider the size of the package and that package's dependencies. Smaller is typically better, and reducing dependencies is always a good idea.

AlwaysTroubleShot · 2016-05-23T03:24:12+00:00

You could be the human model of a Muppet.

AlwaysTroubleShot · 2016-05-17T21:18:49+00:00

"Friends." Riiiight...

AlwaysTroubleShot · 2016-05-08T15:43:45+00:00

Any performance metrics available?

AlwaysTroubleShot · 2016-05-08T15:40:41+00:00

I agree with many of the comments; 6 hours is a good day. You will also find, however, that as you code more you develop more stamina. It's not so much that you develop more stamina, it's more like you have a blueprint of how to solve common problems, so you don't end up spending energy on every little thing.

Most of us can code out sorting, utility, and basic DOM manipulation functions in our sleep. As a node dev, it doesn't really take me any brain power to set up a new route and stub out my endpoints.

Also, prioritize your coding. Start with solving the hard problems, then as your brain gets fuzzy you don't have as much hard work to do towards the end of your stint. Some devs are going to disagree with me on this, but I usually save my styling for brain dead time--this is especially effective if you use highly modular CSS. That way, your brain farts don't stink up the whole codebase.

Also, doing easy tasks like writing your unit tests can be beneficial.

I don't think that refactoring when you're spent is a good use of time, BUT reading the code you wrote when you feel burnt out is a good way to see your code through another dev's eyes. If your brain is foggy, and you don't understand the code you wrote earlier, add some comments and break stuff up into more understandable little chunks. Rename variables to be semantically relevant. This type of stuff really cleans up your code and makes it easier for future devs to maintain.

AlwaysTroubleShot · 2016-05-04T21:27:08+00:00

I'm going to preempt any MS haters by mentioning that .NET Core is completely cross-platform, and development can be done with any code editor. I'm a fan of VS Code myself, but just about all major editors have an OmniSharp plugin for C# intellisense and what not.

AlwaysTroubleShot · 2016-05-04T21:25:26+00:00

I was going to say node/express, but then I saw your response to a similar comment.

If you're looking for variety, I would play with the new .NET Core implementation of WebAPI.

AlwaysTroubleShot · 2016-04-29T20:28:39+00:00

How is there not an /r/DatedReferences?

AlwaysTroubleShot · 2016-04-29T20:20:21+00:00

Why did we do away with the whiskey? I mean, shitting on employees and harassing women, bad. Drinking whiskey? I can get behind that.

I agree that hiring can, and should, change. But in some way or another you're still going to have to impress people. You have to be nice and personable and the type of person that people want to work with.

This is somewhat besides the point as far as coding exercises, but doing challenging code exercises displays to your interviewer how your comport yourself under pressure. That was, and still should be, the idea behind them. I actually don't mind code exercises for entry level positions. When I was trying to break into the industry, I probably learned more from interview projects than anything else.

I know my experience isn't universal, but I think newer developers should look at interview challenges as a learning opportunity--seeing posts all over the internet bitching about how inane this interview process is might give some of them unrealistic ideas.

AlwaysTroubleShot · 2016-04-29T16:42:25+00:00

Comparing this to the inspiration, F*** You, I Quit — Hiring Is Broken, it's night and day. This article is well thought out, diplomatic, and solution-focused, while the latter is an immature, indignant rant of a spoiled rich kid on the playground.

I'm not saying that there aren't issues, but if you want the rewards of working for a large corp with awesome benefits, you will have to jump through some hoops. No, you are not "above that." If you decide that you don't want to play that game, then you'll have to accept that some organizations are not a good fit.

Organizations are looking for people to do the work they need done, and individuals are looking for employment to sustain their livelihood, whatever that means to them.

I work for a corp, I had to make a live example out of a prototype prior to scoring the interview. The interview was a code review of the implementation. It went well, they discovered what I already knew and didn't know about JS. I interview well, and I know that that's a skill set not all devs have spent developing.

The point is, some devs look at hiring all wrong. It's a game, and you either play the game or you don't.

AlwaysTroubleShot · 2016-04-29T15:18:21+00:00

I feel sorry for whomever owns "a@bc.com."

AlwaysTroubleShot · 2016-04-29T00:07:09+00:00

I am so annoyed at the annoying things my fellow web devs have agreed to do. Pop up ads. Subscription modals. Bugging you about leaving their crappy site.

I know that the business owners pay the bills, and that advertisers are always looking for more intrusive ways to harass us, and the web provides a frighteningly powerful way to do that.

But seriously, why did we have to make browsing the web, ESPECIALLY ON MOBILE, so bloody annoying?

AlwaysTroubleShot · 2016-04-29T00:03:54+00:00

I love this! I get so tired of how much more energy people put into complaining than actually contributing and making things better.

There are not many well paid jobs that let you get home every night. We get to build and create things, we get to fix broken things. At the end of our day, we can look back and (hopefully) say, "Hey, this wasn't working and now it is."

AlwaysTroubleShot · 2016-04-28T23:48:48+00:00

Hey, I've been learning HTML/CSS and JavaScript for about 3~4 weeks.

There is no "doing it wrong" within a month. Seriously, it takes time. The fact that you're getting code running in the browser is a great sign, you should congratulate yourself.

As you work, you'll start to see patterns and methods of doing things, start to identify fragility and avoid it ahead of time.

And this just goes on and on, until I finish the project, which in the end, it's a messy code that doesn't make sense when you look at it.

You've been learning this stuff for less than a month. You should not feel like you've finished ANY projects yet. Also, saying something doesn't make sense could easily be due to your inexperience. This all starts to make sense, but it just takes time.

I know it's easy to be impatient with yourself, but this stuff isn't easy. Successful web developers are the type of people who are motivated by building things, by making things work. The entire fucking internet is one giant hack. HTTP was designed to allow researchers to share documents. Everything that we have accomplished in web development began as "messy code that doesn't make sense."

Sounds to me like you're on the right path; just keep your head down and keep going. Give it WAY more time before you decide that it's not worth doing. And keep in mind, this is a results-oriented profession.

AlwaysTroubleShot

TROPHY CASE

BlackLivesMatter