• Content count

  • Joined

  • Last visited

Community Reputation

2990 Excellent

About szecs

  • Rank

Personal Information

  • Interests
  1. That first triangle.

    What Vilem said. Since rendering should be a separate module anyway, I see no point in not making at lest a very basic rendering even if you are so experienced in the specific game type you are making that you need no visual testing/debugging and you are fine with a blank console. To answer your question directly: I'm starting with a triangle immediately. And 10000 LoC is a complete (simple) game for me. I'm very surprised how you can reliably/effectively test some game code that size with no visuals, just console messages (I hope you at least have those...). I could never imagine how could someone write a game (or anything) from just left to right (either technically or psychologically).
  2. It's a common saying that programming is not about the languages but the way of thinking, but every new language I tinkered in taught me new things. And I agree that a shallow knowledge is not enough. Just an example: on a glimpse Javascript looks very similar to C (the basic syntax is almost the same) and LabView looks very different to them (graphical-like programming where you don't have direct control on execution order (things run "parallel")), but having done some programming in Javascript taught me that it's much farther from C than LabView from C. Labview and C can almost be translated to each other 1:1, but Javascript is very different. Variable scoping , asynchronous execution (it doesn't have anything like "halt execution till something else finishes" (no delay function, no busy loops) etc.); requires different architecture. I guess I will see that it''s not really different from other programming, but certainly it will teach me some new patterns (asynchronous programming). EDIT: okay, it's actually pretty easy to halt execution in Javascript with a busy loop.... Anyhoo, you shouldn't. Maybe I shouldn't do programming only in the night and morning hours... EDIT2: it's actually the task/circumstances that taught me new things, so forget everything I said
  3. Looking at the tons of different "apps" for the same task, lots of totally useless other apps (like the one which puts a crappy cartoon rabbit ears on your selfie which is among the factory installed apps on my GF's mobile), it seems that the market is not dictated by demand but by the free-time and boredness of the developers.
  4. How Much Do You Program Outside of Work?

    My comment was supposed to be a joke. I know that you are a male.
  5. How Much Do You Program Outside of Work?

    A woman president, nah...
  6. How Much Do You Program Outside of Work?

    I used to program a lot (12 hours a day) in the past, but I was is school that time. I don't remember how much programming I did when I started working, because my new hobby became Lego Technic design that time. I'm slowly getting out of that too, so maybe I'll get back to programming again if it's possible with kids (seems to be more possible than with a Lego hobby).
  7. Probably it was Open Transport Tycoon Deluxe a few years ago. I managed to grow the little cities almost to make the map into one single giant city. As far as I remember it took weeks, 8-10 hours of playing per day. And it was not the only "mission", I also played on several other maps where I focused on the clever rail junctions more.
  8. Well, don't come to Hungary. My salary is only good in Hungary but I don't earn much more than a diswasher in Western Europe (with prices that are close to Western European prices...). Plus there are other shit in this country and the youth is actually fleeing from here. But the proportions are similar. Just don't expect to get into the top companies and positions (so don't aim for Boeing, just a company that produces the toilet flusher in their planes). Sorry for the typos. No spellcheckand I'm sleepy as asdasd
  9. I'm a mechanical engineer and it pays quite well. Having programming experience as a mechanical engineer also gives you a huge advantage over other mechanical engineers. Programming in my job (which is about only 5-10% of my work hours) meant bonuses and pay-rises without asking, and it also satisfy my programming desires quite well. I don't know about other countries, but mechanical engineering is a quite stable job too. There are people at the company where I work who has been working there since 20 years now. I have been working there for 5 years now and I don't see they'd lay me off. It's more likely that I will "look for other challenges". 5-6 years of collage, and I don't think you'd need to go to the best universities. Sure, you won't be a rock star designer with Ferraris if you are after that stuff.
  10. Networking, 3rd party code is involved? Those can cause random shit too. Anyway, when I run into bugs like this, I usually apply a fallback-like "fix" at the smallest scope I can locate where the bug occurred. I test if this ""fix"" doesn't cause problems, and I am done with it for that time. I cannot put enough quotation marks around the word "fix". It also helps if others test or use the software: The latest of this random crap (a measuring amplifier fails to work in buffered data acquisition mode, even after) I ran into was eventually coming up in a rather deterministic way (always) for a specific use case and it turned out that my fix I applied months earlier worked pretty good, and I could improve the fix (still no buffered DAQ but at least the program properly fails back to software timed sampling). The root cause is still not clear, our best guest is that our special/custom/motherfucker corporate firewall is blocking a port for the program only (or rather it's opening the port only for a specific other program, which works fine with buffered DAQ). The device can connect and read samples, but buffered DAQ required another port to be open. Dunno, maybe there's a proper way to test/debug these problems, but I'm not a real programmer, so Story time over.
  11. Also, immigration and terrorist attacks are two separate things.
  12. You'd be tortured until you confess you are Allah himself... because of a mistake or someone reported you because you were unsympathetic. I grew up in a country with that  "janitor society".   Also it's not likely that our society and science will get to a level soon enough (for solving the urgent problem of terrorism) to avoid the collateral damage that a police state would mean. A collateral damage that would turn even some of the Christian übermensch snow white hetero people towards radicalism and opposition.   Edit: Internets. That's a problem. Pretty much all these attackers are young people. People at their late adolescence (at least mentally). Pretty much we were all rebels at this age. But we didn't have internet, so it was all played out in our heads or in a small futile group. Just an example: I, for one, was excited and not horrified by the WTC attack. I was stupid as fuck (age 16) but my stupidity had no effect at all, and turned into unlimited pacifism. I don't know what would have happened if I had found a group that could control my otherwise typical feelings and thoughts. So my solution: kill the internet and all people between the age of 15 and 25.   I still don't speak English and can't form a comprehensive point, sorry.
  13. Not only from ethical point of view butt also from practical point of view. If we take these measures other minorities will be afraid and plunged into radicalism so the circle would continue until only Breivik and Heidi Klumm stays alive.
  14. What are you working on?

    Recently got into "web design", so I'm working* on a website to show off our work of measuring and documenting old  houses (some of them are 150 years old) in Transylvania as a part of a folk architecture research project (for long it was endorsed and organized by the biggest university in Hungary, now it's voluntary). My girlfriend started the website project with a web-designer program, but it was too constraining, there were some unsolvable glitches, so I took over the programming part.     * hacking the crap out of the Blogger platform, struggling with javascript (as there is no systax check in blogger, so I edit the code - update the post - test it - press edit post - edit code, which is a very slow process), making html code generators to ease adding pages, menus and content. The challenges include that we still don't have a final design, so the site is still in lorum ipsum state with random elements on random pages with some random menu. So far I've got an "interactive map" to select villages, a custom lightbox with fake tags (both work in progress), a dropdown-menu generator that can be inserted in the xhtml of the blogger template (and this blogger xthml coding is hardy documented, which means hacking like crazy) If anyone interested (these can't be accessed through the menu yet): Map probe with village placement helper code generator thing: Gallery:
  15. Quasar light bending footage, Hmm... don't get it

    Um, yup, based on Nypyren's comment, maybe it's some polarization effect of the lens. or.. something... I mean the light from the object behind is polarized in a circular fashion by the object in front of it, and the lens has polarizing filter. so if you'd rotate the cam, the image of the four spots would rotate along.   or.... something...