I'm taking a parallel programming class this summer and I think it's super cool. We're playing around with OpenCL. It's also yet another moment where just when I start to feel like I know a little bit, we start looking at some of the advanced OpenCL examples Intel provides and it's like
Doing a demo of clojure for our dev team built this guy for the demo: https://github.com/colonelrascals/snek
The main one Pretty pumped to go to the official conference. For python I only went to pydata, which is cool, but Pycon sounds sweet
The school that I go to requires all vaguely computer-related students to do some amount of hardware stuff, which I think is interesting but not worth what I had to pay for the classes. Most of it was informative, but not particularly relevant (calculating by hand bitwise ORs and things like that), but the one I'm in now is pretty cool. We get to mess around with an Arduino board for a bunch of simple pre-written labs, and then get to do our own thing. My partner and I are making a room alarm using a motion sensor, some bright-ass LEDs, an obnoxious speaker, and a keypad to arm/disarm. This stuff is actually super cool. Possible video to follow.
Arduino compatibie boards are great, there's tons of tools to let you write in your language of choice and flash them. We're going to move soon and I'll have a garage to tinker and solder boards (and a Micro Center very close by). Wife previously didn't want me soldering in the house.
I'm basically the only dev on our project so I'm soon going to rewrite our Java based Quartz scheduler in Elixir. The damn thing struggles with too many simultaneous requests and shits the bed with thesr transiebt DB connection errirs, I'm hoping BEAM will solve this problem.
My partner and I got this thing to work, but it's only effective out to about 12 feet. Possibly because we only spent like $5 on the motion sensor.
From what I understand about BEAM it should certainly help. At some point I’m going to look into LFE.
Bleacher report supposedly went from 150 servers to just 5 by using Elixir and leveraging BEAM's ability to handle high numbers of concurrent connections. https://www.techworld.com/apps-wear...eacher-report-handle-8x-more-traffic-3653957/
Anyone else go to re:Invent? My first time and first time in Vegas so I definitely treated it like a vacation since my boss signed isus so late and I couldn't get many sessions I wanted.
Started my second job a couple month ago, JS for a financial services company. The project I’m working on is completely internal which is nice, means I’m no longer wasting my days debugging nonexistent customer issues
In Silicon Valley when they're asking everyone in the company what they actually do, Gilfoyle goes on this rant about how he does the network stuff no one knows anything about and no one appreciates. After my Networks class, I am perfectly okay with other people being Gilfoyle.
Any good information out there regarding which cities in each state have the best/highest selection of jobs in software development and in what technology/stack? Wife and I have talked about eventually moving and we aren't set on any place in particular so really just starting to do some exploratory research. Ideally would like to stick with the Microsoft stack.
Saw Pile Driving Miss Daisy post about moving to Duluth and how it's where a lot of the software jobs are. Georgia is one of the places we've discussed, but never would have guessed thats where the majority of dev jobs are.
I mean any top 20 city in the US is going to have jobs for .NET developers, just depends on where you want to move, cost of living, how much you think you can make based on your experience, etc. Atlanta is red hot for dev jobs right now, Duluth is a suburb and has a couple of companies but there are tons of jobs in downtown/midtown Atlanta. Even Alpharetta is growing out its own little tech hub.
Who here can help me (I'm not a developer) with writing some javascript? I know it's childs play. Need another dev with healthcare experience. I don't have enough devs and I'm trying to write this shit myself to help the team out.
I made a fantasy baseball lineup optimizer last year, going to try a mlb daily game projector this year using baseball savant’s data. Will share here if I end up liking how it looks
hmm. i don't know of any info that is exactly what you're asking for, but the combo of these two things might be helpful : https://trends.google.com/trends/?geo=US https://insights.stackoverflow.com/survey/2018/ So for example, the states where React makes up a large % of search results in the past year are: Washington, California, Utah, DC, Mass .NET it is Washington, Oregon, DC, Virginia, Connecticut For Python it is : Mass, California, Washington (state), Washington DC, Virginia COBOL is : Connecticut, Nebraska, Arkansas, Iowa, Wisconsin
I'm in the final stretch of my school stuff. Objectively I know that there are specific things I can do (relatively) easily which fresh students and random people cannot do, but beyond that it's not like I ever hit some checkpoint where it felt like, "hey, people should pay me a bunch of money to write code now" Is this normal?
yes i think so regarding being worthy of being paid a bunch of money : most tech jobs will have you working as a small cog in a big, established system. In that case the economic value you're capable of providing/creating is dictated primarily by the system you're working in (the business, the strategic choices, the tech being used, the product you're selling, etc) , which, in the context of a specific job, is out of your control. Another way to look at it : the guy who maintains the HTML for amazon is probably providing lots of economic value without necessarily being highly skilled or worthy of a high-paying career. Some Visual Basic programmer somewhere is probably adding shitloads of value by doing some boring shit with customizing buttons in accounting software.
A strong grasp of coding fundamentals and CS concepts is all anyone will really expect from a new grad applicant. They know they will need to teach you their systems and slowly build up your domain knowledge. From what you've posted in here I think you'll have a solid foundation to get attention for entry level positions. .NET jobs are everywhere.
To expand, coding has one of if not the highest percentage of impostor syndrome versus other careers. I remember reading how it heavily affects software devs in the first few years of getting a job. Don't know which article I read before, but tons pop up when searched: https://jaxenter.com/impostor-syndrome-survey-149402.html https://www.laserfiche.com/ecmblog/shut-up-imposter-syndrome-i-can-too-program/# If you're someone without high confidence I would search on how to best handle it since it leads to high anxiety. If not just understand that it's completely normal and that you will learn and eventually should feel more comfortable. Though even once you're comfortable in your job you'll know how much knowledge outside of your scope that you are missing, so the feeling probably never fully goes away. The money really should just be ignored, even now at the point where I think I'm a core part of my team I still laugh at how much they pay me. It's just the market, it's incredibly hard and expensive to hire good programmers.
Hell yeah bitch. Finished this book and starting Programming Phoenix 1.4. https://www.manning.com/books/elixir-in-action <- Sasa Juric, he's my favorite speaker and this talk got me interested in Elixir even though it's only about the VM (BEAM) https://pragprog.com/book/phoenix14/programming-phoenix-1-4 I gave a talk about distributed processes in a cluster with Swarm, but I've found that using Horde + DeltaCrdt for state handoff is actually better for my limited needs. Here's a small repo I put up as an example. https://github.com/joxford531/KeyValue_Horde Are any of you going to the Lonestar Elixir conference at the end of the month in Austin?
Ayyyyyyy Finally agree that closure is gross? Go through this https://elixirschool.com/en/ This is one of the best video learning series https://elixircasts.io/
Aight boys, back at it for the third time. Wrote an ETL package from a postgresql db and trying to fire it all back up again Running through a GA Tech MOOC to hammer the basics back out then all the data science pluralsite/DataCamp examples. Ideally gonna start a micro masters this summer them transfer the credits to a full program. Most likely do GA Techs or USC San Diego if I end up moving to the west coast. USCSD seems to be very python heavy vs some others
Do any of you work for a team with a good system for peer reviews? Does such a thing even exist? I try to be critical & honest but most people seem to just approve anything as long as there are no obvious breaking changes. Or only comment on trivial things like linting errors. This leads to a ton of problems down the road and lots of less than perfect code & logic that is merged in and built upon.
When do you execute peer reviews? On PRs? I would say, if on PRs, when a breaking change makes it into production, find the person(s) who approved and ask them why.
Yes, by peer review I mean pull request reviews. Good thought on keeping the reviewer accountable for bugs, not just the author. We don’t really do that. But it’s not so much the breaking prod changes that bother me, it’s the sloppy code that ‘works’ but is not well written.
Well, he made it sound like this is happening rather frequently. The one off scenarios obviously shouldn't be as harshly judged. In the case you pointed out, I would have QA create a bug and a developer should pick it up and create an automated test for it. There are tools and linters out there that will scan code repositories and reject builds if certain syntax or style guides aren't met.
Just from a political standpoint, this feels like something that should be addressed in your company's coding standards. Having said that, there's no harm in asking why somebody did something a certain way (or why they didnt do it a different way) during a code review.
Yeah blaming people isn't a good way to make a team better. Instead you can make it about improvement and have those involved write up what when wrong and why, and how processes can be improved to avoid it next time. As far as getting good code reviews, that's just company/team culture. I don't know how you would improve it if it's already broken like that. Maybe lead meetings to set coding standards and ask people to enforce them in the code reviews.
Struggling with this myself right now. We're in the infancy stages of setting up automated testing, CI, and linting and it has been a painful process. Although we don't have many seasoned developers on this project (myself included) so it's been sort of trial by fire. We've been pretty good about reviewing bugs and process issues and figuring out what went wrong and implementing changes to avoid those issues so far, but down the line without the proper testing it's not going to matter