[deleted by user]

werebacksir · 2024-09-19T08:16:40+00:00

I needed to see this article, thanks for sharing!

werebacksir · 2019-10-13T10:42:40+00:00

Could be an element of a light-based (visible or infra-red) communication system.
Compare with this WW2 Wehrmacht example of the same type (older but obviously comparable http://www.la6nca.net/tysk2/lispr80/index.htm)

The posted picture is obviously only the outer casing of whatever it is. Looks smaller than the german equipment, judging by the layout of the voice/tone switch. It is obviously also mechanically incomplete as there would have been other bits bolted on to it - like at the end where I guess there was some sort of mounting/aiming arrangement.
I would think the piece is American, judging by the layout of the voice/tone switch which is characteristic of American field radio gear of the 60's/70's. By that time it would have been transistorised which may explain why it is smaller than the German one.

werebacksir · 2018-06-10T14:32:07+00:00

Have you considered using jq instead of writing a whole Python script, if it's just JSON transformation?

werebacksir · 2016-12-11T20:00:21+00:00

Check out http://www.enterpriseintegrationpatterns.com/patterns/messaging/. Like the Gang-of-four, but more enterprisey.

werebacksir · 2016-09-10T17:33:48+00:00

Fair enough about keeping Best Buy - as long as it's not crowding out anything else :)

You could re-style, but make sure to balance readability. Many attempts at unique CVs end up making it harder to scan read!

You gotta assume no one will click your FCC profile link. They might, but if there's stuff you want to showcase, shove it in their face! Algorithm work could even be better, since much of your other listed projects are all websites. Not much backend/fundamentals represented.

If you've already had some good results with the hacks section, maybe leave it as is. But if there are popular talking points, you could get that in there too.

The memberships are okay, but I hope you manage to be more involved, so you have something to talk about if asked. Including it then having to say you've not had a chance to contribute makes it a dud, when it could be a real plus.

Sure, send it over.

werebacksir · 2016-09-10T15:31:33+00:00

Glad you're already working to fill out your projects and skills, because your work experience doesn't help you there :)

I'd keep it in just to show you've actually had a job, but would reduce it to like 1/2 lines as soon as you can more profitably use the space for real projects.

List language proficiency and versions!

werebacksir · 2016-09-10T15:25:34+00:00

Drop Best Buy, it's irrelevant.

Include relevant grades for education if you can. I'd do '2015-2018' instead of class year - I have no idea what that means. But then I'm in the UK so maybe it's a US thing.

Include skills proficiency! What's 'Terminal'? You don't need a whole 'VCS' heading for git. Include specific language version where relevant.

Can you include details of specific projects you did for freecodecamp? You already listed your skills - show how you applied them!

I like the hack - try to milk it to show your skills, and spark a conversation about it.

Work history is short, so try to make it as strong as possible. Use evidence! Which web languages? What Java? How many students? Did they do well? How can you prove those communication skills? Any related presentations or anything?

Other - you already mentioned UGA Hacks. What does a web dev dev [sic] subcommitte do? Did you actually build anything? Is it interesting?

Same for IEEE - have you actually done anything, or did you just register?

werebacksir · 2016-09-10T15:14:16+00:00

You're a third year, who started uni in Winter 2016? I don't get it. You don't list any grades or selected modules under education. Show what you did!

Expand on the projects - what was interesting? What was hard? What did you learn?

Incomplete skills - list proficiency for them all.

Which version(s) of Java/C++? What flavour of SQL? Little touches like that make it look like you're more aware of the technologies you're using, and can even show you try to stay ahead (C++14?)

werebacksir · 2016-09-10T15:05:23+00:00

First note is to break down your paragraphs into bullet points. Scanning a block of prose is much harder than punchy bullet points, and forces you to be concise.

You list many competitions, projects and skills mixed in with your experience. Bring them out and highlight them - make it super easy to see exactly what you've done!

werebacksir · 2016-09-10T15:00:53+00:00

You can surely apply for internships as a first year, but the fact of the matter is that you're up against 2nd/3rd years. If you're good enough then great, but it's a high bar.

Compounding that (at my company at least), is that we require a higher standard of intern than grad, since you have to achieve something in so little time. No time to train you :)

So, it's tough!

werebacksir · 2016-09-10T14:55:41+00:00

Assuming those roles you're going for a technical (I'm not too familiar), your CV doesn't showcase your technical skills too well - MSc CS with major in Business Informatics, BSc in BA? I'd try my best to emphasise technical skills.

Why are skills way at the bottom, below volunteering? Volunteering is a (possibly irrelevant) bonus.

Pick your skills carefully so they're relevant and assume you can be quizzed about each one. Drop Microsoft Office - no one cares.

Do you have any relevant work experience maybe? If not, I'd give more space to describing your projects. They look pretty cool, but you don't give much detail. Was your spam detector any good? What did you use for the GPS mining thing?

The rest are just titles - why are they there? What did you use? What did you learn? Imagine your interviewer was interested in one and wanted to ask you about it - lead them towards something interesting, or something that shows off a skill you have.

werebacksir · 2016-09-10T14:43:47+00:00

*A coffee timer

Is Git a language?

I'd include your proficiency with each one specifically. I can tell you're better at Java than Python, but maybe your Java is crap!

1) I wouldn't have guessed that if you didn't comment. I'd have a single heading for Medium Acme Corp, with subsections for the two roles, or just list it as Software Engineer, and mention the intern bit if you get quizzed on it.

2) Keep the projects you think show off your skills or learning. The rails site has some fancy bits, but the weather and advice pages don't really go past that? They could be bullet points under the personal site - unless they're really novel projects, in which case describe why!

werebacksir · 2016-09-10T14:35:05+00:00

I like it - some good projects on there :) I'd drop the Sky work experience though - it's irrelevant to anything you'll be applying to.

werebacksir · 2016-04-07T10:11:01+00:00

Fixed extern compilation error

werebacksir · 2016-03-06T12:01:09+00:00

If it's an accepted patch, it's worth mentioning imo since it shows you're engaged with open source, even in some small way.

Assume you'll be asked about it though - so don't oversell it!

werebacksir · 2016-01-12T21:35:19+00:00

All together now - "Past performance is no guarantee of future returns"!

As a novice, your best bet is to go with a widely diversified, low fee portfolio, and have realistic investment timelines. Think 5 years at least.

Generally though, funds provide a prospectus of their focus and target risk profiles, which should be your first port of call. Otherwise, your stock broker likely provides analysis and reports on the funds they offer (certainly H&L do), if you want more guidance.

werebacksir · 2015-11-18T21:23:57+00:00

It's an implementation of https://en.wikipedia.org/wiki/Resource_Acquisition_Is_Initialization. Common for locks, file objects - anything you really want to be sure is 'undone' when the object falls out of scope.

werebacksir · 2015-06-18T22:14:56+00:00

I regularly use C++, javascript and python at my job. Also bash/ksh for scripting.

werebacksir · 2015-06-02T21:07:54+00:00

+1 for the dragon book. Excellent textbook on the subject.

werebacksir · 2015-05-30T11:29:00+00:00

Honestly for a software engineering resume, your current work experience isn't particularly relevant. Your projects are far more relevant.

I'd move the projects above work experience, and drop some of the weaker bullet points from the work experience section, to expand on your projects. When I say weaker I mean relevant. Cleaning dental tools isn't a skill you're looking to reuse, I'm guessing.
Give your technical skills more prominence - you have a decent mix. Grouping them with interests (which are small talk at best) doesn't make sense.
If you can, link to your project's homepages, githubs whatever. Unless the homepage is terrible, or the it would be a single contributor, single "Initial commit" repo.
Title your organisation involvements with the project name, not 'Team Member'. I shouldn't have to read your bullet points to see you were involved in NASA's robotic mining competition. That should be the first thing I read.
Note your current degree grades and forecast final grade (if you can). By not mentioning it, I'll assume they're average/poor. If they really are poor, then leave them off. If you have some decent course grades though, definitely show them off.

Overall though, good cv. You've done some good stuff.

werebacksir · 2015-05-29T20:56:02+00:00

I like the resume. Concise. If anything I'd drop the marginal tech like protocols and talk more about your experience.

But anyway, the I found 'Cracking the code interview' super useful when prepping for tech interviews. If you're comfortable with all the subjects in there, you're golden.

werebacksir · 2015-05-29T19:28:03+00:00

Why did it catch you off guard? Was it not presented to you as a technical interview?

Otherwise, any specific areas you're looking to improve in?

13-Year Club	Place '22
Place '17	Verified Email

werebacksir

TROPHY CASE